Hi,
As some of you might know, we'll spend quite some time this year seting
up automated builds and test using our Jenkins platform and make it
easier to extract information and data from it.
For the first iteration, which is automatically build of interesting
branches, we need to specify:
* Which branches we want to build?
We already build the base branches (stables, testing, devel and
experimental + feature/jessie).
So the questions raised is mostly concern the feature/* and bugfix/*
branches (so topic branches)
The criterias to automatically select the branches to be build could be:
branches which are not merged to devel but has new commits since N weeks
time, 15 days or the previous release.
* Which regularity if needed? (assuming it will be build when a push is
made on it)
- Is a branch built everyday enough? Should it be built more often or
less often?
* How should you be notified?
- Direct e-mail?
- IRC channel?
We're already drafted some scenario's on:
https://tails.boum.org/blueprint/automated_builds_and_tests/autobuild_specs/
Some of you might want to see other one's implemented , so please update
the blueprint accordingly.
Scenarios can range from release managers, developers, reviewers,
testers. Some of these suggestions might not make it this year but will
be looked at in the following year.
Need to keep in mind that the same question will be raised when we'll
design the automated tests.
All the best,
CI team
