Feature #10492
Decide if Jenkins should test our documentation branches
Start date:
2015-11-05
Due date:
% Done:
100%
Description
During the first stage of deployment, some of us raised the question about deciding if we want our doc/
and web/
branches to be tested in Jenkins. There are pros and cons and we need to decide something about that, and the way we would implement it.
See https://mailman.boum.org/pipermail/tails-dev/2015-October/009645.html
Subtasks
Related issues
Related to Tails - Feature #9760: Prioritize builds from release branches over others | Confirmed | 2015-07-19 | |
Related to Tails - |
Resolved | 2015-12-03 | |
Blocks Tails - |
Resolved | 2015-12-03 |
History
#1 Updated by bertagaz 2015-11-06 04:36:22
- blocks #8668 added
#2 Updated by bertagaz 2015-11-06 04:37:09
- Description updated
#3 Updated by intrigeri 2015-11-06 07:35:53
- Starter changed from Yes to No
- Deliverable for changed from 268 to 267
#5 Updated by bertagaz 2015-11-18 04:36:27
- Status changed from Confirmed to In Progress
- Assignee changed from bertagaz to intrigeri
- % Done changed from 0 to 50
- QA Check set to Info Needed
#6 Updated by intrigeri 2015-12-01 10:57:01
Data point — in November, among 314 non-aborted ISO test suite runs, 24% (75) were about branches whose name starts with “doc” or “web”.
#7 Updated by intrigeri 2015-12-01 12:24:29
- related to Feature #9760: Prioritize builds from release branches over others added
#8 Updated by intrigeri 2015-12-01 12:28:54
- Assignee changed from intrigeri to bertagaz
- % Done changed from 50 to 60
- QA Check changed from Info Needed to Dev Needed
Replied on the ML, summed up there what’s left to do before we can close this ticket.
#9 Updated by bertagaz 2015-12-03 07:04:49
- blocks
Feature #10706: Tag scenarios that rely on the shipped documentation added
#10 Updated by bertagaz 2015-12-03 07:14:02
- related to
Feature #10707: Test only @doc scenarios for documentation branches added
#11 Updated by bertagaz 2015-12-03 07:23:19
- Assignee changed from bertagaz to intrigeri
- % Done changed from 60 to 80
- QA Check changed from Dev Needed to Ready for QA
Reassigning for review as asked on the ML. See related tickets for more.
#12 Updated by intrigeri 2015-12-05 10:07:52
- Status changed from In Progress to Resolved
- Assignee deleted (
intrigeri) - % Done changed from 80 to 100
- QA Check changed from Ready for QA to Pass