Feature #14610

Give anonym read-write access to jenkins-jobs.git

Added by intrigeri 2017-09-07 14:25:39 . Updated 2018-02-26 12:32:15 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Tails_3.6
Start date:
2017-09-07
Due date:
% Done:

100%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

… so that he can use Bug #14609 as needed.

Subtasks

Related issues

Blocks Tails - Feature #14611: Evaluate the global --old-iso kill switch for the test suite on Jenkins Resolved 2017-09-07

History

#1 Updated by intrigeri 2017-09-07 14:28:51

  • blocks Feature #14611: Evaluate the global --old-iso kill switch for the test suite on Jenkins added

#2 Updated by bertagaz 2017-10-13 12:48:39

  • Status changed from Confirmed to In Progress
  • Assignee changed from bertagaz to anonym
  • % Done changed from 0 to 50
  • QA Check set to Ready for QA

intrigeri wrote:
> … so that he can use Bug #14609 as needed.

Done. anonym, can you check you can clone gitolitegit.puppet.tails.boum.org:jenkins-jobs@. The doc about how to use the old-iso switch has been documented in commit:8c2a584 in the Tails repo.

#3 Updated by intrigeri 2017-11-06 15:30:03

  • Target version changed from Tails_3.3 to Tails_3.5

(making anonym’s plate lighter; this can wait a bit more)

#4 Updated by anonym 2017-11-07 13:29:52

The release process should have a step about this in the Prepare for the next release section.

#5 Updated by intrigeri 2017-11-07 14:08:49

> The release process should have a step about this in the Prepare for the next release section.

What would this step be about?

#6 Updated by anonym 2017-11-07 14:14:32

intrigeri wrote:
> > The release process should have a step about this in the Prepare for the next release section.
>
> What would this step be about?

Never mind. The switch should be turned as soon as a Tails Installer is uploaded (so it affects some branch on Jenkins) whose UI changes breaks the tests, not when a new Tails is released.

#7 Updated by intrigeri 2017-11-07 14:45:35

> Never mind. The switch should be turned as soon as a Tails Installer is uploaded (so
> it affects some branch on Jenkins) whose UI changes breaks the tests, not when a new
> Tails is released.

Yes, and a ticket filed to revert this change as soon as it’s done.

#8 Updated by anonym 2017-12-04 10:43:29

  • Assignee changed from anonym to bertagaz
  • QA Check changed from Ready for QA to Dev Needed

Eh, seems I forgot to answer the actual question:

bertagaz wrote:
> anonym, can you check you can clone gitolite@git.puppet.tails.boum.org:jenkins-jobs.

Yes!

> The doc about how to use the old-iso switch has been documented in 8c2a584 in the Tails repo.

All clear!

Reassigning back in case any more steps are needed on your side.

#9 Updated by anonym 2018-01-23 19:52:51

  • Target version changed from Tails_3.5 to Tails_3.6

#10 Updated by bertagaz 2018-02-26 12:32:15

  • Status changed from In Progress to Resolved
  • Assignee deleted (bertagaz)
  • % Done changed from 50 to 100
  • QA Check changed from Dev Needed to Pass

Nothing more to do here, so closing this ticket.