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
plugins.jenkins.io
https://github.com/jenkinsci/accelq-ci-connect-plugin/actions/runs/5947704568/job/16130197723#step:4:41
This a successful build of maven-cd/release job, I expect it to show a new release build in https://plugins.jenkins.io/accelq-ci-connect/releases/
maven-cd/release
Is it correct?
No response
The text was updated successfully, but these errors were encountered:
Hi @accelq , the plugin.jenkins.io deployment is driven by the following pipeline: https://github.com/jenkins-infra/plugin-site/blob/master/Jenkinsfile_k8s.
In particular, https://github.com/jenkins-infra/plugin-site/blob/master/Jenkinsfile_k8s#L55 tells us that it has a 3 hours cron trigger: it means you usually have to wait maximum 3 hours before checking plugins.jenkins.
I've triggererd manually a build to have a delivery for you: it is now delivered: https://plugins.jenkins.io/accelq-ci-connect/releases/
Thanks for contributing to the Jenkins ecosystem!
Sorry, something went wrong.
dduportal
No branches or pull requests
Service(s)
plugins.jenkins.io
Summary
https://github.com/jenkinsci/accelq-ci-connect-plugin/actions/runs/5947704568/job/16130197723#step:4:41
This a successful build of
maven-cd/release
job, I expect it to show a new release build in https://plugins.jenkins.io/accelq-ci-connect/releases/Is it correct?
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: