Project

General

Profile

Feature #10492

Feature #10153: Automated tests: phase two

Decide if Jenkins should test our documentation branches

Added by bertagaz about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Continuous Integration
Target version:
Start date:
11/05/2015
Due date:
% Done:

100%

Feature Branch:
Type of work:
Discuss
Blueprint:
Starter:
No
Affected tool:

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


Related issues

Related to Tails - Feature #9760: Prioritize builds from release branches over others Confirmed 07/19/2015
Related to Tails - Feature #10707: Test only @doc scenarios for documentation branches Resolved 12/03/2015
Blocks Tails - Feature #10706: Tag scenarios that rely on the shipped documentation Resolved 12/03/2015

History

#2 Updated by bertagaz about 4 years ago

  • Description updated (diff)

#3 Updated by intrigeri about 4 years ago

  • Starter changed from Yes to No

#5 Updated by bertagaz about 4 years ago

  • 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 about 4 years ago

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 about 4 years ago

  • Related to Feature #9760: Prioritize builds from release branches over others added

#8 Updated by intrigeri about 4 years ago

  • 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 about 4 years ago

  • Blocks Feature #10706: Tag scenarios that rely on the shipped documentation added

#10 Updated by bertagaz about 4 years ago

  • Related to Feature #10707: Test only @doc scenarios for documentation branches added

#11 Updated by bertagaz about 4 years ago

  • 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 about 4 years ago

  • 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

Also available in: Atom PDF