Commit f2fb7ce7 authored by intrigeri's avatar intrigeri
Browse files

SponsorS: add deliverable codename.

parent c0d73a40
...@@ -27,35 +27,37 @@ In November, XXX ISO images were automatically built on our Jenkins setup. ...@@ -27,35 +27,37 @@ In November, XXX ISO images were automatically built on our Jenkins setup.
In November, **314 ISOs** were tested by our Jenkins instance. In November, **314 ISOs** were tested by our Jenkins instance.
With the 1.7 release, we were able to unify back the way the branches - B.2.4. Implement and deploy the best solution from this research
based on our maintenance branch and the ones based on our development
branch were tested. (#10409) With the 1.7 release, we were able to unify back the way the branches
based on our maintenance branch and the ones based on our development
We have deployed the feature that prints out in the test suite logs in branch were tested. (#10409)
Jenkins a direct link to the collected artifacts of the failing step.
(#10445) We have deployed the feature that prints out in the test suite logs in
Jenkins a direct link to the collected artifacts of the failing step.
We found out that Sikuli was sometimes leaving PNG files in the Jenkins (#10445)
workspaces, and we worked on a fix. (#10476)
We found out that Sikuli was sometimes leaving PNG files in the Jenkins
We are being short again in disk space and need to anticipate that future workspaces, and we worked on a fix. (#10476)
infrastructure features will require more, so we're sorting out what's the real
needs of our isotesters on this side, now that we have more data points. We are being short again in disk space and need to anticipate that future
(#10396) infrastructure features will require more, so we're sorting out what's the real
needs of our isotesters on this side, now that we have more data points.
We are also short on isotesters to really test every single automatically (#10396)
built ISO image. So we're discussing if we need new hardware to cope with the
load, and if so, which kind. (#9264) We are also short on isotesters to really test every single automatically
built ISO image. So we're discussing if we need new hardware to cope with the
Meanwhile, our automated test suite will still be a bit more efficient load, and if so, which kind. (#9264)
on testing branches that actually change Tails' code, while testing
only some subset for the branches that only change our website or Meanwhile, our automated test suite will still be a bit more efficient
documentation. (#10492) on testing branches that actually change Tails' code, while testing
only some subset for the branches that only change our website or
We spent a lot of the CI time gathering statistics about the test suite documentation. (#10492)
runs in Jenkins in order to help the team writing the tests to identify
which scenarios were fragile, going forward to the release of the We spent a lot of the CI time gathering statistics about the test suite
notifications to contributors. runs in Jenkins in order to help the team writing the tests to identify
which scenarios were fragile, going forward to the release of the
notifications to contributors.
## B.3. Extend the coverage of our test suite ## B.3. Extend the coverage of our test suite
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment