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

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 #11801 (closed)

Original created by @anonym on 12559 (Redmine)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information