We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
cert.ci.jenkins.io
The Azure client credentials used by cert.ci.jenkins.io to start Azure VM/Container agents (ref. ) expires on 2 February 2025.
We have to:
2025-02-02T00:00:00Z
⚠️ Once this PR is merged, the deployment of Azure agents on ci.jenkins.io will fail until the Jenkins credential azure-jenkins-sponsorship-credentials (managed manually) is updated - ref. https://github.com/jenkins-infra/jenkins-infra/blob/abf8a194da9247dc955f832162565d9c3322c4b3/hieradata/clients/controller.cert.ci.jenkins.io.yaml#L130
azure-jenkins-sponsorship-credentials
No response
The text was updated successfully, but these errors were encountered:
2025-01-13
plugins.jenkins.io
2025-01-08
2024-10-19
Sorry, something went wrong.
credential rotated successfully, and both verification done, le service principal and the cloud azure vms
No branches or pull requests
Service(s)
cert.ci.jenkins.io
Summary
The Azure client credentials used by cert.ci.jenkins.io to start Azure VM/Container agents (ref. ) expires on 2 February 2025.
We have to:
cert.ci.jenkins.io
expires on2025-02-02T00:00:00Z
azure#920azure-jenkins-sponsorship-credentials
(managed manually) is updated - ref. https://github.com/jenkins-infra/jenkins-infra/blob/abf8a194da9247dc955f832162565d9c3322c4b3/hieradata/clients/controller.cert.ci.jenkins.io.yaml#L130Reproduction steps
No response
The text was updated successfully, but these errors were encountered: