path: root/wiki/src/blueprint/automated_builds_and_tests/automated_tests_specs.mdwn
diff options
authoranonym <>2015-10-21 18:43:37 +0200
committeranonym <>2015-10-21 18:43:37 +0200
commit5d1603131c8f779feecddc30ec7a26fd50caecb2 (patch)
treeba4d289bef3c998d0a7584220ebb80453483bd01 /wiki/src/blueprint/automated_builds_and_tests/automated_tests_specs.mdwn
parentb25d21c50db43ac0e4a5179a010af5834227b548 (diff)
parent4c64182b0bc75f876d83036a6d60731731f90bcd (diff)
Merge branch 'devel' into test/10378-fix-tails-shipped-openpgp-keys-test-is-fragiletest/10378-fix-tails-shipped-openpgp-keys-test-is-fragile
Diffstat (limited to 'wiki/src/blueprint/automated_builds_and_tests/automated_tests_specs.mdwn')
1 files changed, 7 insertions, 14 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 b694e6a..5df035b 100644
--- a/wiki/src/blueprint/automated_builds_and_tests/automated_tests_specs.mdwn
+++ b/wiki/src/blueprint/automated_builds_and_tests/automated_tests_specs.mdwn
@@ -128,26 +128,19 @@ The test suite produces different kind of artifacts: logfiles, screen
captures for failing steps, snapshots of the test VM, and also videos of
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. If we
-decide to still use them, then we probably have to wait for
-[[!tails_ticket 10001]] too be resolved.
+We can keep the video captures in the build artifacts, now that
+[[!tails_ticket 10001]] is 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 and video captures, the
+ * For red test suite run: keep the screenshots and video captures, the
logs and the pcap files.
-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.
+In [[!tails_ticket 10155]] we calculated that we can probably keep the
+video captures for a full release cycle. This will be refine is reality
+claims the contrary after an evaluation.
# Scenarios