[JIRA] (JENKINS-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Jay Ache commented on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites Still not fixed, Blue Ocean 1.21.0, Autofavorite for Blue Ocean 1.2.4, Jenkins 2.150.3 Anyone working on this? I probably have to completely remove Blue Ocean from our pipeline because of this little Autofavorite bug (I can't use Christian Häussler's suggestions of -DBLUEOCEAN_FEATURE_AUTOFAVORITE_ENABLED=false because I don't have admin access to my team's Jenkins instance). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189812.1523357354000.4127.1579766280418%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title
Jay Ache edited a comment on JENKINS-54126
Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Steps to reproduce:1. Create a branch {{testbranch}} that is one commit behind the tip of {{master}} (or some branch that is to be merged into)2. Make a commit to {{testbranch}} that will cause a conflict with the latest on {{master}}.3. In GitHub, create a pull-request for {{testbranch}} to be merged into {{master}}. (It will warn you that it can't be automatically merged, but "don't worry, you can still create the pull-request". (Jenkins Multibranch pipeline will refuse to create a build for both the branch and the PR).4. Rebase {{testbranch}} off the latest on {{master}}, resolve the conflicts, and {{git push origin testbranch --force}}.5. Jenkins Multibranch pipeline will catch that the branch changed, and build the branch, however, it still doesn't sense the pull-request, and refuses to create a build for it.Closing and re-opening the pull-request doesn't help.Closing the pull-request and opening a new one (for the same, conflict-free branch) does work (but is obviously not ideal).{{rm -rf $JENKINS_HOME/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache/*}} does work.I'd also like to state that there indeed was a Jenkinsfile on {{testbranch}}, and that the trigger of this bug is when there's a merge conflict _at the time the pull-request is created_. Jenkins 2.176.2GitHub Source Plugin 2.5.6Pipeline: Multibranch 2.21
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.1406.1566959701783%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Jay Ache commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria Steps to reproduce: 1. Create a branch testbranch that is one commit behind the tip of master (or some branch that is to be merged into) 2. Make a commit to testbranch that will cause a conflict with the latest on master. 3. In GitHub, create a pull-request for testbranch to be merged into master. (It will warn you that it can't be automatically merged, but "don't worry, you can still create the pull-request". (Jenkins Multibranch pipeline will refuse to create a build for both the branch and the PR). 4. Rebase testbranch off the latest on master, resolve the conflicts, and git push origin testbranch --force. 5. Jenkins Multibranch pipeline will catch that the branch changed, and build the branch, however, it still doesn't sense the pull-request, and refuses to create a build for it. Closing and re-opening the pull-request doesn't help. Closing the pull-request and opening a new one (for the same, conflict-free branch) does work (but is obviously not ideal). rm -rf $JENKINS_HOME/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache/* does work. I'd also like to state that there indeed was a Jenkinsfile on testbranch, and that the trigger of this bug is when there's a merge conflict at the time the pull-request is created. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.1318.1566959461892%40Atlassian.JIRA.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Jay Ache edited a comment on JENKINS-47496 Re: No automatic builds for tags I found that adding a Basic Branch Build Strategy to automatically build tags interfered with the rest of the multibranch pipeline builds automatically triggered by GitHub. They were working fine, then I added a Basic Branch Build Strategy to automatically build a tag, added a new tag, the new tag was automatically discovered and it attempted to build it (but failed with a NullPtrException; I had to manually schedule the tag build again before it successfully built, but that's an unrelated issue , probably because of this: https://issues.jenkins-ci.org/browse/JENKINS-50715 ). However, subsequent pushes to branches didn't re-trigger builds as expected. Simply removing the Basic Branch Build Strategy fixed it, and builds/pull-requests were again automatically built whenever pushes happened. I'll try Mark F's JobDSL workaround next. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.1917.1557794400289%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Jay Ache commented on JENKINS-47496 Re: No automatic builds for tags I found that adding a Basic Branch Build Strategy to automatically build tags interfered with the rest of the multibranch pipeline builds automatically triggered by GitHub. They were working fine, then I added a Basic Branch Build Strategy to automatically build a tag, added a new tag, the new tag was automatically discovered and it attempted to build it (but failed with a NullPtrException; I had to manually schedule the tag build again before it successfully built, but that's an unrelated issue). However, subsequent pushes to branches didn't re-trigger builds as expected. Simply removing the Basic Branch Build Strategy fixed it, and builds/pull-requests were again automatically built whenever pushes happened. I'll try Mark F's JobDSL workaround next. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.849.1557739680362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
