-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
401 during CD deployment #4382
Comments
I think it might be all plugins for which CD is broken: https://github.com/jenkinsci/jenkins-infra-test-plugin/actions/runs/11732201191/job/32683942682 |
Confirmed what @jglick says: token and username seems to have stopped being updated on GitHub side |
Audit trail:
=> Looks like the Artifactory token is invalid or expired, as they were no code change in RPU |
Confirmed the Artifactory admin token was expired. It looks like I did forget to put a reminder in #4203. |
|
Update:
=> CD is back |
Confirmed it worked for https://github.com/jenkinsci/jenkins-infra-test-plugin/actions/runs/11732201191 |
created #4383 for monitoring |
Ah ah I was writing an issue for this, thanks Tim! ❤️ Also Added a calendar event for the team |
Yuck, does it not support OIDC? |
In theory yes: https://jfrog.com/help/r/jfrog-platform-administration-documentation/configure-an-oidc-integration I'm not sure about the effort required to have it used on such a sensitive system though (compared to rotating a token every 3 months) |
Service(s)
Artifactory
Summary
I am getting 401 errors trying to deploy CD releases of
workflow-job
. Most recently: https://github.com/jenkinsci/workflow-job-plugin/actions/runs/11731857921/job/32682817656Acc. to https://github.com/jenkinsci/workflow-job-plugin/settings/secrets/actions the
MAVEN_TOKEN
is 9h old. Should it have been refreshed more recently?Reproduction steps
No response
The text was updated successfully, but these errors were encountered: