Bug #12559

The shared secrets repo is no up-to-date on Jenkins

Added by anonym 2017-05-18 10:25:55 . Updated 2017-05-18 10:28:05 .

Status:
Duplicate
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Start date:
2017-05-18
Due date:
% Done:

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

We should git fetch && git reset --hard origin/master before each test suite run so new secrets are used without having to ping the sysadmin team to do this manually.

Example: right now some changes done in the feature branch of Feature #12242 depend on new secrets, which I have pushed to the secrets repo, but all affected tests fail because the repo is not kept up-to-date on Jenkins’ isotesters.


Subtasks


Related issues

Is duplicate of Tails - Bug #11801: Use shared-secrets.d instead of TailsToaster_config/common.d Resolved 2016-09-16

History

#1 Updated by intrigeri 2017-05-18 10:27:18

  • is duplicate of Bug #11801: Use shared-secrets.d instead of TailsToaster_config/common.d added

#2 Updated by intrigeri 2017-05-18 10:27:45

  • Status changed from Confirmed to Duplicate

#3 Updated by intrigeri 2017-05-18 10:28:05

  • Assignee deleted (bertagaz)
  • Target version deleted (Tails_3.0)