Commit 121eb56c authored by intrigeri's avatar intrigeri
Browse files

Sponsor S report: focus B.2.4 on the most important bits.

... and take over vague sentence about rescheduling with something
that should be a bit clearer.
parent 60ae1d30
......@@ -60,6 +60,20 @@ In December, **788 ISOs** were tested by our Jenkins instance.
- B.2.4. Implement and deploy the best solution from this research
We went on with the effort we started in October, to identify test
cases that prove to be fragile in our CI environment, that were
blocking us from notifying contributors when tests fail there.
And finally, we reached the point when we felt comfortable with the
subset of our automated test suite we deem to be robust, and
unleashed these notifications to the greater Tails community
([announce](https://mailman.boum.org/pipermail/tails-dev/2015-December/009931.html)).
We will now go on working on making as much of our test suite robust enough
to be suitable for running in this context (B.3.11, see below).
([[!tails_ticket 10296]] and [[!tails_ticket 10382]])
Other than that, our testing setup has seen quite some polishing all
over the place, that we are going to sum up now.
As a way to optimize resource usage and to shorten the feedback
loop, we have limited the amount of tests we run on ISO images built from
documentation branches: we now run only the test cases that depends
......@@ -83,12 +97,6 @@ In December, **788 ISOs** were tested by our Jenkins instance.
after each release, resulting in losing their automatic build and
test history. ([[!tails_ticket 10123]])
XXX: move on top and explain why it's an important milestone:
We finally unleashed the automated tests failure notifications to
branches authors, as there were now much less false positives.
([[!tails_ticket 10296]] and [[!tails_ticket 10382]])
XXX: [[!tails_ticket 10717]], [[!tails_ticket 10507]]
## B.3. Extend the coverage of our test suite
......@@ -116,9 +124,6 @@ During December,
([[!tails_ticket 10497]]), we marked most network related scenarios
as fragile.
We also rescheduled the timeline we'll work on fixing the fragile
scenarios we've identified. XXX: that is?
## B.4. Freezable APT repository
- B.4.5. Implement processes and tools for importing and freezing
......
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