[JIRA] [sonar] (JENKINS-34942) sonar runner configurations lost in jobs configurations since moved to 'global tools config' section
Title: Message Title Alexandre Aubert commented on JENKINS-34942 Re: sonar runner configurations lost in jobs configurations since moved to 'global tools config' section I can confirm that both problems are well fixed in this version. thanks. 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] [publish-over-ssh-plugin] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Title: Message Title David Turner commented on JENKINS-17058 Re: Publish over SSH plugin XML configuration cannot be read on jenkins start up. Hi All, For clarity, can someone please answer this q'n? We're still on Jenkins 1.509.2 LTS, Windows exe, bundled 1.6 Java RE (like Brett Delle Grazie above) and have this problem. I am browsing the GitHub forks trying to work out the necessary dependencies to obtain a compatible 'fix' for Publish Over SSH without updating Java RE or Jenkins core. Will the 'fixed' SSH 1.11 work on 1.509 LTS and J6RE despite the apparent new baseline? Ref from the MANIFEST.MFs: Plugin-Version: 1.10 Hudson-Version: 1.388 Build-Jdk: 1.6.0_32 Depends on Publish-Over: 0.17 Plugin-Version: 1.11 Hudson-Version: 1.532.1 Jenkins-Version: 1.532.1 Build-Jdk: 1.7.0_45 Depends on Publish-Over: 0.18 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] [pipeline-stage-view-plugin] (JENKINS-34791) Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34791 Re: Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded limits Code changed in jenkins User: Sam Van Oort Path: rest-api/src/main/java/com/cloudbees/workflow/rest/external/FlowNodeLogExt.java rest-api/src/main/java/com/cloudbees/workflow/rest/external/JobExt.java rest-api/src/main/java/com/cloudbees/workflow/rest/external/RunExt.java rest-api/src/main/java/com/cloudbees/workflow/rest/external/StageNodeExt.java ui/src/main/js/model/runs-stage-grouped.js http://jenkins-ci.org/commit/pipeline-stage-view-plugin/c5ca0a9190773ec211f1899cbd0c5eb4b3cec31d Log: Properties to configure hardcoded limits on APIs - JENKINS-34791 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] [pipeline-stage-view-plugin] (JENKINS-34791) Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-34791 Pipeline stage plugin shows "No data available..." if active builds are more then 10 AND provide system properties to override stage view hardcoded limits Change By: Sam Van Oort Issue Type: Bug Improvement 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] [htmlpublisher-plugin] (JENKINS-35397) CSS issue while reports are generated.
Title: Message Title mcrooney resolved as Not A Defect That's the right link, you'll want to read the whole thing and especially the section on HTML Publisher. You'll need to change your CSP policy for Jenkins. See other recent bug reports for HTML Publisher for more details and solutions Jenkins / JENKINS-35397 CSS issue while reports are generated. Change By: mcrooney 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] [workflow-multibranch-plugin] (JENKINS-35144) Disable Pipeline Multibranch sub projects
Title: Message Title Patrick Wolf commented on JENKINS-35144 Re: Disable Pipeline Multibranch sub projects This seems related to JENKINS-32396 - Option to suppress automatic SCM trigger JENKINS-32396 provides an option in the UI to suppress builds matching a pattern from executing. This met the use case of suppressing all automatic builds of designated jobs but does not allow for suppressing future builds of the job via the pipeline script itself. A "property" in pipeline to enable this suppression, if possible, would work here. The first build with the property would still run, even if it didn't do anything but set the property, but subsequent runs would not be triggered. 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-35453) Allow disabling the default commit status notifier
Title: Message Title Dominic Scheirlinck created an issue Jenkins / JENKINS-35453 Allow disabling the default commit status notifier Issue Type: Improvement Assignee: Jesse Glick Components: github-branch-source-plugin Created: 2016/Jun/08 12:16 AM Priority: Minor Reporter: Dominic Scheirlinck In JENKINS-33151 , giving users the option to disable the default commit status notifier was raised (in lieu of more complex configuration, such as the ability to change the context string, which is hard-coded to 'Jenkins': https://github.com/jenkinsci/github-branch-source-plugin/blob/master@%7B2016-06-08%7D/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubBuildStatusNotification.java#L78) I think there's probably a use case for this, and it would allow users with more complicated status logic (such as in that ticket) to implement their own, and just opt out of the default one. Add Comment
[JIRA] [core] (JENKINS-35452) Change Jnlp url from "slave-agent.jnlp" to "agent.jnlp"
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-35452 Change Jnlp url from "slave-agent.jnlp" to "agent.jnlp" Change By: Liam Newman Found when launching a jnlp agent from command line:"java ... -jnlpUrl http://localhost/computer/agent_name/slave-agent.jnlp"The name of this file should match agreed naming guidelines - "agent . jnlp" or "jenkins-agent.jnlp". 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-35447) bug on moveing pipeline projects into folder
Title: Message Title Hang Dong updated an issue Jenkins / JENKINS-35447 bug on moveing pipeline projects into folder Change By: Hang Dong Component/s: workflow-plugin Component/s: core 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-35452) Change Jnlp url from "slave-agent.jnlp" to "agent.jnlp"
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-35452 Change Jnlp url from "slave-agent.jnlp" to "agent.jnlp" Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/08 12:02 AM Environment: Jenkins 2.6 Priority: Minor Reporter: Liam Newman Found when launching a jnlp agent from command line: "java ... -jnlpUrl http://localhost/computer/agent_name/slave-agent.jnlp" The name of this file should match agreed naming guidelines. Add Comment
[JIRA] [workflow-plugin] (JENKINS-35447) bug on moveing pipeline projects into folder
Title: Message Title Hang Dong updated an issue Jenkins / JENKINS-35447 bug on moveing pipeline projects into folder Change By: Hang Dong Labels: pipeline 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-35447) bug on moveing pipeline projects into folder
Title: Message Title
Hang Dong updated an issue
Jenkins / JENKINS-35447
bug on moveing pipeline projects into folder
Change By:
Hang Dong
Trying out folder in jenkins 2.x, on moving a project (a pipline project to be specific) with no previous failure/instabilty, encountered a stack trace. The project did move, but none of the history made it. Perhaps lastUnstableBuild link doesn't exist for project with no prior unstable runs? Edit: tried the same with a freestyle project, that moved okey. Looks like it's likely specific to pipeline project. {code:java}Stack tracejava.io.FileNotFoundException: /local/mnt/workspace/jenkins/build_record/pipeline-test/lastUnstableBuild (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:146) at org.apache.commons.io.FileUtils.doCopyFile(FileUtils.java:1138) at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1428) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1389) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1261) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1230) at org.apache.commons.io.FileUtils.moveDirectory(FileUtils.java:2755) at hudson.model.Job.movedTo(Job.java:683) at hudson.model.Items.move(Items.java:438) at com.cloudbees.hudson.plugins.folder.relocate.StandardHandler.doMove(StandardHandler.java:73) at com.cloudbees.hudson.plugins.folder.relocate.StandardHandler.handle(StandardHandler.java:65) at com.cloudbees.hudson.plugins.folder.relocate.DefaultRelocationUI.doMove(DefaultRelocationUI.java:121) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at
[JIRA] [core] (JENKINS-35447) bug on moveing pipeline projects into folder
Title: Message Title Hang Dong updated an issue Jenkins / JENKINS-35447 bug on moveing pipeline projects into folder Change By: Hang Dong Summary: bug on moveing pipeline projects into folder 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-35451) Change name of "slave.jar" to "agent.jar"
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-35451 Change name of "slave.jar" to "agent.jar" Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/07 11:58 PM Environment: Jenkins 2.6 Priority: Minor Reporter: Liam Newman Found when launching a jnlp agent from command line: "java -jar slave.jar -jnlpUrl ..." The name of this jar should match agreed naming guidelines. Add Comment
[JIRA] [core] (JENKINS-35450) Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-35450 Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/07 11:52 PM Priority: Minor Reporter: Liam Newman Found while using Jenkins 2.6 docker container, so it needs to be fixed both there and in core. Add Comment This message was sent
[JIRA] [core] (JENKINS-35449) Review and document all remaining uses of the term "slave" in core
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-35449 Review and document all remaining uses of the term "slave" in core Change By: Liam Newman Summary: Review and document all remaining uses of the term "slave" in Jenkins core 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-35449) Review and document all remaining uses of the term "slave" in Jenkins
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-35449 Review and document all remaining uses of the term "slave" in Jenkins Issue Type: Task Assignee: Unassigned Components: core Created: 2016/Jun/07 11:41 PM Priority: Major Reporter: Liam Newman JENKINS-27268 has been resolved but there are still many occurrences of the term "slave" in Jenkins core. Some of these are too hard to fix others are not, but it is unclear which are which. We've put significant effort into removing this term. To make good on that investment, any publich-facing stragglers, bugs need to be filed and linked for all remaining usages of "slave" in Jenkins core. Otherwise, the term will continue to be part of the project's vernacular. Add Comment
[JIRA] [core] (JENKINS-35448) File issues against plugins in jenkinsci github org that use the term "slave" for agents
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-35448 File issues against plugins in jenkinsci github org that use the term "slave" for agents Issue Type: Task Assignee: Unassigned Components: core Created: 2016/Jun/07 11:22 PM Priority: Minor Reporter: Liam Newman Following the completion of JENKINS-31095, issues need to be filed against plugins in the jenkinsci org on github to clean up their terminology as well. Add Comment
[JIRA] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title Zhelyan Panchev commented on JENKINS-35140 Re: JsonSlurper does not work after updating to Jenkins 2.x weird but now it works in Jenkins 2.7 with or without @NonCPS.. I don't think anything changed apart from restarting Jenkins couple of times and upgrading https://github.com/jenkinsci/pipeline-build-step-plugin to 2.1 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] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title
Zhelyan Panchev updated an issue
Jenkins / JENKINS-35140
JsonSlurper does not work after updating to Jenkins 2.x
Change By:
Zhelyan Panchev
Comment:
same code works in Jenkins 2.7 with or without {{\@NonCPS}} after upgrading https://github.com/jenkinsci/pipeline-build-step-plugin to 2.1
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] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title
Zhelyan Panchev edited a comment on JENKINS-35140
Re: JsonSlurper does not work after updating to Jenkins 2.x
same code works in Jenkins 2.7 with or without {{\@NonCPS}} after upgrading https://github.com/jenkinsci/pipeline-build-step-plugin to 2.1
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] [script-security-plugin] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title Zhelyan Panchev commented on JENKINS-35140 Re: JsonSlurper does not work after updating to Jenkins 2.x same code works in Jenkins 2.7 with or without @NonCPS 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-35447) bug on moveing projects into folder
Title: Message Title Hang Dong created an issue Jenkins / JENKINS-35447 bug on moveing projects into folder Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/07 10:26 PM Environment: Jenkins ver. 2.8 running on Ubuntu 14.04 Priority: Minor Reporter: Hang Dong Trying out folder in jenkins 2.x, on moving a project (a pipline project to be specific) with no previous failure/instabilty, encountered a stack trace. The project did move, but none of the history made it. Perhaps lastUnstableBuild link doesn't exist for project with no prior unstable runs? Stack trace java.io.FileNotFoundException: /local/mnt/workspace/jenkins/build_record/pipeline-test/lastUnstableBuild (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:146) at org.apache.commons.io.FileUtils.doCopyFile(FileUtils.java:1138) at org.apache.commons.io.FileUtils.doCopyDirectory(FileUtils.java:1428) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1389) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:1261) at
[JIRA] [acceptance-test-harness] (JENKINS-35446) MavenPluginTest.use_native_mvn is erratic
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-35446 MavenPluginTest.use_native_mvn is erratic Issue Type: Bug Assignee: Andrew Bayer Components: acceptance-test-harness Created: 2016/Jun/07 10:19 PM Priority: Minor Reporter: Andrew Bayer Like JENKINS-31060 , this test is heavily dependent on test environment configuration to actually work and doesn't really test anything valuable in the first place, so let's remove it. Add Comment
[JIRA] [jenkins-test-harness] (JENKINS-35445) Incorrect packaging of Apache HttpComponents in hpi files
Title: Message Title Andres Rodriguez started work on JENKINS-35445 Change By: Andres Rodriguez Status: Open In Progress 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] [jenkins-test-harness] (JENKINS-35445) Incorrect packaging of Apache HttpComponents in hpi files
Title: Message Title Andres Rodriguez created an issue Jenkins / JENKINS-35445 Incorrect packaging of Apache HttpComponents in hpi files Issue Type: Bug Assignee: Andres Rodriguez Components: jenkins-test-harness Created: 2016/Jun/07 10:07 PM Environment: New parent POM. Split JTH Priority: Minor Reporter: Andres Rodriguez When migrating plugins to the new parent POM and the split JTH, one of the most usual issues are incompatibilities between the versions of Apache HttpComponents used by the plugin itself (in many cases indirectly through its dependencies) and the one brought by the HtmlUnit dependency of the JTH. Normally some juggling the dependencies orders and scopes saves the day, but we are starting to see cases where a configuration that let compilation and tests (including InjectedTests) run turns out building an hpi file that is not the one intended. The fact that Maven 3 (correctly, imho) gets rid of the possibility of having different versions of a dependency in different scopes, also contributes to this situation (meaning that this behavior could have been a workaround in Maven 2). E.g., in aws-java-sdk-plugin#3, introducing the version of httpclient needed for the InjectedTests in the test scope (we should not upgrade a dependency of a
[JIRA] [external-workspace-manager-plugin] (JENKINS-35440) Implement a second fallback when searching for disk definitions
Title: Message Title Alexandru Somai commented on JENKINS-35440 Re: Implement a second fallback when searching for disk definitions Thank you Martin for adding this comment. The issue description that I've provided was a bit ambiguous, but your comment makes it more clear. 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-35444) java.io.NotSerializableException issues even with @NonCPS
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-35444 java.io.NotSerializableException issues even with @NonCPS Change By: Andrew Bayer Assignee: Antonio Muñiz Andrew Bayer 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-35444) java.io.NotSerializableException issues even with @NonCPS
Title: Message Title
Trevor Hartman updated an issue
Jenkins / JENKINS-35444
java.io.NotSerializableException issues even with @NonCPS
Change By:
Trevor Hartman
I get java.io.NotSerializableException: java.util.regex.Matcher on:{code: groovy java }@NonCPSdef extractLatency(linesArr) { latency = [:] println "extractLatency" for (int j = 0; j < linesArr.size(); j++) {line = linesArr[j]println("looping over line: $line")// Matches lines like: Connect:01 0.1 1 1abPattern = /(\w+)\:\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)/def matcher = { (line =~ abPattern) }if (matcher().size > 1) { println("matched")}matcher = nullabPattern = null } return latency}{code}If I throw a @NonCPS on the inner `def matcher` it fixes it.
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-35444) java.io.NotSerializableException issues even with @NonCPS
Title: Message Title
Andrew Bayer updated an issue
Jenkins / JENKINS-35444
java.io.NotSerializableException issues even with @NonCPS
Change By:
Andrew Bayer
Component/s:
workflow-plugin
Component/s:
pipeline-milestone-step-plugin
I get java.io.NotSerializableException: java.util.regex.Matcher on:{code: java groovy }@NonCPSdef extractLatency(linesArr) { latency = [:] println "extractLatency" for (int j = 0; j < linesArr.size(); j++) {line = linesArr[j]println("looping over line: $line")// Matches lines like: Connect:01 0.1 1 1abPattern = /(\w+)\:\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)/def matcher = { (line =~ abPattern) }if (matcher().size > 1) { println("matched")}matcher = nullabPattern = null } return latency}{code}If I throw a @NonCPS on the inner `def matcher` it fixes it.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are
[JIRA] [acceptance-test-harness] (JENKINS-35443) ATH: InternalUsersTest.Create, update and delete user fails on 1.x
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-35443 ATH: InternalUsersTest.Create, update and delete user fails on 1.x Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2016/Jun/07 9:53 PM Priority: Minor Reporter: Andrew Bayer "InternalUsersTest.Create, update and delete user" fails on 1.x but not on 2.x - not sure whether we need to worry about fixing it on 1.x or if we should just disable it when running against 1.x. Add Comment
[JIRA] [pipeline-milestone-step-plugin] (JENKINS-35444) java.io.NotSerializableException issues even with @NonCPS
Title: Message Title
Trevor Hartman created an issue
Jenkins / JENKINS-35444
java.io.NotSerializableException issues even with @NonCPS
Issue Type:
Bug
Assignee:
Antonio Muñiz
Components:
pipeline-milestone-step-plugin
Created:
2016/Jun/07 9:53 PM
Priority:
Minor
Reporter:
Trevor Hartman
I get java.io.NotSerializableException: java.util.regex.Matcher on:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
@NonCPS
def extractLatency(linesArr) {
latency = [:]
println "extractLatency"
for (int j = 0; j < linesArr.size(); j++) {
line = linesArr[j]
println("looping over line: $line")
// Matches lines like: Connect:01 0.1 1 1
abPattern = /(\w+)\:\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)/
def matcher = { (line =~ abPattern) }
if (matcher().size > 1) {
println("matched")
}
matcher = null
abPattern = null
}
return latency
}
If I throw a @NonCPS on the inner `def matcher` it fixes it.
[JIRA] [structs-plugin] (JENKINS-35395) Snippet Generator no longer includes global variables
Title: Message Title Andrew Bayer commented on JENKINS-35395 Re: Snippet Generator no longer includes global variables PR up - https://github.com/jenkinsci/workflow-cps-plugin/pull/17 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] [structs-plugin] (JENKINS-35395) Snippet Generator no longer includes global variables
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-35395 Snippet Generator no longer includes global variables Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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] [structs-plugin] (JENKINS-35395) Snippet Generator no longer includes global variables
Title: Message Title Andrew Bayer commented on JENKINS-35395 Re: Snippet Generator no longer includes global variables Whoops, when I moved it around it worked. PR incoming. 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] [structs-plugin] (JENKINS-35395) Snippet Generator no longer includes global variables
Title: Message Title Andrew Bayer commented on JENKINS-35395 Re: Snippet Generator no longer includes global variables I tried copy-pasting it into block.jelly and it didn't work - it gets the dropdown list of the GlobalVariable that are available but doesn't render the 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] [core] (JENKINS-16143) Jenkins escapes 2 dollar signs in the Parameterized Build fields
Title: Message Title
Kevin R. edited a comment on JENKINS-16143
Re: Jenkins escapes 2 dollar signs in the Parameterized Build fields
same issue for me too. printing out the shell env ( {{ env }} command) shows that the env var is automatically setting {{value$}}instead of{{value$$}} Jenkins 2.0, CentOS7
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-16143) Jenkins escapes 2 dollar signs in the Parameterized Build fields
Title: Message Title Kevin R. commented on JENKINS-16143 Re: Jenkins escapes 2 dollar signs in the Parameterized Build fields same issue for me too. printing out the shell env (env command) shows that the env var is automatically setting value$ instead of value$$ 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] [external-workspace-manager-plugin] (JENKINS-35440) Implement a second fallback when searching for disk definitions
Title: Message Title Martin d'Anjou commented on JENKINS-35440 Re: Implement a second fallback when searching for disk definitions Thank you for capturing this in Jira Alex. You are very thorough! In the current design, the user has to provide a global configuration, plus either 1) node configuration, or 2) template configuration. The idea when I suggested the second fallback was that in homogeneous networks, where all nodes have the same mounts as the master node - or in even smaller cases with only a master node, only a global configuration would be needed. This in fact reduces the amount of user configuration, at the cost of some internal complexity, and some additional documentation. 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-plugin] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Will Hughes edited a comment on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens I am having the same problem Edit: And I can also confirm that if I make a freestyle project with the same repo and trigger the webhook, Jenkins recognises this and starts the build (only for the freestyle project) 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-parameter-plugin] (JENKINS-35363) Git parameter filter doesn't work
Title: Message Title George Sakhnovsky edited a comment on JENKINS-35363 Re: Git parameter filter doesn't work Thanks Boguslaw, installing the JQuery plugin (https://wiki.jenkins-ci.org/display/JENKINS/jQuery+Plugin) resolved this issue for us.As this is a mandatory dependency, does it make sense to declare it? As per https://wiki.jenkins-ci.org/display/JENKINS/Dependencies+among+plugins 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-plugin] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Will Hughes commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens I am having the same 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] [git-parameter-plugin] (JENKINS-35363) Git parameter filter doesn't work
Title: Message Title George Sakhnovsky commented on JENKINS-35363 Re: Git parameter filter doesn't work Thanks Boguslaw, installing the JQuery plugin (https://wiki.jenkins-ci.org/display/JENKINS/jQuery+Plugin) resolved this issue for us. As this is a mandatory dependency, does it make sense to declare it? As per https://wiki.jenkins-ci.org/display/JENKINS/Dependencies+among+plugins 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-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Sam Van Oort resolved as Fixed Appears to be resolved by the fix to the queue issue. Jenkins / JENKINS-34256 Preparing Jenkins For Shutdown Hangs Running Pipelines Change By: Sam Van Oort Status: Reopened 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-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Sam Van Oort commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines Daniel Ruoso Excellent! I'm going to go ahead and close this one out as a duplicate of the other one then. 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-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Daniel Ruoso commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines I just tested with latest Jenkins release and I can't reproduce the bug. When I initially reported this Jenkins2 was not really released, it is now... I'll just move to the new version. 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-34668) Layout broken in SetupWizard
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-34668 Layout broken in SetupWizard Change By: Keith Zantow Assignee: Manuel Recena Soto Keith Zantow 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-34668) Layout broken in SetupWizard
Title: Message Title Keith Zantow started work on JENKINS-34668 Change By: Keith Zantow Status: Open In Progress 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] [external-workspace-manager-plugin] (JENKINS-35281) [EWM] Implement the exwsAllocate step for the downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35281 Re: [EWM] Implement the exwsAllocate step for the downstream job Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/77b50de952eac5ec566d9048891a1d7212677704 Log: JENKINS-35281 Add logging and register run actions for both upstream and downstream jobs 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] [external-workspace-manager-plugin] (JENKINS-35281) [EWM] Implement the exwsAllocate step for the downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35281 Re: [EWM] Implement the exwsAllocate step for the downstream job Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/model/ExternalWorkspace.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/bd8a5bbb7d450f1128b1358b45ac3f7e09f52515 Log: JENKINS-35281 Error message enhancement Compare: https://github.com/jenkinsci/external-workspace-manager-plugin/compare/7198be72a11c^...bd8a5bbb7d45 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] [external-workspace-manager-plugin] (JENKINS-35281) [EWM] Implement the exwsAllocate step for the downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35281 Re: [EWM] Implement the exwsAllocate step for the downstream job Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/81e95d8d2806e31f79a7d338bcba874dca52753e Log: JENKINS-35281 Fix FindBugs warnings 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] [external-workspace-manager-plugin] (JENKINS-35281) [EWM] Implement the exwsAllocate step for the downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35281 Re: [EWM] Implement the exwsAllocate step for the downstream job Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/actions/ExwsAllocateAction.java src/main/resources/org/jenkinsci/plugins/ewm/Messages.properties http://jenkins-ci.org/commit/external-workspace-manager-plugin/51a53781bd6cd8e248ff674f92e1d708bad6999c Log: JENKINS-35281 Set folder icon for ExwsAllocateAction and use Jenkins localization for display name 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] [external-workspace-manager-plugin] (JENKINS-35281) [EWM] Implement the exwsAllocate step for the downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35281 Re: [EWM] Implement the exwsAllocate step for the downstream job Code changed in jenkins User: Alexandru Somai Path: pom.xml src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/2a7d8a112a310ffd1bee2da7a5217bc4e74da376 Log: JENKINS-35281 Implement the downstream job functionality 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] [external-workspace-manager-plugin] (JENKINS-35281) [EWM] Implement the exwsAllocate step for the downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35281 Re: [EWM] Implement the exwsAllocate step for the downstream job Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/actions/ExwsAllocateAction.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/model/ExternalWorkspace.java src/main/resources/org/jenkinsci/plugins/ewm/actions/ExwsAllocateAction/index.jelly http://jenkins-ci.org/commit/external-workspace-manager-plugin/7198be72a11c595430520b687a6473c67b704016 Log: JENKINS-35281 Register the exwsAllocate information at a run Action, which will be later used by the downstream job 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-parameter-plugin] (JENKINS-35363) Git parameter filter doesn't work
Title: Message Title Boguslaw Klimas commented on JENKINS-35363 Re: Git parameter filter doesn't work Hi, You don't have jquery in jenkins please install jquery plugin Regards Boguslaw 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-35424) No build history (queue?) in job configuration pages
Title: Message Title Serg Pr edited a comment on JENKINS-35424 Re: No build history (queue?) in job configuration pages For me, it is very important to see the build history on the left side in job configuration page. When I configuring the job, very often, for example, I need to open console from the build history. But now, I should open my job in new window -> find my build -> and open the console. In old jenkins (ver.1) I can see and open the build on the left side of my job configuration page without unnecessary movements and without closing or saving my configuration page .I have configured a lot of jobs and I spend a lot of time for searching build history of my opened configuration page, if you understand what I mean. 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-34751) StackOverflowError in Groovy scripts
Title: Message Title Daniel Spilker commented on JENKINS-34751 Re: StackOverflowError in Groovy scripts Follow-up PR to update to Groovy 2.4.7: https://github.com/jenkinsci/jenkins/pull/2399 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-35424) No build history (queue?) in job configuration pages
Title: Message Title Serg Pr commented on JENKINS-35424 Re: No build history (queue?) in job configuration pages For me, it is very important to see the build history on the left side in job configuration page. When I configuring the job, very often, for example, I need to open console from the build history. But now, I should open my job in new window -> find my build -> and open the console. In old jenkins (ver.1) I can see and open the build on the left side of my job configuration page without unnecessary movements. I have configured a lot of jobs and I spend a lot of time for searching build history of my opened configuration page, if you understand what I mean. 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] [external-workspace-manager-plugin] (JENKINS-35244) [EWM] Implement the exws step
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35244 Re: [EWM] Implement the exws step Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsExecution.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/8507d271399b594845b16dd95e02980f64d126f4 Log: JENKINS-35244 Enhance exception messages 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-plugin] (JENKINS-35442) Jenkins2 credentials lost during plugin install
Title: Message Title Ryan Frizzell commented on JENKINS-35442 Re: Jenkins2 credentials lost during plugin install I forgot to add upon using the plugin updater or installing a new pluging, you need to check the box "Restart Jenkins when installation is complete and no jobs are running" in order to reproduce the issue. presently we workd around the issue by installing/updating plugins, then executing systemct restart jenkins 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] [antisamy-markup-formatter-plugin] (JENKINS-31616) "Safe HTML" vulnerable to protocol-relative form action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31616 Re: "Safe HTML" vulnerable to protocol-relative form action Code changed in jenkins User: Daniel Beck Path: src/main/java/hudson/markup/MyspacePolicy.java src/test/java/hudson/markup/MyspacePolicyTest.java http://jenkins-ci.org/commit/antisamy-markup-formatter-plugin/bf3758df15828bec772322fd7ad629df1d40571c Log: [FIX JENKINS-31616] Prohibit scheme-relative URLs 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] [antisamy-markup-formatter-plugin] (JENKINS-31616) "Safe HTML" vulnerable to protocol-relative form action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31616 Re: "Safe HTML" vulnerable to protocol-relative form action Code changed in jenkins User: Steven Christou Path: src/main/java/hudson/markup/MyspacePolicy.java src/test/java/hudson/markup/MyspacePolicyTest.java http://jenkins-ci.org/commit/antisamy-markup-formatter-plugin/3f7c587cde27d59d4d549f5a5a5c15ddf66631e4 Log: Merge pull request #4 from daniel-beck/ JENKINS-31616 [FIX JENKINS-31616] Prohibit scheme-relative URLs Compare: https://github.com/jenkinsci/antisamy-markup-formatter-plugin/compare/d4c35338718a...3f7c587cde27 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] [antisamy-markup-formatter-plugin] (JENKINS-31616) "Safe HTML" vulnerable to protocol-relative form action
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31616 "Safe HTML" vulnerable to protocol-relative form action 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] [credentials-plugin] (JENKINS-35442) Jenkins2 credentials lost during plugin install
Title: Message Title Ryan Frizzell created an issue Jenkins / JENKINS-35442 Jenkins2 credentials lost during plugin install Issue Type: Bug Assignee: stephenconnolly Components: credentials-plugin Created: 2016/Jun/07 7:43 PM Labels: jenkins2.0 credentials Priority: Minor Reporter: Ryan Frizzell We've got Jenkins2 running with 4 build slaves (via ssh). We're running Jenkins 2.6 presently. When going into the plugin manager and selecting "download now and install after restart", upon restart, the credentials used to contact the slaves are gone. In order to get things back up, we have to re-create the credential then re-connect the slaves. What's interesting is that we can update and install plugins, then restart jenkins via systemd, then things seem to work fine...no lost credentials, not need to re-create credentials or re-connect slaves. OS details: LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: CentOS Description: CentOS Linux release 7.2.1511 (Core) Release: 7.2.1511 Codename: Core
[JIRA] [core] (JENKINS-35441) New permission for Viewing Plugin Info
Title: Message Title Thanh Ha created an issue Jenkins / JENKINS-35441 New permission for Viewing Plugin Info Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Jun/07 7:40 PM Priority: Major Reporter: Thanh Ha Currently the permission to view plugin information and their version is tied to the administrator permission. We'd like an improvement to split off this permission to a separate view plugin info permission which can be assigned to a user. We use a tool called Jenkins Job Builder (JJB) which uses the view plugin info permission to figure out which version of the plugin is installed and it figures out what the appropriate XML to generate is based on the plugin version. Having a separate permission to view the plugin version would be handy so that we are not required to give JJB tool full administrator rights. Add Comment
[JIRA] [external-workspace-manager-plugin] (JENKINS-35440) Implement a second fallback when searching for disk definitions
Title: Message Title Alexandru Somai created an issue Jenkins / JENKINS-35440 Implement a second fallback when searching for disk definitions Issue Type: Improvement Assignee: Alexandru Somai Components: external-workspace-manager-plugin Created: 2016/Jun/07 7:32 PM Priority: Minor Reporter: Alexandru Somai Consider the following use case for the external workspace manager plugin: all the nodes have the same mounts as the master node (e.g. in a homogeneous network). Currently, the 'exws' step looks for the disk definitions in the External Workspace Template (from global config) and the fallbacks to the Node configuration. For this use case, it may be useful to have a second fallback condition: External Workspace Definitions (global config). So the search order would be: template, node, global. See the discussions on https://github.com/jenkinsci/external-workspace-manager-plugin/pull/6 Add Comment
[JIRA] [ssh-slaves-plugin] (JENKINS-35439) Adapt to the new bouncycastle-api plugin
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-35439 Adapt to the new bouncycastle-api plugin Issue Type: Task Assignee: Antonio Muñiz Components: ssh-slaves-plugin Created: 2016/Jun/07 7:14 PM Priority: Major Reporter: Antonio Muñiz Adapt to the new bouncycastle-api plugin. A detailed explanation of the need to this API plugin is in its own README. Add Comment This message was
[JIRA] [ssh-slaves-plugin] (JENKINS-35439) Adapt to the new bouncycastle-api plugin
Title: Message Title Antonio Muñiz started work on JENKINS-35439 Change By: Antonio Muñiz Status: Open In Progress 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] [delivery-pipeline-plugin] (JENKINS-25541) Supports Dashboard View portlets
Title: Message Title Suresh Kumar edited a comment on JENKINS-25541 Re: Supports Dashboard View portlets [~tommysdk] Did you got PR for this submitted along with Unit Tests.https://github.com/Diabol/delivery-pipeline-plugin/pull/188Have a chance to look it into this . Thanks 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-fleet-plugin] (JENKINS-35438) Fleet always keeps at least one instance
Title: Message Title Paul Draper created an issue Jenkins / JENKINS-35438 Fleet always keeps at least one instance Issue Type: Bug Assignee: Aleksei Besogonov Components: ec2-fleet-plugin Created: 2016/Jun/07 6:38 PM Priority: Major Reporter: Paul Draper At least one instance is always running, regardless of the number of queued jobs. The is a limitation of the AWS API. It can be worked around (e.g. cancelling and creating fleets as necessary); otherwise, this surprising limitation should at least be documented. Add Comment
[JIRA] [p4-plugin] (JENKINS-35437) Build Review self helps are missing
Title: Message Title dan tran created an issue Jenkins / JENKINS-35437 Build Review self helps are missing Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Jun/07 6:08 PM Priority: Minor Reporter: dan tran I would be helpful to see field descriptions Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [jacoco-plugin] (JENKINS-35436) Add legend for 'M' & 'C' labels in JaCoCo Coverage Reports
Title: Message Title Larry West updated an issue Jenkins / JENKINS-35436 Add legend for 'M' & 'C' labels in JaCoCo Coverage Reports Change By: Larry West Summary: Add legend for 'M' & 'C' labels in JaCoCo Coverage Reports 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] [jacoco-plugin] (JENKINS-35436) Add legend for 'M' & 'C' labels in Coverage Reports
Title: Message Title Larry West created an issue Jenkins / JENKINS-35436 Add legend for 'M' & 'C' labels in Coverage Reports Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2016/Jun/07 6:05 PM Environment: Jenkins 1.64.4.2 Priority: Minor Reporter: Larry West The Overall Coverage Summary and Coverage Breakdown by Package have graphic bars showing percentages, and associated labels 'M' and 'C'. Although seemingly obvious, for people who don't breathe code coverage these can be mysterious. It would help to have a little legend under those tables saying something like 'M' = Missed, 'C' = Covered
[JIRA] [ec2-fleet-plugin] (JENKINS-35435) Test connection doesn't work
Title: Message Title Paul Draper created an issue Jenkins / JENKINS-35435 Test connection doesn't work Issue Type: Bug Assignee: Aleksei Besogonov Components: ec2-fleet-plugin Created: 2016/Jun/07 6:00 PM Priority: Trivial Reporter: Paul Draper Test Connection doesn't seem to use the provided credentials. > Unable to load AWS credentials from any provider in the chain Though the plugin works fine. Add Comment
[JIRA] [js-builder] (JENKINS-35180) transformToJSX handles Path string wrong on windows
Title: Message Title Tom FENNELLY resolved as Fixed This particular issue is resolved not. Thanks for reporting. Jenkins / JENKINS-35180 transformToJSX handles Path string wrong on windows Change By: Tom FENNELLY 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] [external-workspace-manager-plugin] (JENKINS-35192) [EWM] Implement the exwsAllocate step
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35192 Re: [EWM] Implement the exwsAllocate step Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/definitions/Disk.java src/main/java/org/jenkinsci/plugins/ewm/definitions/DiskPool.java src/main/java/org/jenkinsci/plugins/ewm/definitions/Template.java src/main/java/org/jenkinsci/plugins/ewm/nodes/DiskNode.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsStep.java src/main/java/org/jenkinsci/plugins/ewm/steps/model/ExternalWorkspace.java src/main/java/org/jenkinsci/plugins/ewm/strategies/DiskAllocationStrategy.java src/main/java/org/jenkinsci/plugins/ewm/strategies/MostUsableSpaceStrategy.java src/main/resources/org/jenkinsci/plugins/ewm/definitions/Disk/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/definitions/Disk/help-masterMountPoint.html src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep/help-diskPoolId.html src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsAllocateStep/help-upstream.html src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsStep/config.jelly src/main/resources/org/jenkinsci/plugins/ewm/steps/ExwsStep/help-externalWorkspace.html http://jenkins-ci.org/commit/external-workspace-manager-plugin/b22286a9aeb9101ba6b515f4f8337cbac65da049 Log: JENKINS-35192 Implement the exwsAllocate step for the upstream job (#9) JENKINS-35192 Implement the exwsAllocate step for the upstream job JENKINS-35192 Additional null checks JENKINS-35192 Enhance the error messages JENKINS-35192 Use AbortException. Add missing help files JENKINS-35192 Fix FindBugs issues JENKINS-35192 Replace AbortException with IOException for method signatures. Additional minor changes.
[JIRA] [saml-plugin] (JENKINS-35434) Wiki is out-of-sync with 0.5
Title: Message Title Russell Mora created an issue Jenkins / JENKINS-35434 Wiki is out-of-sync with 0.5 Issue Type: Bug Assignee: Ben McCann Components: saml-plugin Created: 2016/Jun/07 5:46 PM Priority: Minor Reporter: Russell Mora The saml-plugin wiki (https://wiki.jenkins-ci.org/display/JENKINS/SAML+Plugin) talks about UserName Attribute, however, this was added to the course code after the 0.5 release. Looks like 0.6 needs to get released, which would probably help with resolving some other open issues like JENKINS-27423 Add Comment
[JIRA] [core] (JENKINS-35433) Move js modules in util & api into separate NPM module
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-35433 Move js modules in util & api into separate NPM module Change By: Keith Zantow Assignee: Keith Zantow 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-35433) Move js modules in util & api into separate NPM module
Title: Message Title Keith Zantow created an issue Jenkins / JENKINS-35433 Move js modules in util & api into separate NPM module Issue Type: Task Assignee: Unassigned Components: core Created: 2016/Jun/07 5:12 PM Priority: Minor Reporter: Keith Zantow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message
[JIRA] [tfs-plugin] (JENKINS-35432) Scheduled builds crash after running for more than 8 hours
Title: Message Title albert chu created an issue Jenkins / JENKINS-35432 Scheduled builds crash after running for more than 8 hours Issue Type: Bug Assignee: Unassigned Components: tfs-plugin Created: 2016/Jun/07 5:07 PM Labels: tfs-plugin Priority: Major Reporter: albert chu I am using VS online, TFS plugin 4.1. I have scheduled builds (every 5 minutes) which checkcode code using the TFS plugin. After 1 or 2 days the builds start failing and I need to restart jenkins. From my initial searches, I believe this is an issue with how the plugin interacts with the TFS Java sdk. https://social.msdn.microsoft.com/Forums/vstudio/en-US/2ace3851-8e1c-4aee-8e2d-192b0810213a/tfs-sdk-leak?forum=tee The workaround is to close the TFSConfigurationServer first and then close the TFSTeamProjectCollection. Future versions of the TFS SDK will take care of closing the TFSConfigurationServer AND throw an exception if you close them the other way around. Here is the log: FATAL: null java.lang.StackOverflowError at
[JIRA] [vsphere-cloud-plugin] (JENKINS-34912) vSphere from Pipeline integation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34912 Re: vSphere from Pipeline integation Code changed in jenkins User: Jason Swager Path: .gitignore pom.xml src/main/java/org/jenkinsci/plugins/vsphere/VSphereBuildStep.java src/main/java/org/jenkinsci/plugins/vsphere/VSphereBuildStepContainer.java src/main/java/org/jenkinsci/plugins/vsphere/builders/Clone.java src/main/java/org/jenkinsci/plugins/vsphere/builders/ConvertToTemplate.java src/main/java/org/jenkinsci/plugins/vsphere/builders/ConvertToVm.java src/main/java/org/jenkinsci/plugins/vsphere/builders/Delete.java src/main/java/org/jenkinsci/plugins/vsphere/builders/DeleteSnapshot.java src/main/java/org/jenkinsci/plugins/vsphere/builders/Deploy.java src/main/java/org/jenkinsci/plugins/vsphere/builders/ExposeGuestInfo.java src/main/java/org/jenkinsci/plugins/vsphere/builders/PowerOff.java src/main/java/org/jenkinsci/plugins/vsphere/builders/PowerOn.java src/main/java/org/jenkinsci/plugins/vsphere/builders/Reconfigure.java src/main/java/org/jenkinsci/plugins/vsphere/builders/ReconfigureCpu.java src/main/java/org/jenkinsci/plugins/vsphere/builders/ReconfigureDisk.java src/main/java/org/jenkinsci/plugins/vsphere/builders/ReconfigureMemory.java src/main/java/org/jenkinsci/plugins/vsphere/builders/ReconfigureNetworkAdapters.java src/main/java/org/jenkinsci/plugins/vsphere/builders/ReconfigureStep.java src/main/java/org/jenkinsci/plugins/vsphere/builders/Rename.java src/main/java/org/jenkinsci/plugins/vsphere/builders/RenameSnapshot.java src/main/java/org/jenkinsci/plugins/vsphere/builders/RevertToSnapshot.java src/main/java/org/jenkinsci/plugins/vsphere/builders/SuspendVm.java src/main/java/org/jenkinsci/plugins/vsphere/builders/TakeSnapshot.java src/main/java/org/jenkinsci/plugins/vsphere/tools/VSphere.java src/main/java/org/jenkinsci/plugins/workflow/vSphereStep.java src/main/resources/org/jenkinsci/plugins/workflow/vSphereStep/config.jelly src/main/resources/org/jenkinsci/plugins/workflow/vSphereStep/help.html http://jenkins-ci.org/commit/vsphere-cloud-plugin/6c7ce63529c64af1b85d1645ef38f9f552dee6b2 Log: Merge pull request #45 from witokondoria/master JENKINS-34912 vSphere from Pipeline integation Compare: https://github.com/jenkinsci/vsphere-cloud-plugin/compare/4545172c82a4...6c7ce63529c6 Add Comment This message was sent by Atlassian JIRA
[JIRA] [core] (JENKINS-35424) No build history (queue?) in job configuration pages
Title: Message Title Daniel Beck commented on JENKINS-35424 Re: No build history (queue?) in job configuration pages This has already been filed by gus reiber. Gus didn't want the sidepanel for the initial config of the job, apparently missing that it'll also remove the sidepanel from any further views. FWIW there's also no explicit 'Cancel' button on the config form, so if you want to leave without saving, browser back or breadcrumbs bar are the only options right now, and they're weird. Previously you could click e.g. 'Status'. 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] [pam-auth-plugin] (JENKINS-35285) Migrate pam-auth-plugin to 2.x parent pom
Title: Message Title Kristin Whetstone closed an issue as Done Jenkins / JENKINS-35285 Migrate pam-auth-plugin to 2.x parent pom Change By: Kristin Whetstone Status: In Progress Closed Resolution: Done 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] [pam-auth-plugin] (JENKINS-35285) Migrate pam-auth-plugin to 2.x parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35285 Re: Migrate pam-auth-plugin to 2.x parent pom Code changed in jenkins User: Manuel Recena Path: pom.xml http://jenkins-ci.org/commit/pam-auth-plugin/2f187f72c321217112aeea50d99e85f42e01e391 Log: Merge pull request #4 from kwhetstone/master JENKINS-35285 Upgrade to parent POM Compare: https://github.com/jenkinsci/pam-auth-plugin/compare/a2e44be63fa8...2f187f72c321 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-35402) Make it possible for plugins to customize the UpdateCenter.InstallationJob created from a custom UpdateSite
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-35402 Make it possible for plugins to customize the UpdateCenter.InstallationJob created from a custom UpdateSite 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-35402) Make it possible for plugins to customize the UpdateCenter.InstallationJob created from a custom UpdateSite
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35402 Re: Make it possible for plugins to customize the UpdateCenter.InstallationJob created from a custom UpdateSite Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/f1dfc7207fc323fcfef1733b3de03ee447e1bd93 Log: Merge pull request #2394 from stephenc/custome-installation-job [FIXED JENKINS-35402] Make it easier for update sites to tweak the InstallationJob Compare: https://github.com/jenkinsci/jenkins/compare/9657629d2e28...f1dfc7207fc3 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-35402) Make it possible for plugins to customize the UpdateCenter.InstallationJob created from a custom UpdateSite
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35402 Re: Make it possible for plugins to customize the UpdateCenter.InstallationJob created from a custom UpdateSite Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/UpdateSite.java http://jenkins-ci.org/commit/jenkins/53f89740e94b7fe9a517d5858e438de3fd80a5f2 Log: [FIXED JENKINS-35402] Make it easier for update sites to tweak the InstallationJob 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] [s3-plugin] (JENKINS-34216) Failed to reset the request input stream
Title: Message Title Kevin Chen commented on JENKINS-34216 Re: Failed to reset the request input stream We're having the same problem since upgrading to 0.10.3. It's intermittent. 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-parameter-plugin] (JENKINS-35363) Git parameter filter doesn't work
Title: Message Title George Sakhnovsky commented on JENKINS-35363 Re: Git parameter filter doesn't work Can replicate on Jenkins 1.653 using Chrome. 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-33983) Multibranch Pipeline with git uses jgit, but should use git installation that is configured
Title: Message Title Nghia Le Van commented on JENKINS-33983 Re: Multibranch Pipeline with git uses jgit, but should use git installation that is configured I have same this 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] [confluence-publisher-plugin] (JENKINS-35431) New page created in wrong place if "Page" does not exist.
Title: Message Title J M created an issue Jenkins / JENKINS-35431 New page created in wrong place if "Page" does not exist. Issue Type: Bug Assignee: Joe Hansche Components: confluence-publisher-plugin Created: 2016/Jun/07 3:38 PM Priority: Major Reporter: J M For example in my Confluence Publisher configuration:: Space FIX OK: Fixnetix Development Page DBX+Dev+Releases/DBX2+Prod3.1.0.$SVN_REVISION.jmg_testing . Which should be created under: http://jira:8090/confluence/display/FIX/DBX2+Dev+Releases But is actually created under: http://jira:8090/confluence/pages/viewpage.action?pageId=28870270 (Which is the root of the FIX space.) This is irrespective of whether build-time parameters are used. Add Comment
[JIRA] [git-parameter-plugin] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Sebastian Mandrean commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM Same here! 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-35430) maven breaks build
Title: Message Title Yuriy Burtsev commented on JENKINS-35430 Re: maven breaks build http://stackoverflow.com/questions/37667409/jenkins-2-7-pipeline-build-in-docker-container 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-35430) maven breaks build
Title: Message Title
Yuriy Burtsev created an issue
Jenkins / JENKINS-35430
maven breaks build
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Jun/07 3:28 PM
Environment:
Jenkins 2.8 maven 3.2.5 or 3.3.3 open or Oracle JDK 1.8 Docker 1.9.1 CentOS 7 with 4.6.0-1.el7.elrepo.x86_64
Labels:
jenkins 2.0 workflow
Priority:
Blocker
Reporter:
Yuriy Burtsev
My Jenkins server is docker container from docker hub, which using docker server as a node (docker). I am trying to build my project with Jenkins and pipeline plugin in docker container. My Jenkinsfile looks like this:
node('docker') { docker.image('build-node:1').inside { stage 'scm checkout' checkout scm
stage 'maven build' try { sh 'mvn clean | tee mvn.log' }
catch (e) { println "Maven failed : $ {e}
" } } }
Output:
[JIRA] [javadoc-plugin] (JENKINS-35286) Migrate javadoc-plugin to 2.x parent pom
Title: Message Title Manuel Recena Soto resolved as Done Jenkins / JENKINS-35286 Migrate javadoc-plugin to 2.x parent pom Change By: Manuel Recena Soto Status: In Progress Resolved Resolution: Done 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] [javadoc-plugin] (JENKINS-35286) Migrate javadoc-plugin to 2.x parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35286 Re: Migrate javadoc-plugin to 2.x parent pom Code changed in jenkins User: Manuel Recena Path: pom.xml http://jenkins-ci.org/commit/javadoc-plugin/7c6d6dc321ceda518ce472c4c8b6ecbcc0ba025e Log: Merge pull request #5 from kwhetstone/parent_pom JENKINS-35286 Upgrade to parent POM Compare: https://github.com/jenkinsci/javadoc-plugin/compare/9f9f795ae041...7c6d6dc321ce 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] [perforce-plugin] (JENKINS-35369) Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment
Title: Message Title Rob Petti commented on JENKINS-35369 Re: Changeset should not be calculated in each run in the job when P4DISABLESYNC has been set in environment This is not an issue. You have set P4DISABLESYNC and P4DISABLECHANGELOG. It is not syncing any changes, and it is not getting any changelog information. This is by design. The results of the line "p4 changes -s submitted -m 1 //job_name/..." is not being used for anything, because you have explicitly disabled everything. Once again, this plugin is deprecated. Use p4-plugin instead. If you have problems with it, contact perforce support or file another ticket against it. 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] [createjobadvanced-plugin] (JENKINS-35404) unable to create a new job in 2.8
Title: Message Title Mahesh Janardhanan closed an issue as Fixed Seems like the plugins were not updated which caused the issue. updating the plugins fixed the issue Jenkins / JENKINS-35404 unable to create a new job in 2.8 Change By: Mahesh Janardhanan 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] [confluence-publisher-plugin] (JENKINS-35429) Add ability to "Publish to Confluence" more than once in a post-build step.
Title: Message Title J M updated an issue Jenkins / JENKINS-35429 Add ability to "Publish to Confluence" more than once in a post-build step. Change By: J M Summary: Add ability to "Publish to Confluence" more than one once in a post-build step. 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] [createjobadvanced-plugin] (JENKINS-35404) unable to create a new job in 2.8
Title: Message Title Mahesh Janardhanan commented on JENKINS-35404 Re: unable to create a new job in 2.8 Please close this issue. It seems like not updating the plugins was the cause 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.
