Skip to content
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

Jenkinsfile incompatible with ci.jenkins.io #4

Closed
daniel-beck opened this issue Nov 14, 2017 · 1 comment
Closed

Jenkinsfile incompatible with ci.jenkins.io #4

daniel-beck opened this issue Nov 14, 2017 · 1 comment
Assignees

Comments

@daniel-beck
Copy link
Member

The current Jenkinsfile in praqma/dev is incompatible with ci.jenkins.io (the CI instance of the Jenkins project that builds all plugins in the @jenkinsci organization) by selecting a node label that just doesn't exist. This adds queue items that never start.

screen shot

Since we're using a GH org folder, our ability to configure individual projects is limited.

While I personally would advocate for just using that Jenkins instance for all your CI needs, a quick fix could be to just return from the Jenkinsfile if the JENKINS_URL.contains('.jenkins.io') or similar.

@ewelinawilkosz
Copy link
Contributor

oops, wasn't aware that it ends up on your Jenkins. I used your advice. and you're right, I we'll try to move it to ci.jenkins.io soon

LinuxSuRen pushed a commit to LinuxSuRen/configuration-as-code-plugin that referenced this issue Dec 24, 2019
Fix the potential issues from a static field
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants