idaholab
Need way to record test environment change
In the discussion with the assessors one place we may have a hole is recording "system support software" changes. This may not have anything to do with CIVET but I want to start the discussion here. When we make a change to the test system can we come up with a way to figure out that it changed if we needed to pull that information during an audit?
e.g. If Jason updates the compiler, that gets reported in the environment step of every build, it would be really cool if we could figure out a way to report the changes so that we could verify the software works as the environment changes.
- Come up with a standard way or or ticket reference when the environment changes
- Have CIVET monitor for changes and record them in the database? (maybe, maybe not)
Is it not enough to just do a module list and env and the beginning of every test? That should capture it well enough.
Yes, but when we get an audit we need to be able to pull all of the times changes occurred to show "objective evidence". Right now we have no way of doing that.
Good luck with that.
This one might come down to a "procedure" for @milljm . If he modifies the environment of the test boxes he may need to make note of it somewhere...
Derek
On Wed, Mar 23, 2016 at 6:17 PM Cody Permann [email protected] wrote:
Yes, but when we get an audit we need to be able to pull all of the times changes occurred to show "objective evidence". Right now we have no way of doing that.
— You are receiving this because you commented.
Reply to this email directly or view it on GitHub https://github.com/idaholab/civet/issues/45#issuecomment-200565549
Yeah. Thought about that too. Not good enough because there is too much room for human error.
This issue keeps coming up at each assessment. We can handle this in CIVET. We just need to parse and store relevant parts of the environment dump, then we can query to our hearts content. On Wed, Mar 23, 2016 at 6:03 PM Derek Gaston [email protected] wrote:
Good luck with that.
This one might come down to a "procedure" for @milljm . If he modifies the environment of the test boxes he may need to make note of it somewhere...
Derek
On Wed, Mar 23, 2016 at 6:17 PM Cody Permann [email protected] wrote:
Yes, but when we get an audit we need to be able to pull all of the times changes occurred to show "objective evidence". Right now we have no way of doing that.
— You are receiving this because you commented.
Reply to this email directly or view it on GitHub https://github.com/idaholab/civet/issues/45#issuecomment-200565549
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/idaholab/civet/issues/45#issuecomment-200588486