|author||bertagaz <email@example.com>||2015-09-07 09:35:25 +0200|
|committer||bertagaz <firstname.lastname@example.org>||2015-09-07 10:57:22 +0200|
Blueprint: add video captures to artifacts to be kept.
Diffstat (limited to 'wiki/src/blueprint/automated_builds_and_tests')
1 files changed, 13 insertions, 8 deletions
diff --git a/wiki/src/blueprint/automated_builds_and_tests/automated_tests_specs.mdwn b/wiki/src/blueprint/automated_builds_and_tests/automated_tests_specs.mdwn
index b1f4466..7b832d0 100644
@@ -130,19 +130,24 @@ the running test session.
Videos may be a bit too much to keep, given they slow down the test
suite and might take quite a bit of disk space to store. If we want to
-keep them, we may want to do so only for failing test suite runs. But
-then, often the screen capture are enought to identify why a step failed
-to run. If we decide to still use them, then we probably have to wait
-for [[!tails_ticket 10001]] too be resolved.
+keep them, we may want to do so only for failing test suite runs. If we
+decide to still use them, then we probably have to wait for
+[[!tails_ticket 10001]] too be resolved.
+Proposal for a first iteration:
* For green test suite run: keep the test logs (Jenkins natively do
- * For red test suite run: keep the screen captures and the logs.
+ that) and video captures
+ * For red test suite run: keep the screen and video captures and the
+On the second iteration, we will keep video capture only for the red
The retention strategy should be the same than for the automatically
+built ISOs. In particular, we will have to pay attention to the rotation
+of videos capture (given they'll quickly bloat our storage space).
+Keeping them only for 7 days sounds reasonnable.