Feature #6565
Run the test suite automatically on Git push
Start date:
2014-01-03
Due date:
2015-10-15
% Done:
0%
Description
Once we have a platform to run the automated test suite, we can plug it into our Jenkins setup to run it automatically on autobuild ISO images.
Based on the results of Feature #8667:
- write library code that implements the (successful Jenkins ISO build job -> if/what needs to be tested) mapping;
- research and quickly try out the various options available to implement the specified needs with Jenkins; the deliverable is a blueprint comparing these options, proposing a design, and finally leading the discussion towards a decision;
- implement the chosen design.
Zuul might be useful for this.
Subtasks
Related issues
Blocked by Tails - |
Resolved | ||
Blocked by Tails - |
Resolved | 2015-01-10 | 2015-07-15 |
History
#1 Updated by bertagaz 2015-01-10 15:12:58
- blocked by
Feature #8667: Lead a discussion to specify what automatically build ISOs needs to be tested, when and how added
#2 Updated by bertagaz 2015-01-10 15:13:30
- Target version changed from Hardening_M1 to Tails_1.6
#3 Updated by intrigeri 2015-05-28 15:03:01
- blocks #8668 added
#4 Updated by intrigeri 2015-05-28 15:09:26
- Description updated
- Assignee set to bertagaz
#5 Updated by intrigeri 2015-08-02 07:59:50
- Due date set to 2015-10-15
#6 Updated by bertagaz 2015-08-28 09:43:05
- Assignee changed from bertagaz to intrigeri
- QA Check set to Info Needed
Isn’t that a bit of a duplicate of Feature #5288?
#7 Updated by intrigeri 2015-08-30 10:12:58
- Assignee changed from intrigeri to bertagaz
> Isn’t that a bit of a duplicate of Feature #5288?
Indeed. Assuming all child tickets of Feature #5288 are part of the same deliverable, feel free to kill Feature #6565.
#8 Updated by bertagaz 2015-08-31 09:27:23
- Status changed from Confirmed to Duplicate
- Assignee deleted (
bertagaz) - QA Check deleted (
Info Needed)
Duplicate of its parent.