[JIRA] (JENKINS-41840) Add pipeline support for rich-text-publisher-plugin
Title: Message Title Moritz Wirger assigned an issue to Dmitry Korotkov Jenkins / JENKINS-41840 Add pipeline support for rich-text-publisher-plugin Change By: Moritz Wirger Assignee: Dmitry Korotkov 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-41840) Add pipeline support for rich-text-publisher-plugin
Title: Message Title Moritz Wirger commented on JENKINS-41840 Re: Add pipeline support for rich-text-publisher-plugin Well when I created the issue it was set to auto assign and rich-text-publisher-plugin is the right component, but I think that Dmitry Korotkov is not maintaining it anymore and all that needs to be done is to accept the pull request. 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-40621) MavenEmbedderUtils#getMavenVersion() leaks file descriptors
Title: Message Title Oleg Nenashev commented on JENKINS-40621 Re: MavenEmbedderUtils#getMavenVersion() leaks file descriptors Arnaud Héritier should we also bump the dependnecy on maven-plugin in the Artifactory plugin? I suppose we can leave it as is since the issue is not severe 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-41264) better javadocs for new remoting protocol
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41264 Re: better javadocs for new remoting protocol Code changed in jenkins User: Valentina Armenise Path: core/src/main/java/jenkins/slaves/JnlpAgentReceiver.java http://jenkins-ci.org/commit/jenkins/a9e72abe4fdb3f6c9fbaca62027f4a135d063d7b Log: [FIX JENKINS-41264] followup fixing methods' references in javadoc 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-42084) Errors when "wait for completion" is ticked
Title: Message Title
Phil Rumble created an issue
Jenkins / JENKINS-42084
Errors when "wait for completion" is ticked
Issue Type:
Bug
Assignee:
Christian McHugh
Components:
saltstack-plugin
Created:
2017/Feb/16 6:49 AM
Priority:
Blocker
Reporter:
Phil Rumble
I . get this error Started by user anonymous Building in workspace /var/lib/jenkins/jobs/salt-test/workspace ERROR: { "_links": {"jobs": []} , "return": [{}] } ERROR: {"Error": "java.io.IOException: Server returned HTTP response code: 401 for URL: http://172.16.42.10:8000/jobs/\n\tat sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)\n\tat sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)\n\tat com.waytta.Utils.getJSON(Utils.java:69)\n\tat com.waytta.Builds.runBlockingBuild(Builds.java:97)\n\tat com.waytta.SaltAPIBuilder.performRequest(SaltAPIBuilder.java:253)\n\tat com.waytta.SaltAPIBuilder.perform(SaltAPIBuilder.java:201)\n\tat com.waytta.SaltAPIBuilder.perform(SaltAPIBuilder.java:161)\n\tat hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)\n\tat hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)\n\tat hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)\n\tat hudson.model.Build$BuildExecution.build(Build.java:206)\n\tat hudson.model.Build$BuildExecution.doRun(Build.java:163)\n\tat hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)\n\tat hudson.model.Run.execute(Run.java:1728)\n\tat hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)\n\tat hudson.model.ResourceController.execute(ResourceController.java:98)\n\tat hudson.model.Executor.run(Executor.java:405)\n"} Response on test.ping for '*': [{}] Build step 'Send a message to Salt API' changed build result to FAILURE Finished: FAILURE
[JIRA] (JENKINS-42024) Silent error : UnsupportedOperationExceptions are not raised when using each/find
Title: Message Title Lucas Cimon commented on JENKINS-42024 Re: Silent error : UnsupportedOperationExceptions are not raised when using each/find OK. Thanks for your answer. I have some questions: when and where is the sandbox mode "ON" ? Whenever a Jenkinsfile in executed ? Only when you "Replay" it ? is it possible to detect this outside Jenkins, in a "static code analysis" phase, or maybe when running unit tests ? 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-38752) The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-38752 The job link in the detail view for multibranch should link to a filtered activity list of appropriate branch Change By: James Dumay Assignee: Ivan Meredith 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-38460) Move toasts from bottom left to bottom right
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-38460 Move toasts from bottom left to bottom right Change By: James Dumay Assignee: Ivan Meredith 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-39893) Enable findbugs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39893 Enable findbugs Change By: James Dumay Sprint: panthalassa up next 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-41087) When the user wants to create classic pipelines
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41087 When the user wants to create classic pipelines Change By: Michael Neale Priority: Minor 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-41087) When the user wants to create classic pipelines
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41087 When the user wants to create classic pipelines Change By: James Dumay Sprint: tethys, pannonian, panthalassa iapetus 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-41437) How to disable standard message?
Title: Message Title Martin Reinhardt commented on JENKINS-41437 Re: How to disable standard message? you can disable the message via rawMessage: rocketSend channel: 'general', message: 'My message', rawMessage: true 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-41437) How to disable standard message?
Title: Message Title Martin Reinhardt closed an issue as Fixed Jenkins / JENKINS-41437 How to disable standard message? Change By: Martin Reinhardt 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 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-41650) More documentation on setting up rocketchatnotifier
Title: Message Title Martin Reinhardt closed an issue as Won't Fix Jenkins / JENKINS-41650 More documentation on setting up rocketchatnotifier Change By: Martin Reinhardt Status: Open Closed Resolution: Won't Fix 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-41650) More documentation on setting up rocketchatnotifier
Title: Message Title Martin Reinhardt commented on JENKINS-41650 Re: More documentation on setting up rocketchatnotifier WebHook and API Keys are not supported. Feel free to add a Feature Request. I will document the rest in the wiki page 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-42074) Test connection should also validate check active credentials
Title: Message Title René de Groot commented on JENKINS-42074 Re: Test connection should also validate check active credentials Logging a warning during job execution with the check if the credentials are of the pre-1.1.1 plugin version could be helpful too 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-41543) Clicking "Blue Ocean" should take you to the dashboard
Title: Message Title Josh McDonald commented on JENKINS-41543 Re: Clicking "Blue Ocean" should take you to the dashboard https://github.com/jenkinsci/blueocean-plugin/pull/829 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-41966) Entering and exiting the editor
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-41966 Entering and exiting the editor Change By: Brody Maclean *Entry points** Creation (when there is no Jenkinsfile in the repository) ** https://invis.io/Q2A110KM9#/216715766_Pipeline_Creation-Github_Step_4_No_Repos** https://zpl.io/AOIaW* For a specific branch on the Branches tab ** https://invis.io/Q2A110KM9#/218891868_Pipeline-Branches** https://zpl.io/ZtGMt8* For a specific branch on the run screen ** https://invis.io/Q2A110KM9#/218685699_Failed_Tests_1200px** https://zpl.io/Z4q3x2*Saving options*Very similar to Githubs web file editing workflow.** https://invis.io/Q2A110KM9#/219103950_Editor-Commit_New_File** https://zpl.io/ZGeB17We present a dialog that allows users to:* Specify a commit message* Specify a commit description* Radio list** Commit to $CURRENT_BRANCH** Commit to new branch*** Text box: branch name* Buttons** Save - commits the Jenkinsfile** Cancel - exists this dialog and returns to the editor_Github example_ !github-new-file.png|thumbnail! *Authenticating*When saving we may have to ask for a "upgrade" to the stored Github token. Writing to the repository needs different scopes than what we may have setup during creation. I'd imagine this looks very similar to the creation way of doing it (asking for a Key) * https://invis.io/Q2A110KM9#/219318668_Editor-Commit_New_File_Connect_To_Github * https://zpl.io/ZT8LLy* Editor header buttons*** https://invis.io/Q2A110KM9#/219088047_Editor-Home** https://zpl.io/1Aij8a* Save - triggers the save dialog* Try** Needs to be defined** Cancel - exists the editor without saving, goes back to entry point Add Comment
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title Michael Neale assigned an issue to Michael Neale Jenkins / JENKINS-26138 Support workspaces for Pipeline jobs Change By: Michael Neale Assignee: Jesse Glick Michael Neale 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-36423) Ability to search testng-results outside of jenkins workpsace
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-36423 Ability to search testng-results outside of jenkins workpsace Change By: Nalin Makar Assignee: Nalin Makar 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-38661) NPE occurred when testngProjAction is NULL
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-38661 NPE occurred when testngProjAction is NULL Change By: Nalin Makar Assignee: Nalin Makar 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-18185) TestNG plugin should be able to capture and display stdout/stderr of tests
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-18185 TestNG plugin should be able to capture and display stdout/stderr of tests Change By: Nalin Makar Assignee: Nalin Makar 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-26971) looking at failed TestNG result causes an exception
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-26971 looking at failed TestNG result causes an exception Change By: Nalin Makar Assignee: Nalin Makar 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-32746) TestNG Results Trend graph doesn't show all build results
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-32746 TestNG Results Trend graph doesn't show all build results Change By: Nalin Makar Assignee: Nalin Makar 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-35254) Thresholds to mark build unstable
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-35254 Thresholds to mark build unstable Change By: Nalin Makar Assignee: Nalin Makar 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-10462) Display TestNG Method parameters at the top level
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-10462 Display TestNG Method parameters at the top level Change By: Nalin Makar Assignee: Nalin Makar 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-32698) Negative duration times displayed by Jenkins TestNG plugin
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-32698 Negative duration times displayed by Jenkins TestNG plugin Change By: Nalin Makar Assignee: Nalin Makar 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-23539) Initialize TestNgResult from testng result xml tag
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-23539 Initialize TestNgResult from testng result xml tag Change By: Nalin Makar Assignee: Nalin Makar 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-15985) Common TestNG report on Matrix configuration project
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-15985 Common TestNG report on Matrix configuration project Change By: Nalin Makar Assignee: Nalin Makar 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-32933) No TestNG results should mark build as Failure
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-32933 No TestNG results should mark build as Failure Change By: Nalin Makar Assignee: Nalin Makar 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-37002) Forcefully Mark Build as SUCCESS when Failure count is below Unstable Threshold
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-37002 Forcefully Mark Build as SUCCESS when Failure count is below Unstable Threshold Change By: Nalin Makar Assignee: Nalin Makar 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-27687) xmlPullParser.nextToken() returning 'null', code using that generates Illegal Argument on Enum class
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-27687 xmlPullParser.nextToken() returning 'null', code using that generates Illegal Argument on Enum class Change By: Nalin Makar Assignee: Nalin Makar 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-13654) Showing attributes in testng results
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-13654 Showing attributes in testng results Change By: Nalin Makar Assignee: Nalin Makar 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko edited a comment on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException [~daichirata] Thanks, just tried this and can confirm that Pipeline Nodes and Processes Plugin 2.9 is the issue [~iocanel] He narrowed it down to this plugin / version 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Daichi Hirata Thanks, just tried this and can confirm that Pipeline Nodes and Processes Plugin 2.9 is the issue 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-34825) Jobs in Folders should show credentials bound in the credential domain
Title: Message Title Joel Brown commented on JENKINS-34825 Re: Jobs in Folders should show credentials bound in the credential domain This is a security requirement. Folders can be limited to certain users, meaning only those users can use and see that folder's credentials. 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-41543) Clicking "Blue Ocean" should take you to the dashboard
Title: Message Title Josh McDonald started work on JENKINS-41543 Change By: Josh McDonald Status: Open In Progress 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-38753) Flow diagram allows text between nodes to bleed over each other
Title: Message Title Josh McDonald stopped work on JENKINS-38753 Change By: Josh McDonald Status: In Progress Open 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-38753) Flow diagram allows text between nodes to bleed over each other
Title: Message Title Josh McDonald resolved as Fixed Fixed in master Jenkins / JENKINS-38753 Flow diagram allows text between nodes to bleed over each other Change By: Josh McDonald Status: Open Resolved 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 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-41669) Buildgraph view does not show for some json responses
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41669 Re: Buildgraph view does not show for some json responses Code changed in jenkins User: Per Böhlin Path: src/main/webapp/scripts/buildgraph-appctrl.js http://jenkins-ci.org/commit/buildgraph-view/c4ad92978a014e415a42bc0f07a919c9f8fca8a3 Log: [FIXED JENKINS-41669] Buildgraph view does not show for som json responses. 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Lars Lawoko updated an issue Jenkins / JENKINS-42048 Cannot Connect, PID NumberFormatException Change By: Lars Lawoko Component/s: workflow-durable-task-step-plugin 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-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Patrick Thiel edited a comment on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. [~jglick] there looks to be a lot of potentially useful information in this ticket. The linked ticket that this was closed out and marked as a duplicate of has not been updated since November 2016, and was created in December 2014. Further, it doesn't appear to highlight the current issue with environment variables in Jenkins pipelines returning null. Can you please elucidate on the these actions taken ? 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-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Patrick Thiel commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. Jesse Glick there looks to be a lot of potentially useful information in this ticket. The linked ticket that this was closed out and marked as a duplicate of has not been updated since November 2016, and was created in December 2014. Further, it doesn't appear to highlight the current issue with environment variables in Jenkins pipelines returning null. Can you please elucidate on the actions taken? 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-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Daichi Hirata commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException The same kind of problem has occurred in my Jenkins running on GKE. This problem occurred by upgrading Pipeline Nodes and Processes Plugin from 2.8 to 2.9. I am confirming that this problem temporarily resolves by downgrading that plugin from 2.9 to 2.8. 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-34825) Jobs in Folders should show credentials bound in the credential domain
Title: Message Title recampbell edited a comment on JENKINS-34825 Re: Jobs in Folders should show credentials bound in the credential domain BTW, the The workaround is to simply store the credentials at the root level and not try to store them per-folder . 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-34825) Jobs in Folders should show credentials bound in the credential domain
Title: Message Title recampbell commented on JENKINS-34825 Re: Jobs in Folders should show credentials bound in the credential domain BTW, the workaround is to simply store the credentials at the root level. 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-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
Title: Message Title
Peter Springsteen edited a comment on JENKINS-39482
Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
I am seeing the same general behavior as Tony's first run...for every run.Tested on:* Jenkins: 2.19.1* -- github-plugin: 1.26.0 * Jenkins: 2.32.2* -- github-plugin: 1.26.0Using:* Public & Enterprise GitHub* Webhooks, pull requests, manual buildsSince the default activity is to resolve any repos, I checked to see if it was picking up on any repos, which it was:_Picks up on multiple repos because of Global Shared Pipeline Library getting pulled from GitHub_*Jenkins Log*{code:java}Feb 15, 2017 10:51:18 PM FINEST org.jenkinsci.plugins.github.status.sources.AnyDefinedRepositorySource reposrepositories source=repo-name-contributor value=[GitHubRepositoryName[host=github.com,username=psprings,repository=jenkins-pipeline-helpers-lib], GitHubRepositoryName[host={{ENTERPRISEGITURL}},username={{ENTERPRISEGITORG}},repository={{ENTERPRISEGITREPO}}]]{code}But the output did not reflect any repos:*Pipeline Console Text*{code: bash none }[Pipeline] step[Set GitHub commit status (universal)] PENDING on repos [] (sha:6f85cd0) with context:ci/jenkins/foo{code}So I tried manually setting the repo url as per xianju's suggestion, and got the same result (although overriding the sha worked just fine).*Jenkinsfile snippet*{code:java}step([$class: "GitHubCommitStatusSetter",commitShaSource: [$class: "ManuallyEnteredShaSource", sha: gitCommit],//reposSource: [$class: "AnyDefinedRepositorySource"],reposSource: [$class: "ManuallyEnteredRepositorySource", url: "https://enterprisegithuburl.com/Org/Repo" ],contextSource: [$class: "ManuallyEnteredCommitContextSource", context: "ci/jenkins/foo" ],errorHandlers: [[$class: "ChangingBuildStatusErrorHandler", result: "UNSTABLE"]],statusResultSource: [ $class: "ConditionalStatusResultSource", results: [[$class: "AnyBuildResult", message: message, state: state]] ] ]);{code}A status message _is_ set by the GitHub Branch Source plugin if the build passes/fails, but would like more granular commit statuses.Any thoughts/suggestions?
Add Comment
[JIRA] (JENKINS-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
Title: Message Title
Peter Springsteen edited a comment on JENKINS-39482
Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
[~killuazhu] thanks for providing the code snippet. Let me clarify about the "granularity" comment. I mean tying stages to statuses for a given GitHub commit. Your example takes a similar approach to the GitHub Branch Source plugin's *GitHubBuildStatusNotification* class, whereby the final build status of the run (holistically) is tied to a single status for a given commit. What I would like to do is to tie each stage to a _separate_ status.So, your code snippet would be modified to be something like (untested pseudocode){code:java}node('a_node') {buildStep('Checkout'){checkout scm}buildStep('step 1'){sh '''echo "step 1"'''}}void buildStep(String context, Closure closure) { stage(context); try {setBuildStatus(context, "In progress...", "PENDING");closure(); } catch (Exception e) {setBuildStatus(context, e.take(140), "FAILURE"); } setBuildStatus(context, "Success", "SUCCESS");}// Updated to account for contextvoid setBuildStatus(String context, String message, String state) { context = context ?: "ci/jenkins/build-status" step([ $class: "GitHubCommitStatusSetter", reposSource: [$class: "ManuallyEnteredRepositorySource", url: "https://github.com/my-org/my-repo"], contextSource: [$class: "ManuallyEnteredCommitContextSource", context: context], errorHandlers: [[$class: "ChangingBuildStatusErrorHandler", result: "UNSTABLE"]], statusResultSource: [ $class: "ConditionalStatusResultSource", results: [[$class: "AnyBuildResult", message: message, state: state]] ] ]);}{code}So the resulting status array would be something like:*GET /repos/:owner/:repo/commits/:ref/statuses*{code: bash none }{ "state": "failure", "statuses": [{ "url": "https://...bfb1bf", "id": 899209, "state": "success", "description": "Success", "target_url": "http://./job/PR-25/27/display/redirect", "context": "Checkout", "created_at": "2017-02-15T20:05:36Z", "updated_at": "2017-02-15T20:05:36Z"},{ "url": "https://...bfb1bf", "id": 899210, "state": "failure", "description": "Error executing echo", "target_url": "http://./job/PR-25/27/display/redirect", "context": "step 1", "created_at": "2017-02-15T20:05:36Z", "updated_at": "2017-02-15T20:05:36Z"} ], "sha": "...777bfb1bf",{code}I could facilitate this with direct API calls to GitHub, but would prefer a more Pipeline native approach.
Add Comment
[JIRA] (JENKINS-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
Title: Message Title
Peter Springsteen commented on JENKINS-39482
Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
xianjun zhu thanks for providing the code snippet. Let me clarify about the "granularity" comment. I mean tying stages to statuses for a given GitHub commit. Your example takes a similar approach to the GitHub Branch Source plugin's GitHubBuildStatusNotification class, whereby the final build status of the run (holistically) is tied to a single status for a given commit. What I would like to do is to tie each stage to a separate status. So, your code snippet would be modified to be something like (untested pseudocode)
node('a_node') {
buildStep('Checkout'){
checkout scm
}
buildStep('step 1'){
sh '''echo "step 1"
'''
}
}
void buildStep(String context, Closure closure) {
stage(context);
try {
setBuildStatus(context, "In progress...", "PENDING");
closure();
} catch (Exception e) {
setBuildStatus(context, e.take(140), "FAILURE");
}
setBuildStatus(context, "Success", "SUCCESS");
}
// Updated to account for context
void setBuildStatus(String context, String message, String state) {
context = context ?: "ci/jenkins/build-status"
step([
$class: "GitHubCommitStatusSetter",
reposSource: [$class: "ManuallyEnteredRepositorySource", url: "https://github.com/my-org/my-repo"],
contextSource: [$class: "ManuallyEnteredCommitContextSource", context: context],
errorHandlers: [[$class: "ChangingBuildStatusErrorHandler", result: "UNSTABLE"]],
statusResultSource: [ $class: "ConditionalStatusResultSource", results: [[$class: "AnyBuildResult", message: message, state: state]] ]
]);
}
So the resulting status array would be something like: GET /repos/:owner/:repo/commits/:ref/statuses
Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
{
"state": "failure",
"statuses": [
{
"url": "https://...bfb1bf",
"id": 899209,
"state": "success",
"description": "Success",
"target_url": "http://./job/PR-25/27/display/redirect",
"context": "Checkout",
"created_at": "2017-02-15T20:05:36Z",
"updated_at": "2017-02-15T20:05:36Z"
},
{
"url": "https://...bfb1bf",
"id": 899210,
"state": "failure",
"description": "Error executing echo",
"target_url": "http://./job/PR-25/27/display/redirect",
"context": "step 1",
"created_at": "2017-02-15T20:05:36Z",
"updated_at": "2017-02-15T20:05:36Z"
}
],
"sha": "...777bfb1bf",
I could facilitate this with direct API calls to GitHub, but would prefer a more Pipeline native approach.
[JIRA] (JENKINS-40903) Server Name Indication is not supported
Title: Message Title Fabrizio Lungo commented on JENKINS-40903 Re: Server Name Indication is not supported I can confirm that it is during the "Parsing POM" stage that the error occurs. I'll provide feedback once 2.15 is released. Thanks. 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-39705) Remove Show More button instead of disabling it
Title: Message Title Ivan Meredith started work on JENKINS-39705 Change By: Ivan Meredith Status: Open In Progress 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-41096) Only show admin link in header if the user has privileges
Title: Message Title Ivan Meredith started work on JENKINS-41096 Change By: Ivan Meredith Status: Open In Progress 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-38767) Header link on branch name should be moved to pipeline name
Title: Message Title Ivan Meredith resolved as Fixed Fixed in latest headers. Jenkins / JENKINS-38767 Header link on branch name should be moved to pipeline name Change By: Ivan Meredith Status: In Progress Resolved 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 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-38753) Flow diagram allows text between nodes to bleed over each other
Title: Message Title Josh McDonald commented on JENKINS-38753 Re: Flow diagram allows text between nodes to bleed over each other https://github.com/jenkinsci/blueocean-plugin/pull/828 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-42081) Inconsistent folder title "compaction"
Title: Message Title Michael Neale commented on JENKINS-42081 Re: Inconsistent folder title "compaction" have you tried turning it off and on again? 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-41557) manager.createSummary().appendText() fails in sandbox
Title: Message Title
Craig Rodrigues edited a comment on JENKINS-41557
Re: manager.createSummary().appendText() fails in sandbox
[~ikedam] How is this supposed to work?I put this one line in my pipeline script: {noformat} manager.createSummary("green.gif").appendText('test') {noformat} and got this traceback:{noformat}org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildSummaryAction appendText java.lang.String at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) at WorkflowScript.run(WorkflowScript:14) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor380.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:74) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Finished: FAILURE{noformat}I went to the *In-process Script Approval* link,but it did not have any option to whitelist appendText().So is there no way to get appendText() to workinside a pipeline?
[JIRA] (JENKINS-41557) manager.createSummary().appendText() fails in sandbox
Title: Message Title
Craig Rodrigues commented on JENKINS-41557
Re: manager.createSummary().appendText() fails in sandbox
ikedam How is this supposed to work? I put this one line in my pipeline script: manager.createSummary("green.gif").appendText('test') and got this traceback:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildSummaryAction appendText java.lang.String
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:113)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16)
at WorkflowScript.run(WorkflowScript:14)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)
at sun.reflect.GeneratedMethodAccessor380.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:74)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:165)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Finished: FAILURE
I went to the In-process Script Approval link, but it did not have
[JIRA] (JENKINS-42083) Allow Auth Type 'auto'
Title: Message Title Phil Rumble created an issue Jenkins / JENKINS-42083 Allow Auth Type 'auto' Issue Type: Improvement Assignee: Christian McHugh Components: saltstack-plugin Created: 2017/Feb/16 12:46 AM Priority: Minor Reporter: Phil Rumble Can you please add the 'auto' option to the Auth Type. Thank you Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33744) Link to Maven configuration is dependent on Jenkins version
Title: Message Title Arnaud Héritier resolved as Fixed was fixed in 2.14 Jenkins / JENKINS-33744 Link to Maven configuration is dependent on Jenkins version Change By: Arnaud Héritier Status: Open Resolved 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 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-37821) Maven job fails with NPE when JDK is set to (System)
Title: Message Title Arnaud Héritier commented on JENKINS-37821 Re: Maven job fails with NPE when JDK is set to (System) 2.15 should fix this issue 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-42079) Allow "local" Shared Library to be loaded from current repo branch
Title: Message Title Liam Newman commented on JENKINS-42079 Re: Allow "local" Shared Library to be loaded from current repo branch One other note: even if we implement the method or define sections, I believe we should still consider this option. It provides another helpful interim step between on the way to Shared Libraries. 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-38484) Using test stability publisher in a Pipeline build will hang
Title: Message Title Sean Flanigan edited a comment on JENKINS-38484 Re: Using test stability publisher in a Pipeline build will hang Test-stability plugin 2.2 ^*^ has now been released with this fix. Thanks for the report [~orrc], and for the fix [~theomega]! EDIT: Thanks for the support [~kutzi]. ^*^ Why not version 2.0, you ask? Because Maven. 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-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title Arnaud Héritier commented on JENKINS-38738 Re: Maven plugin does not use SNI with SSL maven repos version 2.15 will upgrade wagon to the latest version. Let us know if it fixes this issue. Thanks 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-42080) API to write a single file to the repository
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-42080 API to write a single file to the repository Change By: Patrick Wolf Sprint: frank, tethys, christmas , post-release 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-38484) Using test stability publisher in a Pipeline build will hang
Title: Message Title Sean Flanigan closed an issue as Fixed Test-stability plugin 2.2 * has now been released with this fix. Thanks for the report Christopher Orr, and for the fix Dominik Bruhn! * Why not version 2.0, you ask? Because Maven. Jenkins / JENKINS-38484 Using test stability publisher in a Pipeline build will hang Change By: Sean Flanigan 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-40309) Redeploy Artifacts fails with IllegalStateException: the settings.xml could not be supplied for the current build: null
Title: Message Title Arnaud Héritier commented on JENKINS-40309 Re: Redeploy Artifacts fails with IllegalStateException: the settings.xml could not be supplied for the current build: null please provide more details about your jenkins version, the maven plugin version and your job configuration 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-42079) Allow "local" Shared Library to be loaded from current repo branch
Title: Message Title Liam Newman commented on JENKINS-42079 Re: Allow "local" Shared Library to be loaded from current repo branch Some have suggested that evaluate or readTrusted would be preferable solutions. They are fine for loading individual files, but not for more than one. Also, they behave differently from code in shared libraries, meaning users will have learn different behaviors for each. These also have drawbacks in areas such as testing, support, and documentation. If we guide users towards one consistent way to load things (Libraries) we do not have to explain it multiple times and fixes that help Shared Libraries would generally help local libraries as well. 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-40507) maven plugin : build hang when downloading some artifacts
Title: Message Title Arnaud Héritier commented on JENKINS-40507 Re: maven plugin : build hang when downloading some artifacts The version 2.15 of the plugin will bundle the latest version of wagon. Let us know if it helps 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-40621) MavenEmbedderUtils#getMavenVersion() leaks file descriptors
Title: Message Title Arnaud Héritier resolved as Fixed Fixed in 2.15 Jenkins / JENKINS-40621 MavenEmbedderUtils#getMavenVersion() leaks file descriptors Change By: Arnaud Héritier Status: In Progress Resolved 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 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-40896) Μaven build aborts intermittently with message Accept timed out
Title: Message Title Arnaud Héritier commented on JENKINS-40896 Re: Μaven build aborts intermittently with message Accept timed out swarm plugin was released few days ago and proses a new client jar which is more up-to-date compared the the remoting jar proposed in Jenkins core. Try to update and let us know if it stabilise your platform. Thx 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-40903) Server Name Indication is not supported
Title: Message Title Arnaud Héritier commented on JENKINS-40903 Re: Server Name Indication is not supported In the next version 2.15 of the plugin we upgraded Wagon dependencies to their latest version. If the problem occurs when Jenkins does the "Parsing POM" I hope it should be 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 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-41296) Use private Maven repository does not work in pre-build steps
Title: Message Title Arnaud Héritier commented on JENKINS-41296 Re: Use private Maven repository does not work in pre-build steps Do you have the docker-slaves plugin 1.0.5 installed ? (JENKINS-40410) 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-42080) API to write a single file to the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42080 API to write a single file to the repository Change By: James Dumay * Scope Requirements ** Write natively to any branch of a Git repository hosted on Github* Write to any branch of a Git repository* Must not require a Jenkins core upgrade. Must maintain compatibility with Jenkins 2.7.1 and above.*Desired user experience** User experience is described in JENKINS-41966* Mockup: https://projects.invisionapp.com/share/Q2A110KM9#/screens/219088047*Notes*[~jglick] said there is beginnings of this in the scm-api but no implementations. 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-42080) API to write a single file to the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42080 API to write a single file to the repository Change By: James Dumay *Requirements** Write natively to any branch of a Git repository hosted on Github* Write to any branch of a Git repository* Must not require a Jenkins core upgrade. Must maintain compatibility with Jenkins 2.7.1 and above . *Desired user experience** User experience is described in JENKINS-41966* Mockup: https://projects.invisionapp.com/share/Q2A110KM9#/screens/219088047*Notes*[~jglick] said there is beginnings of this in the scm-api but no implementations. 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-39703) API to read a single file from the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39703 API to read a single file from the repository Change By: James Dumay *Requirements** Read natively from any branch of a Git repository hosted on Github* Read from any branch of a Git repository* Must not require a Jenkins core upgrade. Must maintain compatibility with Jenkins 2.7.1 and above . *Desired user experience** User experience is described in JENKINS-41966* Mockup: https://projects.invisionapp.com/share/Q2A110KM9#/screens/219088047*Notes*[~jglick] said there is beginnings of this in the scm-api but no implementations. 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-39703) API to read a single file from the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39703 API to read a single file from the repository Change By: James Dumay * Scope Requirements ** Read natively from any branch of a Git repository hosted on Github* Read from any branch of a Git repository* Must not require a Jenkins core upgrade. Must maintain compatibility with Jenkins 2.7.1 and above.*Desired user experience** User experience is described in JENKINS-41966* Mockup: https://projects.invisionapp.com/share/Q2A110KM9#/screens/219088047*Notes*[~jglick] said there is beginnings of this in the scm-api but no implementations. 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-42079) Allow "local" Shared Library to be loaded from current repo branch
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-42079
Allow "local" Shared Library to be loaded from current repo branch
Change By:
Liam Newman
For context see: https://jenkins.io/blog/2017/02/15/declarative-notifications/And the linked bugs, in particular JENKINS-41396. I've been informed that this is a horrible idea, but I'm going to describe it here just to make sure. There have been a number of issues and discussions going around, dealing with how to define variables and methods in Declarative Pipeline. Right now, we can define variables and methods outside of the pipeline section but that is not a supported solution and it is not viable long-term.As noted in JENKINS-41396, we have a supported way to define variables and methods that we can use in Declarative Pipeline viaShared Libraries. However, that means I have to spin up a separate repository just to make a helper method that might be used in only one Pipeline. JENKINS-41396 and JENKINS-41335 suggest adding sections to the Declarative Pipeline model to allow these things to defined insidethe same {{Jenkinsfile}}. This is also problematic: there are implementation issues, and it means that the distinction between the overall flow(defined in Declarative Pipeline) and the implementation details (defined in methods, variables, and classes) becomes more blurry.What I'm suggesting, is we reuse the functionality of "Shared libraries" but support loading from a subfolder in the current branch of the currently checked out repository. This would have a number of benefits over other solutions, it would: * reuse existing (and tested) functionality, limiting risk* not require creating a separate repository* keep the script code out of the Declarative Pipeline Jenkinsfile* use the same file/folder structure as Shared Library, getting users familiar with it for when they decide to use Shared LibrariesOn the downside, it would:* depend on additional folder/files beyond Jenkinsfile ({{method}} and {{define}} would be in Jenkinsfile)* require some changes to workflow-cps-global-lib to support loading from local and from subfolder instead of root folder.* make users have to understand library folder/file structure even to write simple helper method.We had a IRC chat about this, which I've attached. Also attached are images from a Pipeline job that I created as a proof-of-concept. The code for this POC is in: https://github.com/bitwiseman/hermann/tree/issue/jenkins-library/exampleWhat is not shown/done in the POC: * loading from a subfolder (not currently supported), subfolder name should default to "jenkins" (maybe?) and be configurable to other values.* * Worked around by putting the {{vars}} folder in the root - this would not work if the project already had a {{src}} or {{vars}} folder.* loading from the currently checked out branch/commit (not currently supported)* * Worked around by hard coding the branch name* using a {{library local}} directive to tell declarative to load a local library* * Worked around by adding
[JIRA] (JENKINS-41337) Jenkins Deploys all the projects irrespective of changed project
Title: Message Title Arnaud Héritier commented on JENKINS-41337 Re: Jenkins Deploys all the projects irrespective of changed project What do you mean by deploy ? Which modules are built in your project ? 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-42079) Allow "local" Shared Library to be loaded from current repo branch
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-42079
Allow "local" Shared Library to be loaded from current repo branch
Change By:
Liam Newman
For context see: https://jenkins.io/blog/2017/02/15/declarative-notifications/And the linked bugs, in particular JENKINS-41396. I've been informed that this is a horrible idea, but I'm going to describe it here just to make sure. There have been a number of issues and discussions going around, dealing with how to define variables and methods in Declarative Pipeline. Right now, we can define variables and methods outside of the pipeline section but that is not a supported solution and it is not viable long-term.As noted in JENKINS-41396, we have a supported way to define variables and methods that we can use in Declarative Pipeline viaShared Libraries. However, that means I have to spin up a separate repository just to make a helper method that might be used in only one Pipeline. JENKINS-41396 and JENKINS-41335 suggest adding sections to the Declarative Pipeline model to allow these things to defined insidethe same {{Jenkinsfile}}. This is also problematic: there are implementation issues, and it means that the distinction between the overall flow(defined in Declarative Pipeline) and the implementation details (defined in methods, variables, and classes) becomes more blurry.What I'm suggesting, is we reuse the functionality of "Shared libraries" but support loading from a subfolder in the current branch of the currently checked out repository. This would have a number of benefits over other solutions, it would: * reuse existing (and tested) functionality, limiting risk* not require creating a separate repository* keep the script code out of the Declarative Pipeline Jenkinsfile* use the same file/folder structure as Shared Library, getting users familiar with it for when they decide to use Shared LibrariesOn the downside, it would:* require depend on additional folder/ files beyond Jenkins file Jenkinsfile ( {{ method }} and {{ define }} would be in Jenkinsfile)* would require some changes to pipeline workflow-cps-global-lib to support loading from local and from subfolder instead of root folder. * make users have to understand library folder/file structure even to write simple helper method. See: We had a IRC chat about this, which I've attached. Also attached are images from a Pipeline job that I created as a proof-of-concept. The code for this POC is in: https://github.com/bitwiseman/hermann/tree/issue/jenkins-library/example What is not shown/done in the POC: * loading from a subfolder (not currently supported), subfolder name should default to "jenkins" (maybe?) and be configurable to other values.* * Worked around by putting the {{vars}} folder in the root - this would not work if the project already had a {{src}} or {{vars}} folder.* loading from the currently checked out branch/commit (not currently supported)* * Worked around by hard coding the branch name* using a {{library local}} directive to
[JIRA] (JENKINS-39703) API to read a single file from the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39703 API to read a single file from the repository Change By: James Dumay *Scope** Read natively from any branch of a Git repository hosted on Github* Read from any branch of a Git repository* Must not require a Jenkins core upgrade. Must maintain compatibility with Jenkins 2.7.1 and above.*Desired user experience* * User experience is described in JENKINS-41966* Mockup: https://projects.invisionapp.com/share/Q2A110KM9#/screens/219088047*Notes*[~jglick] said there is beginnings of this in the scm-api but no implementations. 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-42080) API to write a single file to the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42080 API to write a single file to the repository Change By: James Dumay *Scope** Write natively to any branch of a Git repository hosted on Github* Write to any branch of a Git repository* Must not require a Jenkins core upgrade. Must maintain compatibility with Jenkins 2.7.1 and above.*Desired user experience* * User experience is described in JENKINS-41966* Mockup: https://projects.invisionapp.com/share/Q2A110KM9#/screens/219088047*Notes*[~jglick] said there is beginnings of this in the scm-api but no implementations. 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-41697) StackOverflowError parsing Maven POM
Title: Message Title Arnaud Héritier commented on JENKINS-41697 Re: StackOverflowError parsing Maven POM Any reason to not use the version 2.14 ? 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-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
Title: Message Title
xianjun zhu commented on JENKINS-39482
Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
@peter Not sure if I understand your granular commit status correct, in our build, we do set different status to github PR commit based on the progress of CI build. So following my previous example, we wrapped each workflow step with `buildStep` function below, it will set the commit in PR as `PENDING` before each step, set it to `FAILURE` if fails. If the whole build is successful, then set the status to `SUCCESS`
node('a_node') {
buildStep('Checkout'){
checkout scm
}
buildStep('step 1'){
sh '''echo "step 1"
'''
}
setBuildStatus("Build complete", "SUCCESS");
}
void buildStep(String message, Closure closure) {
stage(message);
try {
setBuildStatus(message, "PENDING");
closure();
} catch (Exception e) {
setBuildStatus(message, "FAILURE");
}
}
void setBuildStatus(String message, String state) {
step([
$class: "GitHubCommitStatusSetter",
reposSource: [$class: "ManuallyEnteredRepositorySource", url: "https://github.com/my-org/my-repo"],
contextSource: [$class: "ManuallyEnteredCommitContextSource", context: "ci/jenkins/build-status"],
errorHandlers: [[$class: "ChangingBuildStatusErrorHandler", result: "UNSTABLE"]],
statusResultSource: [ $class: "ConditionalStatusResultSource", results: [[$class: "AnyBuildResult", message: message, state: state]] ]
]);
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42080) API to write a single file to the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42080 API to write a single file to the repository Change By: James Dumay *Scope** Write natively to any branch of a Git repository hosted on Github* Write to any branch of a Git repository* Must not require a Jenkins core upgrade. Must maintain compatibility with Jenkins 2.7.1 and above.*Desired user experience*Mockup: https://projects.invisionapp.com/share/Q2A110KM9#/screens/219088047 *Notes*[~jglick] said there is beginnings of this in the scm-api but no implementations. 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-42080) API to write a single file to the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42080 API to write a single file to the repository Change By: James Dumay *Scope** Primary** Write natively to any branch of a Git repository hosted on Github* * Github Enterprise* Secondary** Bitbucket Server** Bitbucket Cloud*Out Write to any branch of scope* a Git repository * Git Must not require a Jenkins core upgrade. Must maintain compatibility with Jenkins 2.7.1 and others support above. * Notes Desired user experience * For the [Blue Ocean Pipeline Editor| Mockup: https:// jenkins projects . io invisionapp.com / blog share / 2016 Q2A110KM9# / 09 screens / 19/blueocean-beta-declarative-pipeline-pipeline-editor/], let the user author it in the editor then commit it back to the repository.We need a new API and relevant implementations (Github and Bitbucket) that would allow Blue Ocean to write a file from the repository. 219088047 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received
[JIRA] (JENKINS-39703) API to read a single file from the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39703 API to read a single file from the repository Change By: James Dumay *Scope** Read natively from any branch of a Git repository hosted on Github* Read from any branch of a Git repository* Must not require a Jenkins core upgrade . Must maintain compatibility with Jenkins 2.7.1 and above. * Notes Desired user experience * For the [Blue Ocean Pipeline Editor| Mockup: https:// jenkins projects . io invisionapp.com / blog share / 2016 Q2A110KM9# / 09 screens / 19/blueocean-beta-declarative-pipeline-pipeline-editor/] we want to read the Jenkinsfile from the repository, let the user author it in the editor then commit it back to the repository. 219088047 We need a new API and relevant implementations (Github and Bitbucket) that would allow Blue Ocean to read/write a file from the repository. *Notes* [~jglick] said there is beginnings of this in the scm-api but no implementations. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41761) NullPointerException in Maven32Main
Title: Message Title Arnaud Héritier resolved as Fixed Fixed in 2.15 Jenkins / JENKINS-41761 NullPointerException in Maven32Main Change By: Arnaud Héritier Status: In Progress Resolved 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 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-39703) API to read a single file from the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39703 API to read a single file from the repository Change By: James Dumay *Scope** Read natively from any branch of a Git repository hosted on Github * Out Read from any branch of scope* a Git repository * Git and Bitbucket support Must not require a Jenkins core upgrade *Notes*For the [Blue Ocean Pipeline Editor|https://jenkins.io/blog/2016/09/19/blueocean-beta-declarative-pipeline-pipeline-editor/] we want to read the Jenkinsfile from the repository, let the user author it in the editor then commit it back to the repository.We need a new API and relevant implementations (Github and Bitbucket) that would allow Blue Ocean to read/write a file from the repository.[~jglick] said there is beginnings of this in the scm-api but no implementations. 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
[JIRA] (JENKINS-42079) Allow "local" Shared Library to be loaded from current repo branch
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-42079
Allow "local" Shared Library to be loaded from current repo branch
Change By:
Liam Newman
For context see: https://jenkins.io/blog/2017/02/15/declarative-notifications/And the linked bugs, in particular JENKINS-41396. I've been informed that this is a horrible idea, but I'm going to describe it here just to make sure. There have been a number of issues and discussions going around, dealing with how to define variables and methods in Declarative Pipeline. Right now, we can define variables and methods outside of the pipeline section but that is not a supported solution and it is not viable long-term.As noted in JENKINS-41396, we have a supported way to define variables and methods that we can use in Declarative Pipeline viaShared Libraries. However, that means I have to spin up a separate repository just to make a helper method that might be used in only one Pipeline. JENKINS-41396 and JENKINS-41335 suggest adding sections to the Declarative Pipeline model to allow these things to defined insidethe same {{Jenkinsfile}}. This is also problematic: there are implementation issues, and it means that the distinction between the overall flow(defined in Declarative Pipeline) and the implementation details (defined in methods, variables, and classes) becomes more blurry.What I'm suggesting, is we reuse the functionality of "Shared libraries" but support loading from a subfolder in the current branch of the currently checked out repository. This would have a number of benefits over other solutions, it would: * reuse existing (and tested) functionality, limiting risk* not require creating a separate repository* keep the script code out of the Declarative Pipeline Jenkinsfile* use the same file/folder structure as Shared Library, getting users familiar with it for when they decide to use Shared LibrariesOn the downside, it would:* require additional files beyond Jenkins file (method and define would be in Jenkinsfile)* TODO still editing. would require some changes to pipelineSee: https://github.com/bitwiseman/hermann/tree/issue/jenkins-library/example
Add Comment
[JIRA] (JENKINS-42079) Allow "local" Shared Library to be loaded from current repo branch
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-42079
Allow "local" Shared Library to be loaded from current repo branch
Change By:
Liam Newman
For context see: https://jenkins.io/blog/2017/02/15/declarative-notifications/And the linked bugs, in particular JENKINS-41396. I've been informed that this is a horrible idea, but I'm going to describe it here just to make sure. There have been a number of issues and discussions going around, dealing with how to handle define variables and methods in Declarative Pipeline.Right now, we can define variables and methods outside of the pipeline section but that is not a supported solution and it is not viable long-term. As noted in JENKINS-41396, we have a supported way to define variables and methods that we can use in Declarative Pipeline via Shared Libraries. However, that means I have to spin up a separate repository just to make a helper method that might be used in only one Pipeline. JENKINS-41396 and JENKINS-41335 suggest adding sections to the Declarative Pipeline model to allow these things to defined insidethe same {{Jenkinsfile}}. This is also problematic: there are implementation issues, and it means that the distinction between the overall flow(defined in Declarative Pipeline) and the implementation details (defined in methods, variables, and classes) becomes more blurry.What I'm suggesting, is we reuse the functionality of "Shared libraries" but support loading from a subfolder in the current branch of the currently checked out repository. This would have a number of benefits over other solutions, it would: * reuse existing (and tested) functionality, limiting risk* not require creating a separate repository* keep the script code out of the Declarative Pipeline Jenkinsfile* use the same file/folder structure as Shared Library, getting users familiar with it for when they decide to use Shared LibrariesOn the downside, it would:* require additional files beyond Jenkins file (method and define would be in Jenkinsfile)* TODO still editing. See: https://github.com/bitwiseman/hermann/tree/issue/jenkins-library/example
Add Comment
[JIRA] (JENKINS-41966) Entering and exiting the editor
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-41966 Entering and exiting the editor Change By: Brody Maclean Assignee: Brody Maclean James Dumay 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-39482) GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
Title: Message Title
Peter Springsteen commented on JENKINS-39482
Re: GitHub commit status not working with GitHubCommitStatusSetter on first build of branch in multi-branch pipeline
I am seeing the same general behavior as Tony's first run...for every run. Tested on:
Jenkins: 2.19.1
– github-plugin: 1.26.0
Jenkins: 2.32.2
– github-plugin: 1.26.0 Using:
Public & Enterprise GitHub
Webhooks, pull requests, manual builds
Since the default activity is to resolve any repos, I checked to see if it was picking up on any repos, which it was: Picks up on multiple repos because of Global Shared Pipeline Library getting pulled from GitHub Jenkins Log
Feb 15, 2017 10:51:18 PM FINEST org.jenkinsci.plugins.github.status.sources.AnyDefinedRepositorySource repos
repositories source=repo-name-contributor value=[GitHubRepositoryName[host=github.com,username=psprings,repository=jenkins-pipeline-helpers-lib], GitHubRepositoryName[host={{ENTERPRISEGITURL}},username={{ENTERPRISEGITORG}},repository={{ENTERPRISEGITREPO}}]]
But the output did not reflect any repos: Pipeline Console Text
Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
[Pipeline] step
[Set GitHub commit status (universal)] PENDING on repos [] (sha:6f85cd0) with context:ci/jenkins/foo
So I tried manually setting the repo url as per xianju's suggestion, and got the same result (although overriding the sha worked just fine). Jenkinsfile snippet
step([
$class: "GitHubCommitStatusSetter",
commitShaSource: [$class: "ManuallyEnteredShaSource", sha: gitCommit],
//reposSource: [$class: "AnyDefinedRepositorySource"],
reposSource: [$class: "ManuallyEnteredRepositorySource", url: "https://enterprisegithuburl.com/Org/Repo" ],
contextSource: [$class: "ManuallyEnteredCommitContextSource", context: "ci/jenkins/foo" ],
errorHandlers: [[$class: "ChangingBuildStatusErrorHandler", result: "UNSTABLE"]],
statusResultSource: [ $class: "ConditionalStatusResultSource", results: [
[$class: "AnyBuildResult", message: message, state: state]] ]
]);
[JIRA] (JENKINS-42062) Inputs not showing in inner most nested parallels
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42062
Inputs not showing in inner most nested parallels
Change By:
James Dumay
{panel:title= Support for inputs in nested parallels This bug requires Blue Ocean to solve better support for nested stages and parallels|titleBGColor=lightgrey}This is blocked by JENKINS-38442. Blue Ocean does not handle nesting of stages or parallels at this time.{panel}*Original request*For this pipeline , in Blue Ocean, it requests input once, the second input request is not shown and the flow is paused{code}stage ("stage1") {parallel ("s1": { parallel ( "DB": { node {println("Done DB1")println("Done DB2") } }, "ENV": { node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("done env") } } ) node { println("Done ENV2") } node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("Done ") } } )}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42062) Inputs not showing in inner most nested parallels
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42062
Inputs not showing in inner most nested parallels
Change By:
James Dumay
{panel:title=This bug requires Blue Ocean to solve better support for nested stages and parallels|titleBGColor=lightgrey} This is blocked by JENKINS-38442. Blue Ocean does not handle nesting of stages or parallels at this time. See JENKINS-38442 for more information. {panel} *Original request*For this pipeline , in Blue Ocean, it requests input once, the second input request is not shown and the flow is paused{code}stage ("stage1") {parallel ("s1": { parallel ( "DB": { node {println("Done DB1")println("Done DB2") } }, "ENV": { node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("done env") } } ) node { println("Done ENV2") } node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("Done ") } } )}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42062) Inputs not showing in inner most nested parallels
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42062
Inputs not showing in inner most nested parallels
Change By:
James Dumay
{panel:title=This bug requires Blue Ocean to solve better support for nested stages and parallels|titleBGColor=lightgrey}Blue Ocean does not handle nesting of stages or parallels at this time. See JENKINS-38442 for more information. {panel} *Original request*For this pipeline , in Blue Ocean, it requests input once, the second input request is not shown and the flow is paused{code}stage ("stage1") {parallel ("s1": { parallel ( "DB": { node {println("Done DB1")println("Done DB2") } }, "ENV": { node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("done env") } } ) node { println("Done ENV2") } node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("Done ") } } )}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42062) Inputs not showing in inner most nested parallels
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42062 Inputs not showing in inner most nested parallels Change By: James Dumay Summary: Inputs not showing in inner most nested parallels 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-42062) Inputs not showing in nested parallels
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42062
Inputs not showing in nested parallels
Change By:
James Dumay
{panel:title=Support for inputs in nested parallels requires better support for nested stages and parallels|titleBGColor=lightgrey} This is blocked by JENKINS-38442. Blue Ocean does not handle nesting of stages or parallels at this time. {panel} *Original request*For this pipeline , in Blue Ocean, it requests input once, the second input request is not shown and the flow is paused{code}stage ("stage1") {parallel ("s1": { parallel ( "DB": { node {println("Done DB1")println("Done DB2") } }, "ENV": { node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("done env") } } ) node { println("Done ENV2") } node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("Done ") } } )}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42062) Inputs not showing in nested parallels
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-42062
Inputs not showing in nested parallels
Change By:
James Dumay
This is blocked by JENKINS-38442. Blue Ocean does not handle nesting of stages or parallels at this time.*Original request* For this pipeline , in Blue Ocean, it requests input once, the second input request is not shown and the flow is paused{code}stage ("stage1") {parallel ("s1": { parallel ( "DB": { node {println("Done DB1")println("Done DB2") } }, "ENV": { node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("done env") } } ) node { println("Done ENV2") } node { input message: 'What do you want to do here?', parameters: [choice(choices: 'Rerun\nSkip\nAbort', description: '', name: '')], submitterParameter: ''println("Done ") } } )}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-42062) Inputs not showing in nested parallels
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42062 Inputs not showing in nested parallels Change By: James Dumay Summary: Blue Ocean Process details view failing to show input request for Inputs not showing in nested requests parallels 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-36933) Name or alias Shell Script Step (sh)
Title: Message Title Eloy Lafuente commented on JENKINS-36933 Re: Name or alias Shell Script Step (sh) Sorry Jesse Glick, I must be missing something obvious but... how is this related with Blue Ocean at all, and how can it be closed as not a defect when it's a request for an improvement? I'm a complete newbie with Jenkins pipelines, but this is one of the features I'm missing since day zero (the ability to name "sh" scripts, or any other step) in order to quickly know what is failing/passing and/or going quickly to certain step results. Right now I've to click on them sequentially till I arrive to the one I'm interested on. And I'm not using any "Blue Ocean" special thing/plugin (that I'm aware, lol). Just stock Jenkins and its awesome pipelines. Again, excuse me if I've understood anything wrongly, but I cannot name steps and it's a little bit a pity, and the way this has been closed has surprised me. Hence, I ask. TIA and ciao 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.
