[JIRA] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Joshua Hoblitt commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Keith Zantow If a concrete example would be helpful, this is what a jenkins deployment (partially driven by hiera data) using some of the experimental functionality in puppet-jenkins looks like: https://github.com/lsst-sqre/sandbox-jenkins-demo/blob/master/jenkins_demo/manifests/profile/master.pp#L5-L187 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [logstash-plugin] (JENKINS-30889) Get the updated version of @timestamp with each new message field (while I'm using wrapper)
Title: Message Title Rusty Gerard closed an issue as Fixed Jenkins / JENKINS-30889 Get the updated version of @timestamp with each new message field (while I'm using wrapper) Change By: Rusty Gerard Status: Open Closed Assignee: Rusty Gerard Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [logstash-plugin] (JENKINS-29762) Make inclusion of build and environment variables configurable
Title: Message Title Rusty Gerard assigned an issue to Rusty Gerard Jenkins / JENKINS-29762 Make inclusion of build and environment variables configurable Change By: Rusty Gerard Assignee: gabe cee Rusty Gerard Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [logstash-plugin] (JENKINS-29762) Make inclusion of build and environment variables configurable
Title: Message Title Rusty Gerard resolved as Fixed Jenkins / JENKINS-29762 Make inclusion of build and environment variables configurable Change By: Rusty Gerard Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [logstash-plugin] (JENKINS-29830) Logstash plugin set @timestamp value to line output value
Title: Message Title Rusty Gerard commented on JENKINS-29830 Re: Logstash plugin set @timestamp value to line output value This is available in the build wrapper starting with version 1.2.0. Currently it is not implemented in the post-build action. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [logstash-plugin] (JENKINS-30889) Get the updated version of @timestamp with each new message field (while I'm using wrapper)
Title: Message Title Rusty Gerard commented on JENKINS-30889 Re: Get the updated version of @timestamp with each new message field (while I'm using wrapper) This is available in the build wrapper starting with version 1.2.0. Currently it is not implemented in the post-build action. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [logstash-plugin] (JENKINS-29762) Make inclusion of build and environment variables configurable
Title: Message Title Rusty Gerard commented on JENKINS-29762 Re: Make inclusion of build and environment variables configurable This is now available in version 1.2.0 of the plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title
Joshua Hoblitt edited a comment on JENKINS-34035
Re: 2.0 needs a stable/supported way to disable the Getting Started wizard
[~kzantow] neither ` {{ puppet-jenkins ` }} or ` {{ chef-cookbooks/jenkins ` }} attempt to mange ` {{ config.xml ` }} directly. The main config potentially interacts with so many plugins that it becomes an all or nothing affair unless one wants to attempt to semantically understand the xstream serialization. And don't forget that plugins may also have independent config files (with somewhat difficult to predict names). I concede that it is possible to manage jenkins by copying all of the xstream dumps around as opaque blobs but this doesn't allow you to express any meaningful configuration via a CM tool. The same result could be achieved by copying around a tarball.Most of the CM integration I've looked at use some combination of the pre-canned CLI commands along with groovy scripts feed in via the CLI. I believe this has been the general preference over the REST API as an ssh public key may be user defined. However, I will confess to doing awful things in puppet-jenkins in order to be able to set the API key for a user account to a known value. While the gymnastics the CM integration maintainers are doing is working to a degree, it is painful and required requires considerable effort for every new feature.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Joshua Hoblitt commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Keith Zantow neither `puppet-jenkins` or `chef-cookbooks/jenkins` attempt to mange `config.xml` directly. The main config potentially interacts with so many plugins that it becomes an all or nothing affair unless one wants to attempt to semantically understand the xstream serialization. And don't forget that plugins may also have independent config files (with somewhat difficult to predict names). I concede that it is possible to manage jenkins by copying all of the xstream dumps around as opaque blobs but this doesn't allow you to express any meaningful configuration via a CM tool. The same result could be achieved by copying around a tarball. Most of the CM integration I've looked at use some combination of the pre-canned CLI commands along with groovy scripts feed in via the CLI. I believe this has been the general preference over the REST API as an ssh public key may be user defined. However, I will confess to doing awful things in puppet-jenkins in order to be able to set the API key for a user account to a known value. While the gymnastics the CM integration maintainers are doing is working to a degree, it is painful and required considerable effort for every new feature. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Keith Zantow commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Joshua Hoblitt for said deployments, are you providing a config.xml? If the version is set properly, that should bypass the setup wizard already (ok, there's probably an issue with the upgrade wizard here). It seems like more work to deal with deployment flags. Is dealing with the config.xml part of the problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: recena Path: src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolderDescriptor.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/52ee18657d0aa6044c4b4f4db5d2f2c319b6975d Log: JENKINS-31162 Category ID has changed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: Manuel Recena Path: src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolderDescriptor.java src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/newInstanceDetail.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/newInstanceDetail.properties src/main/resources/com/cloudbees/hudson/plugins/folder/Messages.properties src/main/webapp/images/48x48/folder.png http://jenkins-ci.org/commit/cloudbees-folder-plugin/a7691cc5a63f8b3237fc4f53d8f58e2fe9711a8c Log: JENKINS-31162 Support for Item categorization in Jenkins 2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: Manuel Recena Path: src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/newInstanceDetail.jelly http://jenkins-ci.org/commit/cloudbees-folder-plugin/7cdb034206927c8d808425c930b75a032c10cdbb Log: JENKINS-31162 Invalid Jelly file Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: recena Path: src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolderDescriptor.java src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/9f8fa69e7386a33510ad900e577094ef455d08d6 Log: JENKINS-31162 Removing the default implementation asked by @jglick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolderDescriptor.java src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/newInstanceDetail.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/newInstanceDetail.properties src/main/resources/com/cloudbees/hudson/plugins/folder/Messages.properties src/main/webapp/images/48x48/folder.png http://jenkins-ci.org/commit/cloudbees-folder-plugin/e60b470d1853e94b94cad698fbbb6dd7155d0218 Log: Merge pull request #56 from recena/master JENKINS-31162 Support for Item categorization in Jenkins 2 Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/40b49661ca16...e60b470d1853 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: recena Path: src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolderDescriptor.java src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/e8b1dcb8dd1a6ec78e1b20ec96c49a520bc7a9d0 Log: JENKINS-31162 AbstractFolderDescriptor provides a default implementation of getCategoryId method Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34045) Error in GIT URL
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-34045 Error in GIT URL Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34045) Error in GIT URL
Title: Message Title Mark Waite resolved as Not A Defect Please don't use bug reports to request help. There are very few people who read bug reports for the git plugin and many more people who read the Jenkins mailing list. Please send e-mail to the Jenkins users mailing list with your question. That will allow help from the larger community, instead of relying solely on the git plugin maintainer. Jenkins / JENKINS-34045 Error in GIT URL Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34045) Error in GIT URL
Title: Message Title tanuj manda created an issue Jenkins / JENKINS-34045 Error in GIT URL Issue Type: Bug Assignee: Mark Waite Attachments: Error.jpg Components: git-plugin Created: 2016/Apr/06 2:04 AM Environment: Jenkins 1.654, Java 1.7, Windows 8.1, google chrome, git-plugin, Labels: jenkins plugin Priority: Minor Reporter: tanuj manda When I gave the github URL in the "Source Code Management" "GIT" the URL as https://github.com/tanujchinnu/project1.git. It shows me an error message saying that "Failed to connect to repository : Error performing command: ls-remote -h https://github.com/tanujchinnu/project1.git HEAD" Not sure what this
[JIRA] [gerrit-trigger-plugin] (JENKINS-33875) Gerrit trigger threads blocked (GerritMissedEventPlaybackManager ?)
Title: Message Title Will Saxon commented on JENKINS-33875 Re: Gerrit trigger threads blocked (GerritMissedEventPlaybackManager ?) We're getting this behavior now even with the events-log plugin disabled. We have the default of 3 threads - do we need to add more threads? The documentation is not clear on why the default is 3 or why someone might want to change that number. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-33875) Gerrit trigger threads blocked (GerritMissedEventPlaybackManager ?)
Title: Message Title Will Saxon updated an issue Jenkins / JENKINS-33875 Gerrit trigger threads blocked (GerritMissedEventPlaybackManager ?) Change By: Will Saxon Attachment: Gerrit-threads-locked-noevents-log.txt Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [vmware-vrealize-automation-plugin] (JENKINS-34015) Deployment configuration parameters not working.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34015 Re: Deployment configuration parameters not working. Code changed in jenkins User: inkysea Path: README.md doc/BuildJob.png doc/vRA_BuildStep.png src/main/java/com/inkysea/vmware/vra/jenkins/plugin/model/Deployment.java src/main/java/com/inkysea/vmware/vra/jenkins/plugin/model/Request.java src/main/java/com/inkysea/vmware/vra/jenkins/plugin/model/RequestParam.java src/main/java/com/inkysea/vmware/vra/jenkins/plugin/vRADeploymentBuildStep.java http://jenkins-ci.org/commit/vmware-vrealize-automation-plugin/ff2a6a631986941ccc74143c7455f8694189fdd7 Log: Merge pull request #5 from inkysea/master Merge for bug fix JENKINS-34015 Compare: https://github.com/jenkinsci/vmware-vrealize-automation-plugin/compare/b814c11c3687...ff2a6a631986 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extended-choice-parameter-plugin] (JENKINS-33537) Get JOB_NAME in Groovy Script of Choose Source for Value
Title: Message Title vimil resolved as Fixed The project object is now exposed as a groovy script variable in version 0.63 Jenkins / JENKINS-33537 Get JOB_NAME in Groovy Script of Choose Source for Value Change By: vimil Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [extended-choice-parameter-plugin] (JENKINS-33537) Get JOB_NAME in Groovy Script of Choose Source for Value
Title: Message Title vimil commented on JENKINS-33537 Re: Get JOB_NAME in Groovy Script of Choose Source for Value The project object is now exposed as a groovyscript variable in version 0.63 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed
Title: Message Title Matt McCormick commented on JENKINS-34044 Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed Build script for the AMI: https://github.com/InsightSoftwareConsortium/ITKBuildRobot/tree/master/MS2012R2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ec2-plugin] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed
Title: Message Title Matt McCormick created an issue Jenkins / JENKINS-34044 EC2 Plugin: Windows: java.io.IOException: Pipe closed Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Apr/06 12:43 AM Environment: Jenkins 1.642.4 (DockerHub 'jenkins' image latest) Amazon EC2 plugin 1.31 Windows slave Java Runtime 8.0.73 Windows AMI based off MS2012R2-EBS-HVM Priority: Major Reporter: Matt McCormick When starting the AWS Windows slave, failure occurs with: Apr 05, 2016 8:12:55 PM null FINEST: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is still pending/launching, waiting 5s Apr 05, 2016 8:13:00 PM null FINEST: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is still pending/launching, waiting 5s Apr 05, 2016 8:13:05 PM null FINEST: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is still pending/launching, waiting 5s Apr 05, 2016 8:13:10 PM null FINEST: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is still pending/launching, waiting 5s Apr 05, 2016 8:13:10 PM null FINER: Node ITKAWSWindows (i-0234e203d06253ae7)(i-0234e203d06253ae7) is ready ITKAWSWindows (i-0234e203d06253ae7) booted at 1459901636000 Connecting to
[JIRA] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Daniel Beck commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Joshua Hoblitt Code reviews are not done yet. Still, I expect we'll merge it in time for 2.0 RC. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Joshua Hoblitt commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Daniel Beck That I am in favor of said PR, which is not as of this moment merged. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Daniel Beck commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Joshua Hoblitt There's already a pull request for this and this is being considered as a late addition for 2.0 RC, scheduled for release later today. Given that, could you please clarify what your comment's purpose is? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34042) Git exception message is null when using workflow checkout step
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-34042 Git exception message is null when using workflow checkout step Change By: Mark Waite Component/s: workflow-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Joshua Hoblitt commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Speaking for myself, I deploy test instances of jenkins via puppet, with security configuration, several times a day. I neither need nor want "clippy" popping up at me nor do I want to be forced into screen scraping to perform an unattended deployment. Working well with Configuration Management is an absolutely critical component to a DevOps user narrative. Jenkins already does this poorly and making clippy mandatory only makes the situation worse. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34042) Git exception message is null when using workflow checkout step
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-34042 Git exception message is null when using workflow checkout step Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-33943) jenkins-cli.jar: list-changes command produces the same result for non-existent build and build with no changes recorded
Title: Message Title Daniel Beck commented on JENKINS-33943 Re: jenkins-cli.jar: list-changes command produces the same result for non-existent build and build with no changes recorded Pavel Janoušek You may be interested in this one. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cli] (JENKINS-33942) jenkins-cli.jar: set-build-description command fails with NPE for non-existent build
Title: Message Title Daniel Beck commented on JENKINS-33942 Re: jenkins-cli.jar: set-build-description command fails with NPE for non-existent build Pavel Janoušek You may be interested in this one. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33946) Dhudson.DNSMultiCast.disabled Option Ignored
Title: Message Title Daniel Beck resolved as Not A Defect System properties must be passed between the java command and the -jar argument. Jenkins / JENKINS-33946 Dhudson.DNSMultiCast.disabled Option Ignored Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33960) using gradle in a pipeline
Title: Message Title Daniel Beck commented on JENKINS-33960 Re: using gradle in a pipeline Does this affect all gradle tasks? What about ./gradlew help? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-34043) Docker SSH Slave loses connectivity
Title: Message Title
Brandon Raabe edited a comment on JENKINS-34043
Re: Docker SSH Slave loses connectivity
Here's the stack trace: {{ 16:00:42 ERROR: Connection was broken: java.io.IOException: Sorry, this connection is closed.16:00:42 at com.trilead.ssh2.transport.TransportManager.ensureConnected(TransportManager.java:587)16:00:42 at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:660)16:00:42 at com.trilead.ssh2.channel.Channel.freeupWindow(Channel.java:407)16:00:42 at com.trilead.ssh2.channel.Channel.freeupWindow(Channel.java:347)16:00:42 at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:943)16:00:42 at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58)16:00:42 at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79)16:00:42 at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82)16:00:42 at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72)16:00:42 at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)16:00:42 at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)16:00:42 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)16:00:42 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)16:00:42 Caused by: java.net.SocketException: Connection timed out16:00:42 at java.net.SocketOutputStream.socketWrite0(Native Method)16:00:42 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)16:00:42 at java.net.SocketOutputStream.write(SocketOutputStream.java:159)16:00:42 at com.trilead.ssh2.crypto.cipher.CipherOutputStream.flush(CipherOutputStream.java:75)16:00:42 at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:193)16:00:42 at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:107)16:00:42 at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:677)16:00:42 at com.trilead.ssh2.channel.ChannelManager.sendData(ChannelManager.java:429)16:00:42 at com.trilead.ssh2.channel.ChannelOutputStream.write(ChannelOutputStream.java:63)16:00:42 at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:94)16:00:42 at hudson.remoting.ChunkedOutputStream.sendBreak(ChunkedOutputStream.java:66)16:00:42 at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:46)16:00:42 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:45)16:00:42 at hudson.remoting.Channel.send(Channel.java:582)16:00:42 at hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:261)16:00:42 at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158)16:00:42 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)16:00:42 at java.util.concurrent.FutureTask.run(FutureTask.java:262)16:00:42 at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)16:00:42 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)16:00:42 at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18)16:00:42 at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21)16:00:42 at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)16:00:42 at java.util.concurrent.FutureTask.run(FutureTask.java:262)16:00:42 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)16:00:42 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)16:00:42 at java.lang.Thread.run(Thread.java:745)16:00:42 16:00:42 Build step 'Execute shell' marked build as failure16:00:42
[JIRA] [docker-plugin] (JENKINS-34043) Docker SSH Slave loses connectivity
Title: Message Title
Brandon Raabe edited a comment on JENKINS-34043
Re: Docker SSH Slave loses connectivity
Here's the stack trace:{{ 16:00:42 ERROR: Connection was broken: java.io.IOException: Sorry, this connection is closed.16:00:42 at com.trilead.ssh2.transport.TransportManager.ensureConnected(TransportManager.java:587)16:00:42 at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:660)16:00:42 at com.trilead.ssh2.channel.Channel.freeupWindow(Channel.java:407)16:00:42 at com.trilead.ssh2.channel.Channel.freeupWindow(Channel.java:347)16:00:42 at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:943)16:00:42 at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58)16:00:42 at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79)16:00:42 at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82)16:00:42 at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72)16:00:42 at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)16:00:42 at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)16:00:42 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)16:00:42 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)16:00:42 Caused by: java.net.SocketException: Connection timed out16:00:42 at java.net.SocketOutputStream.socketWrite0(Native Method)16:00:42 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)16:00:42 at java.net.SocketOutputStream.write(SocketOutputStream.java:159)16:00:42 at com.trilead.ssh2.crypto.cipher.CipherOutputStream.flush(CipherOutputStream.java:75)16:00:42 at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:193)16:00:42 at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:107)16:00:42 at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:677)16:00:42 at com.trilead.ssh2.channel.ChannelManager.sendData(ChannelManager.java:429)16:00:42 at com.trilead.ssh2.channel.ChannelOutputStream.write(ChannelOutputStream.java:63)16:00:42 at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:94)16:00:42 at hudson.remoting.ChunkedOutputStream.sendBreak(ChunkedOutputStream.java:66)16:00:42 at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:46)16:00:42 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:45)16:00:42 at hudson.remoting.Channel.send(Channel.java:582)16:00:42 at hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:261)16:00:42 at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158)16:00:42 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)16:00:42 at java.util.concurrent.FutureTask.run(FutureTask.java:262)16:00:42 at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)16:00:42 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)16:00:42 at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18)16:00:42 at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21)16:00:42 at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)16:00:42 at java.util.concurrent.FutureTask.run(FutureTask.java:262)16:00:42 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)16:00:42 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)16:00:42 at java.lang.Thread.run(Thread.java:745)16:00:42 16:00:42 Build step 'Execute shell' marked build as failure16:00:42
[JIRA] [perforce-plugin] (JENKINS-26999) Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27)
Title: Message Title peter liu reopened an issue I feel like I should reopen this ticket since it's never fixed and still seen with latest release 1.3.36 Jenkins / JENKINS-26999 Perforce polling and labeling no longer resolves global password macros (regression from 1.3.27) Change By: peter liu Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-34043) Docker SSH Slave loses connectivity
Title: Message Title
Brandon Raabe commented on JENKINS-34043
Re: Docker SSH Slave loses connectivity
Here's the stack trace:
{{16:00:42 ERROR: Connection was broken: java.io.IOException: Sorry, this connection is closed. 16:00:42 at com.trilead.ssh2.transport.TransportManager.ensureConnected(TransportManager.java:587) 16:00:42 at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:660) 16:00:42 at com.trilead.ssh2.channel.Channel.freeupWindow(Channel.java:407) 16:00:42 at com.trilead.ssh2.channel.Channel.freeupWindow(Channel.java:347) 16:00:42 at com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:943) 16:00:42 at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58) 16:00:42 at com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79) 16:00:42 at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82) 16:00:42 at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72) 16:00:42 at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103) 16:00:42 at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39) 16:00:42 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) 16:00:42 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) 16:00:42 Caused by: java.net.SocketException: Connection timed out 16:00:42 at java.net.SocketOutputStream.socketWrite0(Native Method) 16:00:42 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) 16:00:42 at java.net.SocketOutputStream.write(SocketOutputStream.java:159) 16:00:42 at com.trilead.ssh2.crypto.cipher.CipherOutputStream.flush(CipherOutputStream.java:75) 16:00:42 at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:193) 16:00:42 at com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:107) 16:00:42 at com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:677) 16:00:42 at com.trilead.ssh2.channel.ChannelManager.sendData(ChannelManager.java:429) 16:00:42 at com.trilead.ssh2.channel.ChannelOutputStream.write(ChannelOutputStream.java:63) 16:00:42 at hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:94) 16:00:42 at hudson.remoting.ChunkedOutputStream.sendBreak(ChunkedOutputStream.java:66) 16:00:42 at hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:46) 16:00:42 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:45) 16:00:42 at hudson.remoting.Channel.send(Channel.java:582) 16:00:42 at hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:261) 16:00:42 at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) 16:00:42 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 16:00:42 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 16:00:42 at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) 16:00:42 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 16:00:42 at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18) 16:00:42 at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) 16:00:42 at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) 16:00:42 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 16:00:42 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 16:00:42 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 16:00:42 at
[JIRA] [docker-plugin] (JENKINS-34043) Docker SSH Slave loses connectivity
Title: Message Title Brandon Raabe created an issue Jenkins / JENKINS-34043 Docker SSH Slave loses connectivity Issue Type: Bug Assignee: magnayn Attachments: Screen Shot 2016-04-05 at 3.53.18 PM.png Components: docker-plugin Created: 2016/Apr/05 11:01 PM Priority: Minor Reporter: Brandon Raabe We have been seeing a consistent "Slave went offline" message when using the docker plugin to schedule our ssh build slaves. The build appears to be working fine. I can attach to the slave container and still see the slave.jar process as well as the build job running inside the container. However, when I look at the Nodes page, it looks like eventually the master loses connection with the slave and it starts counting down to failure. The build eventually fails after 15-17 mins. I have disabled the slave and master ping threads documented https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread We started experiencing this issue after jumping from docker-plugin 0.9.* to 0.16.*
[JIRA] [core] (JENKINS-33567) Job configuration scrolls "persist" between page loads incorrectly
Title: Message Title gus reiber closed an issue as Fixed closing the issue, since Daniel isn't seeing it. I think I only saw a similar issue because Chrome was tripping over the debugger. Will check again when we open back up for 2.1 Jenkins / JENKINS-33567 Job configuration scrolls "persist" between page loads incorrectly Change By: gus reiber Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-34032) Pipeline plugin workflow step allocates workspace in jenkins root
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-34032
Pipeline plugin workflow step allocates workspace in jenkins root
According to the documentation given in Snippet Generator:
The path may be relative to the slave root, or absolute.
Now perhaps it would be more intuitive to use Jenkins.getRawWorkspaceDir() or Slave.getWorkspaceRoot() as the base directory if an absolute path is not used. Not sure that such a change would be compatible, though.
Anyway better would perhaps be to write
ws("${pwd()}/../${env.BRANCH_NAME.replace('/', '-')}") {…}
which will always allocate a workspace which is a sibling of the current one.
Change By:
Jesse Glick
Issue Type:
Bug Improvement
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-33847) Support for implicit variable WORKSPACE in Pipeline stages
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-33847 Support for implicit variable WORKSPACE in Pipeline stages Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-33839) Pipeline workspace is not browsable via pipeline page
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-33839 Pipeline workspace is not browsable via pipeline page Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33930) new tabbed job config page broken accessibility
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33930 Re: new tabbed job config page broken accessibility Code changed in jenkins User: gusreiber Path: war/src/main/js/widgets/config/tabbar.less http://jenkins-ci.org/commit/jenkins/99e482b2a94102c6c2b3445c2fa1514f242fede5 Log: JENKINS-33930 focus color for delete style only. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33930) new tabbed job config page broken accessibility
Title: Message Title gus reiber commented on JENKINS-33930 Re: new tabbed job config page broken accessibility waiting for gitHub. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34007) Jenkins 2.0 - wizard 'X' button
Title: Message Title Daniel Beck commented on JENKINS-34007 Re: Jenkins 2.0 - wizard 'X' button Keith Zantow How about adding a 'Skip' link to the bottom of plugin selection (with the two big buttons) that takes you to user creation? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34007) Jenkins 2.0 - wizard 'X' button
Title: Message Title Keith Zantow commented on JENKINS-34007 Re: Jenkins 2.0 - wizard 'X' button Patrick Wolf right, this was a fuzzy requirement added on during review. Happy to modify / remove. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Keith Zantow commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard R. Tyler Croy anyway, I'm not exactly opinionated either way, just pointing out that this undermines one of the things Jenkins 2 is supposed to be improving. I really don't like the security token / generated admin from a user experience standpoint, but I see it as a necessary evil for the time being, given what Daniel Beck is trying to accomplish and I'm not sure having an easy way to automate completely bypassing it is the right thing to do. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title Keith Zantow commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard R. Tyler Croy oddly enough, you could just read the security token and make 2 requests (1: post the auth info, 2: hit the 'complete install' with a cookie from step 1) and these jenkins instances would be 'secure'. if you're going to the trouble to automate deployments, you should have programmatic access to the jenkins home as well as a URL to access the Jenkins system. as long as this was documented (I can do that), i assume advanced users could figure out how to do those basic tasks. yes, it's a few extra steps, but if you're scripting anything meaningful that seems likely to be a drop in the bucket. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [github-branch-source-plugin] (JENKINS-31552) GitHub Multibranch Workflow: anonymous checkout credentials should be renamed
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31552 Re: GitHub Multibranch Workflow: anonymous checkout credentials should be renamed I don't know why this issue is labeled as 2.0-planned Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34035) 2.0 needs a stable/supported way to disable the Getting Started wizard
Title: Message Title R. Tyler Croy commented on JENKINS-34035 Re: 2.0 needs a stable/supported way to disable the Getting Started wizard Keith Zantow I understand the concern, but if a user is automating their Jenkins installation and doesn't set up security, forcing the Getting Started Wizard I do not believe is productive (I would also consider those users "advanced"). There's nothing we can do well right now as far as encouraging secure defaults with Puppet/Chef/etc until something like JENKINS-31094 is introduced. There's been discussion in the puppet-jenkins repo (the issue/pull request eludes me right now) about how difficult it is to stand up a secure Jenkins installation in a deterministic and idempotent manner. IMO this is out of scope for this request though Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34007) Jenkins 2.0 - wizard 'X' button
Title: Message Title Patrick Wolf commented on JENKINS-34007 Re: Jenkins 2.0 - wizard 'X' button Okay, tested it. It installs 0 plugins and it skips the username and password creation. I guess that isn't terrible but probably not what most people want when they install Jenkins. Keith Zantow Maybe we could combine this problem with the wizard for people upgrading? Have an option to re-run setup wizard? Otherwise, I agree, we should probably have a warning screen if people close the setup wizard. Daniel Beck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32879) Integration with mailer plugin is broken
Title: Message Title Alexey Sergin closed an issue as Fixed Jenkins / JENKINS-32879 Integration with mailer plugin is broken Change By: Alexey Sergin Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-34007) Jenkins 2.0 - wizard 'X' button
Title: Message Title Patrick Wolf commented on JENKINS-34007 Re: Jenkins 2.0 - wizard 'X' button If you can't get back to the setup wizard then why would we allow people to close it. If you close it does the install get into an unstable state. What does happen? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-pipeline-plugin] (JENKINS-33935) Can't rerun a build
Title: Message Title Tadeu Sampaio commented on JENKINS-33935 Re: Can't rerun a build Same problem here after update... execute a blue job and re-execute a success job is ok, but re-execute a failed one is not working, on the ajax request I see an 500 error. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-34042) Git exception message is null when using workflow checkout step
Title: Message Title
Martin d'Anjou created an issue
Jenkins / JENKINS-34042
Git exception message is null when using workflow checkout step
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2016/Apr/05 8:43 PM
Priority:
Minor
Reporter:
Martin d'Anjou
I want to catch the exception message produced when the checkout GitSCM step has problems, and send it by email to the user, but the exception message is null. The code to reproduce this issue is:
node('remote') {
try {
checkout([$class: 'GitSCM', branches: [[name: 'refs/heads/master']],
userRemoteConfigs: [[
name: 'origin',
refspec: "invalid",
url: "https://github.com/jenkinsci/simple-build-for-pipeline-plugin.git"
]]
])
} catch (Exception e) {
echo("Exception: "+e.class.name)
error("Exception: "+e.getMessage()) // prints null
}
}
Currently, the getMessage() method returns null, as shown in the console:
...
Exception: hudson.AbortException
[Pipeline] error
[Pipeline] } //node
[Pipeline] Allocate node : End
[Pipeline] End of Pipeline
ERROR: Exception: null
Finished: FAILURE
[JIRA] [workflow-plugin] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title Jesse Glick commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure I assume additional changes will be needed for… Yes, but see issue 7. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32879) Integration with mailer plugin is broken
Title: Message Title Alexey Sergin commented on JENKINS-32879 Re: Integration with mailer plugin is broken I have tried P4 Plugin version 1.3.8 , the problem seems to be fixed. Paul Allen, thank you! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31691) add a step to determine if the current node is windows or not.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31691 Re: add a step to determine if the current node is windows or not. Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/IsUnixStepTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/01ad0a12129f710ed1076bd6610bb32a88fd1132 Log: [FIXED JENKINS-31691] Added isUnix step. Originally-Committed-As: bbd1e838533601139b6daf2f255d456b5090b329 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31458) NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameter
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31458 Re: NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class com.cwctravel.hudson.plugins.extended_choice_parameter.ExtendedChoiceParameterDefinition Code changed in jenkins User: Jesse Glick Path: multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/JobPropertyStep.java http://jenkins-ci.org/commit/workflow-multibranch-plugin/f3a40cf79f89626a2c4cfa126dfad903e687 Log: JENKINS-31458 Noting places where https://github.com/jenkinsci/jenkins/pull/1936 might allow for simplifications. Originally-Committed-As: 393aa3abca8e6fa974e4ae02ce30e96ab8f4c7c6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31086) 'stash' step applies default ant exclude patterns, no way to disable this
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31086 Re: 'stash' step applies default ant exclude patterns, no way to disable this Code changed in jenkins User: Andrew Bayer Path: support/src/main/resources/org/jenkinsci/plugins/workflow/support/steps/stash/StashStep/config.jelly http://jenkins-ci.org/commit/workflow-multibranch-plugin/80fa6b1c94e46832d7e78e62ca5834d2c8202711 Log: [FIXED JENKINS-31086] Add useDefaultExcludes option to stash Defaults to true, meaning use Ant default excludes for DirScanner.Glob. If false, don't use the default excludes, to pick up files like .gitignore etc. Originally-Committed-As: df072fb213d41b1dbf9a3ccea859a25dc5346485 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-29705) Virtual thread dump
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29705 Re: Virtual thread dump Code changed in jenkins User: Kohsuke Kawaguchi Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-job-plugin/36e73dc995a79fb1f910b366f47c1e9205a9ddc5 Log: JENKINS-29705 Exposed thread dump over HTTP Originally-Committed-As: 5e8fdbdc91f9539324a7a57e1e97ef70f813351f Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [branch-api-plugin] (JENKINS-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30206 Re: Multibranch plugin: Modified properties do not propagate to existing branches Code changed in jenkins User: Jesse Glick Path: multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowParameterDefinitionBranchPropertyTest.java http://jenkins-ci.org/commit/workflow-multibranch-plugin/8e3c946b5cf47b59cc4eee8a7d0f39a679ac617d Log: Merge pull request #199 from jglick/multibranch-param-JENKINS-30206 JENKINS-30206 Testing WorkflowParameterDefinitionBranchProperty more Originally-Committed-As: 2c148f146a8f8cf5c4bde9bf70978d6cc3983e8c Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [credentials-binding-plugin] (JENKINS-26051) Workflow integration for Credentials Binding
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26051 Re: Workflow integration for Credentials Binding Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java http://jenkins-ci.org/commit/workflow-multibranch-plugin/fe863c4a5ba855d65cd68588a71e5293f0bdf641 Log: JENKINS-26137 At least during restarting tests, serialization errors seem to be due to there being no PickleFactory’s installed. Merely calling PickleFactory.all() from the RiverWriter constructor, rather than later, seems to let PushdStepTest.restarting pass ( JENKINS-26051 ). Additionally asserting that there are in fact some factories loaded, since there is sure to be trouble if there are not. Also need to wait for the build to finish ( JENKINS-26399 ). Originally-Committed-As: 3d3fa348ed9c34e4492b2733802bc47416824e30 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-29221) WorkflowRun assigned FlowExecution when execution start fails
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29221 Re: WorkflowRun assigned FlowExecution when execution start fails Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-job-plugin/b4563b1d993293d0f7011f21a0b8a7903878edfa Log: JENKINS-29221 If a build fails to start, make sure we still perform all relevant steps as if it finished normally. Originally-Committed-As: 7db48c88df0ac3b35d489f6275b9f7e4d88de85c Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31386) "checkout scm" does not work in standalone jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31386 Re: "checkout scm" does not work in standalone jobs Code changed in jenkins User: Jesse Glick Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/config.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/help-scriptPath.html http://jenkins-ci.org/commit/workflow-cps-plugin/e3e8029b441bda842acc7520f21f863c9d062e00 Log: JENKINS-31386 Merging #264. Originally-Committed-As: c91ed650071362d9949da5fbffd13a9262c1fb1e Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-26149) BuildTriggerStepExecution does not survive restart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26149 Re: BuildTriggerStepExecution does not survive restart Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java http://jenkins-ci.org/commit/workflow-cps-plugin/f383df6b4df20d790df09123489c63f55d048896 Log: Checking sources for other possible restartability bugs as in JENKINS-26149 . RetryStep looks suspicious but apparently works. PushdStep cannot be tested due to a mysterious error noted in JENKINS-26137. Originally-Committed-As: cc76ee2256279676b4858cae95244585feceebaa Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-26074) Parallel branches that are finished disappear from the flow graph until the whole parallel step completes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26074 Re: Parallel branches that are finished disappear from the flow graph until the whole parallel step completes Code changed in jenkins User: Kohsuke Kawaguchi Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/parallel/ParallelStepTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsBodyInvoker.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/DSL.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/FlowHead.java http://jenkins-ci.org/commit/workflow-cps-plugin/ecd87d5c9db5c68fcc0bc7058e8e7847de62fe84 Log: [FIXED JENKINS-26074] I fixed the problem by making FlowHead removal automatic. We keep FlowHead around until another FlowHead subsumes it. In this way, FlowHead that belongs to completed CpsThread will hang around for parallel steps until a big StepEndNode comes in and designates everyone else as the parent. Originally-Committed-As: 920ac4886093f87d919b03008e8339be3fd1698f Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java http://jenkins-ci.org/commit/workflow-cps-plugin/f383df6b4df20d790df09123489c63f55d048896 Log: Checking sources for other possible restartability bugs as in JENKINS-26149 . RetryStep looks suspicious but apparently works. PushdStep cannot be tested due to a mysterious error noted in JENKINS-26137. Originally-Committed-As: cc76ee2256279676b4858cae95244585feceebaa Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31153) Rename workflow to pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31153 Re: Rename workflow to pipeline Code changed in jenkins User: Manuel Recena Path: job/src/main/resources/org/jenkinsci/plugins/workflow/job/WorkflowJob/newInstanceDetail.jelly http://jenkins-ci.org/commit/workflow-job-plugin/a71b83a5cff2c18911c8a62928ee2a5c9dadbac9 Log: JENKINS-31153 @jglick's suggestion was addressed Originally-Committed-As: 2ca9e66e56803506314c48b7a9aebb2c46fda5e2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-32133) Polish and expose auto-generated Workflow step documentation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32133 Re: Polish and expose auto-generated Workflow step documentation Code changed in jenkins User: Jesse Glick Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslHelp.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReference.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/workflow.css cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/workflow.js http://jenkins-ci.org/commit/workflow-cps-plugin/a0513e8e4738221cf41cbe9942074fdc936729b4 Log: JENKINS-32133 Merged #320. Originally-Committed-As: 71559f35cb73ecf7cfa880045b58a4317693b347 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-32133) Polish and expose auto-generated Workflow step documentation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32133 Re: Polish and expose auto-generated Workflow step documentation Code changed in jenkins User: gusreiber Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslHelp.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReference.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/workflow.css cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/workflow.js http://jenkins-ci.org/commit/workflow-cps-plugin/06956bcee3e51eaec9c94043b1e55e2abfc15d9a Log: JENKINS-32133 styling issues for DSL reference help Originally-Committed-As: 7d1fdbdff78fd55bff325051617b3457f5629dad Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31153) Rename workflow to pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31153 Re: Rename workflow to pipeline Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/console/WorkflowConsoleLogger.java http://jenkins-ci.org/commit/workflow-job-plugin/b186ee2849adca7854355b2a4c31aa5f0b974ac0 Log: JENKINS-31153 More renames. Originally-Committed-As: 199d8c9dc7ec8d02d6429dd652f666f14cbfc660 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31153) Rename workflow to pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31153 Re: Rename workflow to pipeline Code changed in jenkins User: Manuel Recena Path: cps/pom.xml http://jenkins-ci.org/commit/workflow-cps-plugin/051a03ceade003d90be6cfb7d6f2ccd7b1d5f2a4 Log: JENKINS-31153 WikiPage URL renamed Originally-Committed-As: 3498babe0c38b35dac8e0a0cccb9051ca129c2c8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32925 Re: StackOverflow when trying to get Pipeline GDSL file Code changed in jenkins User: Kohsuke Kawaguchi Path: cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy http://jenkins-ci.org/commit/workflow-cps-plugin/bf6f1fb7f31747315ca1c972e71f88afc96235d8 Log: JENKINS-32925 Handle recursion Use stack to keep track of traversal. Originally-Committed-As: ff210c3819a66e6fec7772a3242ff105c3646513 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Code changed in jenkins User: Jesse Glick Path: cps/pom.xml cps/src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/03650953a2c28412f57d0ea6e32aee6a0a937c69 Log: JENKINS-26481 With new script-security and groovy-cps releases, eachClosure finally passes. Originally-Committed-As: b356799f09d18b0d9f96c1084354df072b7d656f Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: Manuel Recena Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java http://jenkins-ci.org/commit/workflow-job-plugin/a25bea5e0c7b27222b324771103dd888379086e7 Log: JENKINS-31162 @amuniz's comment was addresed Originally-Committed-As: 98a1afc7748398d08df1bdf068e038baee353934 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: Manuel Recena Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java job/src/main/resources/org/jenkinsci/plugins/workflow/job/Messages.properties job/src/main/resources/org/jenkinsci/plugins/workflow/job/WorkflowJob/newInstanceDetail.jelly job/src/main/webapp/images/48x48/pipelinejob.png http://jenkins-ci.org/commit/workflow-job-plugin/e8cad2297f6af419eb28cd31ec8218c4b9b3ba5a Log: JENKINS-31162 Support for Item categorization in Jenkins 2 Originally-Committed-As: e99d4bc50b04553d14c209fe670228a6f435b196 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-27421) java.util.ArrayList$Itr is not Serializable
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27421 Re: java.util.ArrayList$Itr is not Serializable Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/persistence/IteratorHack.java cps/src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/4ab54f1ad2ef9685e66804dc3d3de7add29fc505 Log: [FIXED JENKINS-27421] Producing a safe serialization replacement for ArrayList$Itr, Originally-Committed-As: a990468a828e64961eda24332673c9cb8835c629 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [durable-task-plugin] (JENKINS-27152) Store sh control files outside of workspace
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27152 Re: Store sh control files outside of workspace Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PwdStepTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/db56cffc53abb11bb7d1ea869dac3c8055cb0458 Log: JENKINS-27152 Option for pwd step to return temp directory. Originally-Committed-As: 8c7421f007e829b2a9581af643b792ef47a6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31153) Rename workflow to pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31153 Re: Rename workflow to pipeline Code changed in jenkins User: Manuel Recena Path: job/pom.xml http://jenkins-ci.org/commit/workflow-job-plugin/4f64bc9272c33de242787f6710e6f5c60463b587 Log: JENKINS-31153 WikiPage URL renamed Originally-Committed-As: 3498babe0c38b35dac8e0a0cccb9051ca129c2c8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-27421) java.util.ArrayList$Itr is not Serializable
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-27421 java.util.ArrayList$Itr is not Serializable Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31162 Re: New item categorization and dynamic choice offering Code changed in jenkins User: Manuel Recena Path: job/src/main/resources/org/jenkinsci/plugins/workflow/job/WorkflowJob/newInstanceDetail.jelly http://jenkins-ci.org/commit/workflow-job-plugin/e0c2d30144f50fd98a12702dc4d04ced7cdb3178 Log: JENKINS-31162 To prevent XSS Originally-Committed-As: 6bea194f47bd19bca555b87e9bbd4152c2f402f5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-33005) Hang in StageStepExecution.println
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33005 Re: Hang in StageStepExecution.println Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java http://jenkins-ci.org/commit/workflow-cps-plugin/53ac56fa79c8b063cb86ee150f21538ac1d4dba8 Log: [FIXED JENKINS-33005] Make StageStepExecution defensively call isReady on foreign builds. Also make CpsFlowExecution.onLoad unconditionally set programPromise, in case CpsStepContext.getThreadGroupSynchronously is waiting for it. Originally-Committed-As: 0b4c317b7bc610283be00fef18b796a43315454c Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-28649) ExportedBean error with Workflow and AfterRestartTask
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28649 Re: ExportedBean error with Workflow and AfterRestartTask Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/AfterRestartTask.java http://jenkins-ci.org/commit/workflow-job-plugin/4129e02fbd080407d5ac18eca8e81bc81c2f9ab6 Log: [FIXED JENKINS-28649] Merging #298. Originally-Committed-As: 07f234e785c9bf6e69c873d2280c479dbd599ce7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-26126) DSLD and/or GDSL
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26126 Re: DSLD and/or GDSL Code changed in jenkins User: Andrew Bayer Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/Snippetizer.java cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/block.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslHelp.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReference.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dsld.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/gdsl.groovy cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/75df2410f755daa69c1005a19d46f4f14afe250c Log: [JENKINS-26126, JENKINS-32133] GDSL, DSLD, improved reference docs Squashed down to one commit. Added GDSL, DSLD and Groovy view-driven HTML reference docs for Workflow DSL, integrated into the job config UI, also able to be fetched directly from standard URLs. Originally-Committed-As: ccedde44b53dde20b3360b4402e028de4069742a Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31838) Virtual thread dump uses phony filenames
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31838 Re: Virtual thread dump uses phony filenames Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/rerun/RerunAction.java http://jenkins-ci.org/commit/workflow-cps-plugin/5cb03cabae608e761c6dd9f97cea29ae69b51427 Log: Noting JENKINS-31838. Originally-Committed-As: 0b1b639e1b14feb1d488e18814487af33be2aec0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30395) ClosedByInterruptException in JenkinsRule setup
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30395 Re: ClosedByInterruptException in JenkinsRule setup Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsFlowExecutionTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsScmFlowDefinitionTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/DSLTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/DynamicEnvironmentExpanderTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/SingleJobTestBase.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/CpsThreadDumpTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/steps/LoadStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/steps/RestartingLoadStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/IsUnixStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PwdStepTest.java cps/src/test/java/org/jenkinsci/plugins/workflow/cps/AbstractCpsFlowTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/b99329d09ad2c8815e60cd268839295d6b17c329 Log: JENKINS-30395 Deleting workaround now that we can use jenkins-test-harness 2.0. Originally-Committed-As: 109b8f82415fc41f24d5d6545e586f0bce7ba705 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-32133) Polish and expose auto-generated Workflow step documentation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32133 Re: Polish and expose auto-generated Workflow step documentation Code changed in jenkins User: Andrew Bayer Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/Snippetizer.java cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/block.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslHelp.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReference.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dslReferenceContent.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/dsld.groovy cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/gdsl.groovy cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/75df2410f755daa69c1005a19d46f4f14afe250c Log: [JENKINS-26126, JENKINS-32133] GDSL, DSLD, improved reference docs Squashed down to one commit. Added GDSL, DSLD and Groovy view-driven HTML reference docs for Workflow DSL, integrated into the job config UI, also able to be fetched directly from standard URLs. Originally-Committed-As: ccedde44b53dde20b3360b4402e028de4069742a Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Code changed in jenkins User: Jesse Glick Path: cps/src/test/java/org/jenkinsci/plugins/workflow/SerializationTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/f9122193c2099f63ce006f63d619ff3874799cd7 Log: JENKINS-26481 Creating integration test. Originally-Committed-As: 07f36024c20fb900c99de6d02d7d0acef6f62b5a Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-32214) Workflow and svn polling
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32214 Re: Workflow and svn polling Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java http://jenkins-ci.org/commit/workflow-job-plugin/77999f564410f4408a75994fe8ba96f68de40cde Log: JENKINS-32214 WorkflowJob.poll reworked to consider polling baselines from any running build or prior polling. Originally-Committed-As: c12abe251d9ad396966460bfb8d7bf9469eb6064 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-33438) replay-pipeline CLI command should have a consoleOutput option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33438 Re: replay-pipeline CLI command should have a consoleOutput option Code changed in jenkins User: Jesse Glick Path: cps/src/main/java/org/jenkinsci/plugins/workflow/cps/replay/ReplayCommand.java http://jenkins-ci.org/commit/workflow-cps-plugin/9a8a08a96877833c5e3620c458ecf2f315688a3e Log: Deleting comment now filed as JENKINS-33438. Originally-Committed-As: 1d45a6ea661f84f3588668bc0c9a023510303cd9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-32819) Pipeline compilation error detection broken when using CSRF detection
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32819 Re: Pipeline compilation error detection broken when using CSRF detection Code changed in jenkins User: Antonio Muñiz Path: cps/src/main/js/workflow-editor.js http://jenkins-ci.org/commit/workflow-cps-plugin/90f3cd32abeabce44961bcc4c0e33fbb85be67f3 Log: JENKINS-32819 Fix script compilation check when CSRF is enabled Originally-Committed-As: a5fdddee3fb14028612df3032414f9d5a1f6dcea Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [js-modules] (JENKINS-33245) jquery-detached creates directory structure with 21 webapp subdirectories
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33245 Re: jquery-detached creates directory structure with 21 webapp subdirectories Code changed in jenkins User: tfennelly Path: cps/pom.xml http://jenkins-ci.org/commit/workflow-cps-plugin/1e99a8cbe1afbb2934c548171175e5d8c208379e Log: Use repackaged jQuery HPI The jQuery plugin was bloated due to a bad assembly. See JENKINS-33245 . Originally-Committed-As: c83b2cc9f1759c0efd02ca39be4e110c197986f7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-22767) AbstractLazyLoadRunMap.getById subject to race condition with .load
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22767 Re: AbstractLazyLoadRunMap.getById subject to race condition with .load Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-job-plugin/c9849559467a7e3af97953262f4bd274031b523b Log: JENKINS-22767 Noting symptom. Originally-Committed-As: a8073443b901b0cde63dacec2f82f9691833744b Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-32214) Workflow and svn polling
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32214 Re: Workflow and svn polling Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java http://jenkins-ci.org/commit/workflow-job-plugin/7d44f65c3e0d06110627f3bbb0765f14e319f27a Log: [FIXED JENKINS-32214] WorkflowJob.poll should give preference to any SCMRevisionState from the latest running build. Originally-Committed-As: 05e46bc4c66a5e0db4f5cced25f824d022b1d95a Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30395) ClosedByInterruptException in JenkinsRule setup
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30395 Re: ClosedByInterruptException in JenkinsRule setup Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/DynamicEnvironmentExpanderTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunRestartTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java http://jenkins-ci.org/commit/workflow-job-plugin/edf1cd0564930316ce4878a09b29088496a4d535 Log: JENKINS-30395 Deleting workaround now that we can use jenkins-test-harness 2.0. Originally-Committed-As: 109b8f82415fc41f24d5d6545e586f0bce7ba705 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33971) WorkflowJob not reliably started from ReverseBuildTrigger after restart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33971 Re: WorkflowJob not reliably started from ReverseBuildTrigger after restart Code changed in jenkins User: Jesse Glick Path: job/src/test/java/org/jenkinsci/plugins/workflow/ReverseBuildTriggerTest.java http://jenkins-ci.org/commit/workflow-job-plugin/9b098c6ef36e90433466ca0b40f8f5a689ffa74b Log: JENKINS-33971 Integration test for ReverseBuildTrigger.upstream2Trigger bug. Originally-Committed-As: d2e726274b919aa3492d195dc75bf39711df7c2b Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
