Project

General

Profile

Feature #14610

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

Added by intrigeri 3 months ago. Updated 7 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Start date:
09/07/2017
Due date:
% Done:

50%

QA Check:
Dev Needed
Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
Affected tool:

Description

… so that he can use #14609 as needed.


Related issues

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

History

#1 Updated by intrigeri 3 months ago

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

#2 Updated by bertagaz about 2 months ago

  • 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 #14609 as needed.

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

#3 Updated by intrigeri about 1 month ago

  • 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 about 1 month ago

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

#5 Updated by intrigeri about 1 month ago

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 about 1 month ago

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 about 1 month ago

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 7 days ago

  • 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 :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.

Also available in: Atom PDF