[JIRA] [core] (JENKINS-31728) JDK Home not set when only one JDK is configured in Jenkins
Title: Message Title Jeff Storey commented on JENKINS-31728 Re: JDK Home not set when only one JDK is configured in Jenkins was in 1.5x (don't have the specific version, since I recently upgraded to try a fix). It looks like this is fixed in 1.639. 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-31728) JDK Home not set when only one JDK is configured in Jenkins
Title: Message Title Jeff Storey created an issue Jenkins / JENKINS-31728 JDK Home not set when only one JDK is configured in Jenkins Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Nov/15 3:31 PM Priority: Minor Reporter: Jeff Storey When only one JDK is configured in Jenkins, the drop down for selecting a JDK does not appear. This kind of makes sense because there is no choice to be made, thought it may be helpful see which JDK you are using. The problem happens when there is a different JRE/JDK used to launch Jenkins than single one configured for Jenkins. A job will pick up the JAVA_HOME from the JRE that launched Jenkins, not the one that is actually configured in Jenkins. If you have 2 JDKs configured in Jenkins and one of them is selected, the job gets the JAVA_HOME from the selected JDK as expected. Add Comment
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-25494) Properties File is being looked for on the MASTER not the slaves
Title: Message Title Jeff Storey commented on JENKINS-25494 Re: Properties File is being looked for on the MASTER not the slaves maurice chen are you sure this is working as expected? I am running into the same problem and the file is on the slave but it cannot be found. 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] [parameterized-remote-trigger-plugin] (JENKINS-25494) Properties File is being looked for on the MASTER not the slaves
Title: Message Title Jeff Storey commented on JENKINS-25494 Re: Properties File is being looked for on the MASTER not the slaves And in fact, it doesn't look like any of this code is being executed on the remote slave. No use of the launcher or the channels at all... 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] [parameterized-remote-trigger-plugin] (JENKINS-25494) Properties File is being looked for on the MASTER not the slaves
Title: Message Title Jeff Storey commented on JENKINS-25494 Re: Properties File is being looked for on the MASTER not the slaves Sorry, wrong Maurice W. on the notification there. 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] [parameterized-remote-trigger-plugin] (JENKINS-30962) Builds with password parameters cause remote trigger to show failure
Title: Message Title Jeff Storey created an issue Jenkins / JENKINS-30962 Builds with password parameters cause remote trigger to show failure Issue Type: Bug Assignee: Jeff Storey Components: parameterized-remote-trigger-plugin Created: 15/Oct/15 1:25 AM Priority: Minor Reporter: Jeff Storey Execute a remote parameterized build with a password parameter, and the following stack trace happens on the local Jenkins even though the remote build succeeds. This happens because the Jenkins API strips out the value of password parameters. ERROR: Build step failed with exception net.sf.json.JSONException: JSONObject["value"] not found. at net.sf.json.JSONObject.getString(JSONObject.java:2040) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.compareParameters(RemoteBuildConfiguration.java:695) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:567) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-30962) Builds with password parameters cause remote trigger to show failure
Title: Message Title Jeff Storey started work on JENKINS-30962 Change By: Jeff Storey 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] [parameterized-remote-trigger-plugin] (JENKINS-30962) Builds with password parameters cause remote trigger to show failure
Title: Message Title Jeff Storey commented on JENKINS-30962 Re: Builds with password parameters cause remote trigger to show failure Pull request submitted https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/15 and ready for review 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-26998) Manual downstream jobs do not work when job is in folder
Jeff Storey created JENKINS-26998 Manual downstream jobs do not work when job is in folder Issue Type: Bug Assignee: Jeff Storey Components: build-pipeline-plugin Created: 17/Feb/15 8:38 PM Description: When build pipeline jobs are in a folder (Cloudless folder plugin) and there is a manual step between jobs, running the second (or any job past the first) does not work. BuildPipelineView.retrieveUpstreamProjectTriggerConfig does a check for downstreamProjectsNames.contains(project.getFullName()) And downstreamProjectNames contains the project short names, not the names with folders Project: Jenkins Priority: Minor Reporter: Jeff Storey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26998) Manual downstream jobs do not work when job is in folder
Jeff Storey resolved JENKINS-26998 as Not A Defect Manual downstream jobs do not work when job is in folder I was specifying the short name of the project in the downstream job. Specifying the full version seems to work. Change By: Jeff Storey (17/Feb/15 8:46 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-25710) Join plugin does not work with folders
Jeff Storey created JENKINS-25710 Join plugin does not work with folders Issue Type: Bug Assignee: mdonohue Components: join-plugin Created: 20/Nov/14 2:08 PM Description: The join plugin doesn't properly setup the aggregator job when jobs are in folders. To reproduce, create a folder using the Cloudbees folder plugin. Put 4 jobs in there - a parent job, 2 child jobs of the parent and then a final job for the join trigger. Both the child jobs and the final job will be listed as children of the parent job rather than the final job being the join trigger. Project: Jenkins Priority: Major Reporter: Jeff Storey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-25710) Join plugin does not work with folders
Jeff Storey commented on JENKINS-25710 Join plugin does not work with folders I created a pull request to fix this https://github.com/jenkinsci/join-plugin/pull/8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25460) Clicking on the console icon to open the console dialog a screen with a Server not found error is displayed
Jeff Storey commented on JENKINS-25460 Clicking on the console icon to open the console dialog a screen with a Server not found error is displayed This should be fixed as part of my pull request https://github.com/jenkinsci/build-pipeline-plugin/pull/56 because of the changes to use app.rootUrl to prefix the link to the console. I took out the leading "/" and updated all calls to fillDialog. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25430) Clicking on console icon doesn't work
Jeff Storey commented on JENKINS-25430 Clicking on console icon doesnt work I added a comment in JENKINS-25460 https://issues.jenkins-ci.org/browse/JENKINS-25460?focusedCommentId=215751page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-215751 on the resolution of this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24315) Can't run a pipeline when first job has parameters
Jeff Storey commented on JENKINS-24315 Cant run a pipeline when first job has parameters This looks duplicated by JENKINS-25427. I submitted a fix that is pending - https://issues.jenkins-ci.org/browse/JENKINS-25427?focusedCommentId=215682page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-215682. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20873) Run button does not work with Parametrized builds
Jeff Storey commented on JENKINS-20873 Run button does not work with Parametrized builds This looks like a duplicate of JENKINS-25427. I recently submitted a fix for this https://github.com/jenkinsci/build-pipeline-plugin/pull/56. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Jeff Storey commented on JENKINS-19121 Build pipeline plugin no longer prompts for parameters of parameterised job This looks like a duplicate of JENKINS-25427. I submitted that is awaiting approval/merge - https://issues.jenkins-ci.org/browse/JENKINS-25427?focusedCommentId=215682page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-215682 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Jeff Storey edited a comment on JENKINS-19121 Build pipeline plugin no longer prompts for parameters of parameterised job This looks like a duplicate of JENKINS-25427. I submitted that is awaiting approval/merge - https://issues.jenkins-ci.org/browse/JENKINS-25427?focusedCommentId=215682page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-215682 I believe the reason the prompt for parameters is no longer happening because the bpp.jelly file only displays the prompt when the BuildPipelineView's isProjectParameterized method is true. The problem is that the method doesn't exist. Adding it fixed the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20841) Links of the pipeline view are not working for project using the Cloudbees folder plug-in
Jeff Storey updated JENKINS-20841 Links of the pipeline view are not working for project using the Cloudbees folder plug-in I created a patch for this issue for v1.4.3. I'm still looking into how to fix this for 1.4.4, but I'm yet sure what to do because JENKINS-25427 seems to have broken the run button for parameterized builds. My github branch for it is here - https://github.com/jeffastorey/build-pipeline-plugin/tree/jenkins_20841_v1.4.3_patch, but I can't create a pull request because of the 1.4.4 breakage mentioned above. Change By: Jeff Storey (08/Nov/14 1:48 AM) Attachment: jenkins_20841_1.4.3.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25427) Build Pipleline Plugin no longer allows starting build with parameters
Jeff Storey commented on JENKINS-25427 Build Pipleline Plugin no longer allows starting build with parameters Added a fix on master https://github.com/jenkinsci/build-pipeline-plugin/pull/56 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20841) Links of the pipeline view are not working for project using the Cloudbees folder plug-in
Jeff Storey commented on JENKINS-20841 Links of the pipeline view are not working for project using the Cloudbees folder plug-in Added a fix on master https://github.com/jenkinsci/build-pipeline-plugin/pull/56 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Jeff Storey commented on JENKINS-25051 ConcurrentModificationException in DSL plugin 1.2.6 Thanks for looking into this so quickly. Agree that it is no longer a blocker. An alternative fix is to just upgrade to the new method. Though quoting it would ensure it works on older versions too. I understand your concerns about not necessarily wanting to change the closure strategy for this as this is probably an edge case. Feel free to close as won't fix since there is a reasonably easy workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Jeff Storey created JENKINS-25051 ConcurrentModificationException in DSL plugin 1.2.6 Issue Type: Bug Assignee: Daniel Spilker Attachments: concurrentmod.log Components: job-dsl-plugin Created: 08/Oct/14 3:23 PM Description: I upgraded the plugin to the newest version 1.2.6 and the jobs would no longer run and threw a ConcurrentModificationException every time I tried to run them. Log is attached. Environment: OS X 10.9.4 Project: Jenkins Priority: Blocker Reporter: Jeff Storey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Jeff Storey
commented on JENKINS-25051
ConcurrentModificationException in DSL plugin 1.2.6
So I had previously added my own configure block to turn this parameter on before it was supported in the DSL with a block that looks like the following. When I replaced that with the new startsWithParameters block it worked. But I wouldn't think that having a configuration block like that should cause a breakage.
jobFactory.view(type: 'BuildPipelineView') {
name("myPipeline")
showPipelineParameters true
showPipelineParametersInHeaders false
showPipelineDefinitionHeader true
selectedJob("ajob")
configure { pipelineNode -
pipelineNode {
startsWithParameters true
}
}
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Jeff Storey
edited a comment on JENKINS-25051
ConcurrentModificationException in DSL plugin 1.2.6
So I had previously added my own configure block to turn this parameter on before it was supported in the DSL with a block that looks like the following. When I replaced that with the new startsWithParameters block it worked.
jobFactory.view(type: 'BuildPipelineView') {
name("myPipeline")
showPipelineParameters true
showPipelineParametersInHeaders false
showPipelineDefinitionHeader true
selectedJob("ajob")
configure { pipelineNode -
pipelineNode {
startsWithParameters true
}
}
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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] (JENKINS-20873) Run button does not work with Parametrized builds
Jeff Storey commented on JENKINS-20873 Run button does not work with Parametrized builds I'm using Jenkins 1.569 and pipeline version 1.4.3 and when I press the run button I get a 404 page. I did verify that "Pipeline starts with parameters" is set to "yes". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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] (JENKINS-20873) Run button does not work with Parametrized builds
Jeff Storey commented on JENKINS-20873 Run button does not work with Parametrized builds Any updates on this one? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
