The shared secrets repo is no up-to-date on Jenkins
Originally created by @anonym on #12559 (Redmine)
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 #12242 (closed) 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.
Related issues
- Is duplicate of sysadmin#11801 (closed)
Edited by anonym