[JIRA] (JENKINS-1858) Support ability to do grid type computing
Title: Message Title John McGehee commented on JENKINS-1858 Re: Support ability to do grid type computing I am the maintainer of the Jenkins SGE plugin. From time to time people ask me about creating a Condor version. My recommendation is to start with the Jenkins SGE plugin, then replace the SGE commands it sends with Condor commands. No official Jenkins Condor Plugin has materialized, but potential candidates do turn up in a search of GitHub. Good luck. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title John McGehee commented on JENKINS-43052 Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects Maybe some more–or all–of these options should be removed when the project type is Pipeline. Jesse Glick, perhaps you meant, "...are obsolete and should be considered..." Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title John McGehee closed an issue as Won't Fix This is a git-plugin issue, not a Pipeline issue. Created Check out to a sub-directory" for Pipeline projects" class="issue-link" data-issue-key="JENKINS-43052" style="color: #3b73af; text-decoration: none">JENKINS-43052 per Jesse Glick's suggestion. Jenkins / JENKINS-40267 Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory Change By: John McGehee Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit
[JIRA] (JENKINS-43052) Disallow *Additional Behaviors > Check out to a sub-directory* for Pipeline projects
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-43052 Disallow *Additional Behaviors > Check out to a sub-directory* for Pipeline projects Change By: John McGehee Summary: Allow Disallow * Additional Behaviors > Check out to a sub-directory only if the AncestorInPath is an AbstractProject * for Pipeline projects Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-43052 Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects Change By: John McGehee Summary: Disallow * " Additional Behaviors > Check out to a sub-directory * " for Pipeline projects Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Allow Additional Behaviors > Check out to a sub-directory only if the AncestorInPath is an AbstractProject
Title: Message Title
John McGehee created an issue
Jenkins / JENKINS-43052
Allow Additional Behaviors > Check out to a sub-directory only if the AncestorInPath is an AbstractProject
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2017/Mar/22 10:19 PM
Environment:
Jenkins ver. 2.19.2 Pipeline 2.4 Pipeline: Multibranch 2.9 Ubuntu 16 LTS
Priority:
Minor
Reporter:
John McGehee
Additional Behaviors > Check out to a sub-directory clones Jenkinsfile in the specified directory. Meanwhile, Jenkins itself continues to look for Jenkinsfile at the top of the workspace. This is very confusing. As far as I can see, Additional Behaviors > Check out to a sub-directory is never appropriate with Pipeline. This should be handled in Jenkinsfile using dir():
dir('subDir') {
checkout scm
}
In JENKINS-40267, Jesse Glick suggested that git-plugin should conditionally display the Additional Behaviors > Check out to a sub-directory option only if the AncestorInPath is an AbstractProject.
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title John McGehee commented on JENKINS-40267 Re: Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory I agree that the workaround is the correct approach. I would suggest that you disable Additional Behaviors > Check out to a sub-directory option so that nobody can get into that strange situation that I got myself into. However I do not care to press the issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40267
Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Change By:
John McGehee
h2. Problem Description Without _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins clones in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace. That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation. h2. Symptom When at first you do not use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you change your mind and start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory. h2. Workaround First, do not use _Additional Behaviors > Check out to a sub-directory_ in the Multibranch Pipeline Configuration.In Jenkinsfile, check out the main repository in the subdirectory using dir():{code:java} dir('subDir') {checkout scm}{code} See my StackOverflow answer for a [discussion of checking out additional repositories|http://stackoverflow.com/a/40392423/2850565].
Add Comment
[JIRA] (JENKINS-40492) How does a Groovy external library get its name?
Title: Message Title John McGehee closed an issue as Fixed Thank you for accepting my documentation. I hope you found it helpful. Jenkins / JENKINS-40492 How does a Groovy external library get its name? Change By: John McGehee Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41116) Instructions for slack-plugin out of date on Jenkins wiki
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-41116 Instructions for slack-plugin out of date on Jenkins wiki Change By: John McGehee I spent quite a while trying to get Slack notifications working based on the [instructions on the Jenkins Wiki|https://wiki.jenkins-ci.org/display/JENKINS/Slack+Plugin]. They do not work.The instructions on GitHub work great, so I added the following warning to the Jenkins Wiki page:bq. The instructions presented below are incomplete. Follow the instructions on the Slack Plugin's GithHub home page. They work great. bq. Please shorten the Jenkins Wiki instructions to refer the user to GitHub.*If you agree that this should be done, just assign this issue to me, and I will edit the Jenkins wiki for you.* Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-41116) Instructions for slack-plugin out of date on Jenkins wiki
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-41116 Instructions for slack-plugin out of date on Jenkins wiki Change By: John McGehee I spent quite a while trying to get Slack notifications working based on the [instructions on the Jenkins Wiki|https://wiki.jenkins-ci.org/display/JENKINS/Slack+Plugin]. They do not work.The instructions on GitHub work great, so I added the following warning to the Jenkins Wiki page: > bq. The instructions presented below are incomplete. Follow the instructions on the Slack Plugin's GithHub home page. They work great. bq. Please shorten the Jenkins Wiki instructions to refer the user to GitHub.*If you agree that this should be done, just assign this issue to me, and I will edit the Jenkins wiki for you.* Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-41116) Instructions for slack-plugin out of date on Jenkins wiki
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-41116 Instructions for slack-plugin out of date on Jenkins wiki Change By: John McGehee Summary: Instructions for slack-plugin out of date on Jenkins wiki Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41116) Instructions out of date on Jenkins wiki
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-41116 Instructions out of date on Jenkins wiki Change By: John McGehee I spent quite a while trying to get Slack notifications working based on the [instructions on the Jenkins Wiki|https://wiki.jenkins-ci.org/display/JENKINS/Slack+Plugin]. They do not work.The instructions on GitHub work great, so I added the following warning to the Jenkins Wiki page:> The instructions presented below are incomplete. Follow the instructions on the Slack Plugin's GithHub home page. They work great.Please shorten the Jenkins Wiki instructions to refer the user to GitHub.*If you agree that this should be done, just assign this issue to me, and I will edit the Jenkins wiki for you.* Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-41116) Instructions out of date on Jenkins wiki
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-41116 Instructions out of date on Jenkins wiki Change By: John McGehee Summary: Jenkins wiki instructions Instructions out of date on Jenkins wiki Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41116) Jenkins wiki instructions out of date
Title: Message Title John McGehee created an issue Jenkins / JENKINS-41116 Jenkins wiki instructions out of date Issue Type: Bug Assignee: Kurt Madel Components: slack-plugin Created: 2017/Jan/17 12:53 AM Priority: Minor Reporter: John McGehee I spent quite a while trying to get Slack notifications working based on the instructions on the Jenkins Wiki. They do not work. The instructions on GitHub work great, so I added the following warning to the Jenkins Wiki page: > The instructions presented below are incomplete. Follow the instructions on the Slack Plugin's GithHub home page. They work great. Please shorten the Jenkins Wiki instructions to refer the user to GitHub. If you agree that this be done, just assign this issue to me, and I will edit the Jenkins wiki for you. Add Comment
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title John McGehee edited a comment on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time [~ db danielbeck ], I completely understand your dilemma. I modified my 11 Jan comment to explain the behavior I expected.It is nice to hear from you. I recall fondly our conversations at Jenkins World 2015 and 2016. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title John McGehee commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time David Bottger, I completely understand your dilemma. I modified my 11 Jan comment to explain the behavior I expected. It is nice to hear from you. I recall fondly our conversations at Jenkins World 2015 and 2016. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title
John McGehee edited a comment on JENKINS-24638
Re: No E-Mail sent when build of new branch fails for first time
I encountered this same issue with Jenkins 2.19.2, and email-ext 2.52. I did some further experiments, and my results contradict some of the previous comments.I am running {{email-ext}} as described in [Sending Notifications in Pipeline|https://jenkins.io/blog/2016/07/18/pipline-notifications/]. As part of my experiments, I used all the recipient providers I know:{code} def recipients = [[$class: 'CulpritsRecipientProvider'], [$class: 'UpstreamComitterRecipientProvider'], [$class: 'RequesterRecipientProvider'], [$class: 'DevelopersRecipientProvider'], [$class: 'FailingTestSuspectsRecipientProvider'], [$class: 'FirstFailingBuildSuspectsRecipientProvider']]{code}I tried two scenarios.h3. Push without modificationI started with a branch into which I had purposely introduced a failure. When Jenkins builds this failing branch, it sends a notification email. I created a new branch, and pushed it without modification:{code}git checkout -b notifybuild4git push --set-upstream origin notifybuild4{code}Jenkins built this new branch and failed as expected, but no email was sent, because the providers yielded no recipients:bq. An attempt to send an e-mail to empty list of recipients, ignored.Building branch notifybuild4 a second time resulted in an email being sent. I expected the recipient providers to yield the same email addresses in all these situations:* When the original branch was built (this works)* When branch notifybuild4 was first pushed (this does not work)* When branch notifybuild4 was re-built (this works) h3. Push with modificationStarting with branch notifybuild4 (which fails as described above), I created a new branch, made an immaterial change and and pushed it:{code}git checkout -b notifybuild5atom Jenkinsfile# Add an empty linegit add Jenkinsfile git commitgit push --set-upstream origin notifybuild5{code}Once again, Jenkins' build of this new branch failed as expected, but no email was sent, because the providers yielded no recipients according to the console output from {{email-ext}}:bq. An attempt to send an e-mail to empty list of recipients, ignored.Building branch notifybuild5 a second time resulted in an email being sent. I expected the recipient providers to yield the same email addresses in all these situations: * When branch notifybuild4 was rebuilt (this works)* When branch notifybuild5 was first pushed (this does not work)* When branch notifybuild5 was re-built (this works)
Add Comment
[JIRA] (JENKINS-24638) No E-Mail sent when build of new branch fails for first time
Title: Message Title John McGehee commented on JENKINS-24638 Re: No E-Mail sent when build of new branch fails for first time I encountered this same issue with Jenkins 2.19.2, and email-ext 2.52. I did some further experiments, and my results contradict some of the previous comments. I am running email-ext as described in Sending Notifications in Pipeline. As part of my experiments, I used all the recipient providers I know: def recipients = [[$class: 'CulpritsRecipientProvider'], [$class: 'UpstreamComitterRecipientProvider'], [$class: 'RequesterRecipientProvider'], [$class: 'DevelopersRecipientProvider'], [$class: 'FailingTestSuspectsRecipientProvider'], [$class: 'FirstFailingBuildSuspectsRecipientProvider']] I tried two scenarios. Push without modification I started with a branch into which I had purposely introduced a failure. I created a new branch, and pushed it without modification: git checkout -b notifybuild4 git push --set-upstream origin notifybuild4 Jenkins built this new branch and failed as expected, but no email was sent, because the providers yielded no recipients: An attempt to send an e-mail to empty list of recipients, ignored. Building branch notifybuild4 a second time resulted in an email being sent. Push with modification Starting with branch notifybuild4 (which fails as described above), I created a new branch, made an immaterial change and and pushed it: git checkout -b notifybuild5 atom Jenkinsfile# Add an empty line git add Jenkinsfile git commit git push --set-upstream origin notifybuild5 Once again, Jenkins' build of this new branch failed as expected, but no email was sent, because the providers yielded no recipients according to the console output from email-ext: An attempt to send an e-mail to empty list of recipients, ignored. Building branch notifybuild5 a second time resulted in an email being sent.
[JIRA] (JENKINS-40492) How does a Groovy external library get its name?
Title: Message Title John McGehee commented on JENKINS-40492 Re: How does a Groovy external library get its name? Ju Ba, see Using Libraries in the documentation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40267
Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Change By:
John McGehee
h2. Problem DescriptionWithout _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins clones in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace.That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation.h2. SymptomWhen at first you do not use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory.h2. WorkaroundFirst, do not use _Additional Behaviors > Check out to a sub-directory_ in the Multibranch Pipeline Configuration.In {{ Jenkinsfile }} , {{stash}} check out the repo main repository in the workspace directory, and {{unstash}} it into a subdirectory using dir() :{code:java} stage dir ( "setup" 'subDir' ) { node("sw") {deleteDir() checkout scm stash name: "repo" } }stage("test") { node("sw") {deleteDir()dir("subdir") {unstash "repo" code } See my StackOverflow answer for a [discussion of checking out additional repositories|http: // Test stuff}}{code} stackoverflow.com/a/40392423/2850565].
Add Comment
[JIRA] (JENKINS-40492) How does a Groovy external library get its name?
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-40492 How does a Groovy external library get its name? Change By: John McGehee Comment: Now that I see how the library name is used, I cannot believe that it was not obvious earlier. Anyway, in [PR #24|JENKINS-40492] I added some explanation to make sure that is absolutely clear. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40492) How does a Groovy external library get its name?
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40492
How does a Groovy external library get its name?
Change By:
John McGehee
The [documentation|https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md#using-libraries] says:bq. @Library('somelib') From At first, I could not understand from where does this library name "somelib" come?This needs to be added to the documentation came . If Now that I see how the documentation cannot be updated soon library name is defined and used , quick answer here would be nice I cannot believe that it was not obvious to me earlier . Anyway, in [PR #24|JENKINS-40492] I would happy added some explanation to write the documentation make sure that is absolutely clear. The only task left for you is to review and submit a accept the pull request. Thank you.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-40492) How does a Groovy external library get its name?
Title: Message Title John McGehee commented on JENKINS-40492 Re: How does a Groovy external library get its name? Now that I see how the library name is used, I cannot believe that it was not obvious earlier. Anyway, in PR #24 I added some explanation to make sure that is absolutely clear. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40492) How does a Groovy external library get its name?
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40492
How does a Groovy external library get its name?
Change By:
John McGehee
The [documentation|https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md#using-libraries] says:bq. @Library('somelib')From where does this library name "somelib" come?This needs to be added to the documentation. If the documentation cannot be updated soon, quick answer here would be nice. I would happy to write the documentation for you and submit a pull request. Thank you.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40492) How does a Groovy external library get its name?
Title: Message Title
John McGehee created an issue
Jenkins / JENKINS-40492
How does a Groovy external library get its name?
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-cps-global-lib-plugin
Created:
2016/Dec/16 12:35 AM
Priority:
Minor
Reporter:
John McGehee
The documentation says:
@Library('somelib')
From where does this library name "somelib" come? This needs to be added to the documentation. If the documentation cannot be updated soon, quick answer here would be nice. Thank you.
Add Comment
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40267
Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Change By:
John McGehee
h2. Problem DescriptionWithout _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins clones in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace.That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation.h2. SymptomWhen at first you do not use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory.h2. WorkaroundFirst, do not use _Additional Behaviors > Check out to a sub-directory_ in the Multibranch Pipeline Configuration. Then, in In {{Jenkinsfile}}, {{stash}} the repo in the workspace directory, and {{unstash}} it into a subdirectory:{code:java}stage("setup") {node("sw") {deleteDir()checkout scmstash name: "repo"}}stage("test") {node("sw") {deleteDir()dir("subdir") {unstash "repo" }// Test stuff}}{code}
Add Comment
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40267
Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Change By:
John McGehee
h2. Problem DescriptionWithout _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins does clone clones in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace. Originally I was thinking that the {{Jenkinsfile}} reader should track _Additional Behaviors > Check out to a sub - directory_, but after gaining some experience with --- - That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation.h2. Symptom If you When at first you do * not * use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory. Pretty darn hard to diagnose... h2. WorkaroundFirst, do not use _Additional Behaviors > Check out to a sub-directory_ in the Multibranch Pipeline Configuration.Then, in {{Jenkinsfile}}, {{stash}} the repo in the workspace directory, and {{unstash}} it into a subdirectory:{code:java}stage("setup") {node("sw") {deleteDir()checkout scmstash name: "repo"}}stage("test") {node("sw") {deleteDir()dir("subdir") {unstash "repo" }// Test stuff}}{code}
Add Comment
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40267
Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Change By:
John McGehee
h2. Problem Description Without _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins does clone in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace. Originally I was thinking that the {{Jenkinsfile}} reader should track _Additional Behaviors > Check out to a sub - directory_, but after gaining some experience with --- - That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation. h2. Symptom If you first do *not* use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory. Pretty darn hard to diagnose... h2. WorkaroundFirst, do not use _Additional Behaviors > Check out to a sub-directory_ in the Multibranch Pipeline Configuration.Then, in {{Jenkinsfile}}, {{stash}} the repo in the workspace directory, and {{unstash}} it into a subdirectory:{code:java}stage("setup") {node("sw") {deleteDir()checkout scmstash name: "repo"}}stage("test") {node("sw") {deleteDir()dir("subdir") {unstash "repo" }// Test stuff}}{code}
Add Comment
[JIRA] (JENKINS-39861) Jenkinsfile path of Multibranch pipeline
Title: Message Title John McGehee commented on JENKINS-39861 Re: Jenkinsfile path of Multibranch pipeline Users, watch out for the problem I reported in JENKINS-40267. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-40267
Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Change By:
John McGehee
Without _Additional Behaviors > Check out to a sub-directory_, Jenkins can find my {{Jenkinsfile}}.If I add _Additional Behaviors > Check out to a sub-directory_, Jenkins does clone in the specified directory, but it still looks for {{Jenkinsfile}} at the top of the workspace. That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation.If you first do *not* use _Additional Behaviors > Check out to a sub-directory_ a {{Jenkinsfile}} will be placed at the top of the workspace, and everything will work as expected.Then if you start using _Additional Behaviors > Check out to a sub-directory_, Jenkins will forever use your old {{Jenkinsfile}} that remains at the top of the workspace--Jenkins will not see any updates to the {{Jenkinsfile}} that now appears in the sub-directory. Pretty darn hard to diagnose...
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title John McGehee created an issue Jenkins / JENKINS-40267 Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2016/Dec/07 1:44 AM Environment: Jenkins ver. 2.19.2 Pipeline 2.4 Pipeline: Multibranch 2.9 Ubuntu 16 LTS Priority: Major Reporter: John McGehee Without Additional Behaviors > Check out to a sub-directory, Jenkins can find my Jenkinsfile. If I add Additional Behaviors > Check out to a sub-directory, Jenkins does clone in the specified directory, but it still looks for Jenkinsfile at the top of the workspace. That's all for the bug report. I add the following for the sake of users who are experiencing the particular way that this problem manifests, and are searching for an explanation. If you first do not use Additional Behaviors > Check out to a sub-directory a Jenkinsfile will be placed at the top of the workspace, and everything will work as expected. Then if you start using Additional Behaviors > Check out to a sub-directory, Jenkins will forever use your old Jenkinsfile that remains at the top of the workspace--Jenkins will not see any updates to the Jenkinsfile that now appears in the sub-directory. Pretty darn hard to diagnose...
[JIRA] (JENKINS-18464) Build Pipeline and Join plugin do not play nicely together
Title: Message Title John McGehee edited a comment on JENKINS-18464 Re: Build Pipeline and Join plugin do not play nicely together After attending At the Jenkins World conference over the past two days, I think it might be better saw the community moving to use the new _Pipeline_ functionality in place of the mashup of plugins that we have historically had to use. With _Pipeline_ I see dim prospects for further development on the scene these plugins , I suspect that piecemeal solutions like the _Build Pipeline_ and _Join_ plugin will become obsolete which have been superseded by _Pipeline_ . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18464) Build Pipeline and Join plugin do not play nicely together
Title: Message Title John McGehee commented on JENKINS-18464 Re: Build Pipeline and Join plugin do not play nicely together After attending Jenkins World over the past two days, I think it might be better to use the new Pipeline functionality in place of the mashup of plugins that we have historically had to use. With Pipeline on the scene, I suspect that piecemeal solutions like the Build Pipeline and Join plugin will become obsolete. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34284) Web hook http://JENKINS_URL/project/PROJECT_NAME fails
Title: Message Title John McGehee closed an issue as Fixed The solution was remarkably simple. I mistakenly used the GitLab project name. It is the Jenkins project name, including any folders, that should be specified. I added this to the GitLab Plugin documentation and issued pull request #414. Jenkins / JENKINS-34284 Web hook http://JENKINS_URL/project/PROJECT_NAME fails Change By: John McGehee Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-34284) Web hook http://JENKINS_URL/project/PROJECT_NAME fails
Title: Message Title
John McGehee updated an issue
Jenkins / JENKINS-34284
Web hook http://JENKINS_URL/project/PROJECT_NAME fails
Change By:
John McGehee
I am trying to set up the Jenkins GitLab plugin. The [GitLab plugin installation instructions|https://github.com/jenkinsci/gitlab-plugin] say to use the web hook {{http://JENKINS_URL/project/PROJECT_NAME}}. Upon testing this hook in GitLab, Jenkins responds with the giant stack trace shown below.I tried the more standard web hook {{http://JENKINS-SERVER/git/notifyCommit?url=""> infra2 SERVER :GROUP/REPO.git}} in GitLab and it did work for ordinary pushes to the source repository. However, when this web hook gets used on merge requests, the Jenkins job is triggered but it fails, complaining:{code}Error fetching remote repo '${gitlabSourceRepoName}'{code}I suppose this is because {{http://JENKINS-SERVER/git/notifyCommit?url=""> infra2 SERVER :GROUP/REPO.git}} triggers Jenkins directly, circumventing the GitLab plugin, which would define variable {{gitlabSourceRepoName}}.[Toward the end of the installation instructions|https://github.com/jenkinsci/gitlab-plugin#help-needed], there are words that cast doubt on whether {{http://JENKINS_URL/project/PROJECT_NAME}} actually does work.-Here is the stack trace mentioned above:{code}Hook execution failed: Jenkins [Jenkins]var isRunAsTest=false; var rootURL=""; var resURL="/static/2ea7aded";crumb.init("", "");var Q=jQuery.noConflict()Skip to content log in createSearchBox("/search/");Jenkins Jenkins project Bug tracker Mailing Lists Twitter: @jenkinsci Oops!A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] (JENKINS-37096) Exception when adding New Node of type SGE Slave
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-37096 Exception when adding New Node of type SGE Slave Change By: John McGehee Summary: Expection Exception when adding a New Node of type SGE node Slave Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37096) Exception when adding New Node of type SGE Slave
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-37096 Exception when adding New Node of type SGE Slave Change By: John McGehee Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37096) Expection when adding a SGE node
Title: Message Title John McGehee edited a comment on JENKINS-37096 Re: Expection when adding a SGE node I apologize for the late response.The [installation instructions|https://wiki.jenkins-ci.org/display/JENKINS/SGE+Cloud+Plugin] call for adding an _SGE Cloud_, not a _New Node_ of type _SGE Slave_. Please follow the installation instructions and tell me if that works.Still, the presence of a useless button that causes a crash is certainly a bad thing. Thank you for reporting it. I tried the same thing as you on RHEL 6.5, and I too got an exception, although Jenkins would not show me the stack trace.After you confirm that you were able to get the Jenkins SGE Cloud Plugin working without adding a _New Node_ of type _SGE Slave_, I will remove the useless (and dangerous) _SGE Slave_ button. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37096) Expection when adding a SGE node
Title: Message Title John McGehee commented on JENKINS-37096 Re: Expection when adding a SGE node I apologize for the late response. The installation instructions call for adding an SGE Cloud, not a New Node of type SGE Slave. Please follow the installation instructions and tell me if that works. Still, the presence of a useless button that causes a crash is certainly a bad thing. Thank you for reporting it. I tried the same thing as you on RHEL 6.5, and I too got an exception, although Jenkins would not show me the stack trace. After you confirm that you were able to get the Jenkins SGE Plugin working without adding a New Node of type SGE Slave, I will remove the useless (and dangerous) SGE Slave button. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
