[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-28637) Unable to select stored credentials from the credential plug-in
Title: Message Title Ken Garland created an issue Jenkins / JENKINS-28637 Unable to select stored credentials from the credential plug-in Issue Type: Bug Assignee: Maurice W. Components: parameterized-remote-trigger-plugin Created: 29/May/15 1:48 AM Labels: plugin Priority: Major Reporter: Ken Garland Jenkins 1.615 Parameterized Remote Trigger - 2.26 Credentials - 1.22 From the Jenkins Configure System page under Parameterized Remote Trigger Configuration when I add a remote host and choose Use the Credentials Plugin under Authentication none of my stored credentials appear in the dropdown. The list is empty. If I click the button to Add a credential the list still remains empty. I have tried from Safari and Chrome.
[JIRA] [core] (JENKINS-22275) Save of job configuration doesn't work after removing a parameter under 'This build is parameterized'
Ken Garland edited a comment on JENKINS-22275 Save of job configuration doesn't work after removing a parameter under 'This build is parameterized' Typo... Jenkins ver. 1.596 I can get it to work in Safari but Chrome (even Chrome Canary) doesn't work. 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] [core] (JENKINS-22275) Save of job configuration doesn't work after removing a parameter under 'This build is parameterized'
Ken Garland edited a comment on JENKINS-22275 Save of job configuration doesn't work after removing a parameter under 'This build is parameterized' Typo... Jenkins ver. 1.596 As other previously stated, I can get it to work in Safari but Chrome (even Chrome Canary) doesn't work. 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] [core] (JENKINS-22275) Save of job configuration doesn't work after removing a parameter under 'This build is parameterized'
Ken Garland commented on JENKINS-22275 Save of job configuration doesn't work after removing a parameter under 'This build is parameterized' Typo... Jenkins ver. 1.596 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] [core] (JENKINS-22275) Save of job configuration doesn't work after removing a parameter under 'This build is parameterized'
Ken Garland reopened JENKINS-22275 Save of job configuration doesn't work after removing a parameter under 'This build is parameterized' Looks like this issue is back with 1.569 Change By: Ken Garland (05/Jan/15 8:12 PM) Resolution: Duplicate Status: Resolved Reopened 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] [cli] (JENKINS-23755) Exception
Ken Garland created JENKINS-23755 Exception Issue Type: Bug Assignee: Unassigned Components: cli Created: 10/Jul/14 9:49 PM Description: When attempting to create a job with jenkins-cli using a malformed XML file the exception is "java.io.IOException: Unable to read" which always places the uploaded file name at the jenkins_home location even when it originated elsewhere. Example: java -jar jenkins-cli.jar -s http://127.0.0.1:8080/ create-job Test33 < /tmp/Test34_config.xml java.io.IOException: Unable to read /var/lib/jenkins/jobs/Test33/config.xml Also, this is misleading as the file was read, it was just not properly formated and thus should have an error of "Malformed XML document /tmp/Test34_xonfig.xml" or something similar. Exception output https://gist.github.com/anonymous/a38eeab53a9bf35695dc Environment: Jenkins 1.571, Amazon AMI 2014.03, java version "1.7.0_55" Project: Jenkins Priority: Trivial Reporter: Ken Garland 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] [email-ext] (JENKINS-23715) Multiple recipients list
Ken Garland closed JENKINS-23715 as Not A Defect Multiple recipients list Change By: Ken Garland (08/Jul/14 6:21 PM) Status: Resolved Closed 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] [email-ext] (JENKINS-23715) Multiple recipients list
Ken Garland resolved JENKINS-23715 as Not A Defect Multiple recipients list Change By: Ken Garland (08/Jul/14 6:20 PM) Status: Open Resolved Resolution: Not A Defect 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] [email-ext] (JENKINS-23715) Multiple recipients list
Ken Garland edited a comment on JENKINS-23715 Multiple recipients list How do you make new lists appear in the dropdown for Send To? EDIT: Nevermind, I see the 2nd Advanced button now! 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] [email-ext] (JENKINS-23715) Multiple recipients list
Ken Garland edited a comment on JENKINS-23715 Multiple recipients list How do you make new lists appear in the dropdown for Send To? Nevermind, I see the 2nd Advanced button now! 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] [email-ext] (JENKINS-23715) Multiple recipients list
Ken Garland commented on JENKINS-23715 Multiple recipients list How do you make new lists appear in the dropdown for Send To? 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] [email-ext] (JENKINS-23715) Multiple recipients list
Ken Garland created JENKINS-23715 Multiple recipients list Issue Type: Improvement Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 08/Jul/14 5:48 PM Description: I'd like to have multiple recipients lists. For example one would contain managers, another would have project leads and so on. This way Each trigger could contain more specific notification groups. Not everyone wants to be notified of the same things. Ultimately it would be great to be able to name these lists when creating them as well. Due Date: 18/Jul/14 12:00 AM Environment: Amazon AMI 2014.3, Jenkins 1.571 Fix Versions: current Project: Jenkins Labels: email-ext Priority: Trivial Reporter: Ken Garland 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] [ircbot] (JENKINS-18300) Include job status in message.
Ken Garland closed JENKINS-18300 as Not A Defect Include job status in message. Change By: Ken Garland (11/Jun/13 7:30 PM) Status: Open Closed Resolution: Not A Defect 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/groups/opt_out.
[JIRA] [ircbot] (JENKINS-18300) Include job status in message.
Ken Garland created JENKINS-18300 Include job status in message. Issue Type: Improvement Assignee: kutzi Components: ircbot Created: 11/Jun/13 7:24 PM Description: Need to be able to show job success or failure after completion. Project: Jenkins Priority: Major Reporter: Ken Garland 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/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Ken Garland assigned JENKINS-17684 to Account App Run by Kohsuke Dashboard web pages don't render correctly in Chrome because of bad cache/session 15:51:06 <+rpetti> IMO, just assign it to kohsuke Change By: Ken Garland (15/May/13 7:53 PM) Assignee: Account App Run by Kohsuke 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/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Ken Garland updated JENKINS-17684 Dashboard web pages don't render correctly in Chrome because of bad cache/session Change By: Ken Garland (13/May/13 8:37 PM) Attachment: css_issue.jpg 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/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Ken Garland updated JENKINS-17684 Dashboard web pages don't render correctly in Chrome because of bad cache/session Change By: Ken Garland (13/May/13 8:35 PM) Attachment: css_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/groups/opt_out.
[JIRA] (JENKINS-15925) Changed delimiter of securityGroups from space to semi-colon.
Ken Garland commented on JENKINS-15925 Changed delimiter of securityGroups from space to semi-colon. Pull request has been made with modified code. https://github.com/jenkinsci/ec2-plugin/pull/28 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
[JIRA] (JENKINS-15925) Changed delimiter of securityGroups from space to semi-colon.
Ken Garland started work on JENKINS-15925 Changed delimiter of securityGroups from space to semi-colon. Change By: Ken Garland (26/Nov/12 9:16 PM) Status: Open In Progress 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
[JIRA] (JENKINS-15925) Changed delimiter of securityGroups from space to semi-colon.
Ken Garland updated JENKINS-15925 Changed delimiter of securityGroups from space to semi-colon. Change By: Ken Garland (26/Nov/12 7:49 PM) Summary: EC2 Security group with spaces in name Changed delimiter of securityGroups from space to semi-colon . Assignee: Francis Upton Ken Garland 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
[JIRA] (JENKINS-15925) EC2 Security group with spaces in name.
Ken Garland created JENKINS-15925 EC2 Security group with spaces in name. Issue Type: Task Affects Versions: current Assignee: Francis Upton Components: ec2 Created: 26/Nov/12 5:22 PM Description: When adding a security group that has a space in the name it is treated as multiple groups. Perhaps the delimiter should be changed to a comma or something else to keep spaces intact. Due Date: 26/Nov/12 12:00 AM Project: Jenkins Priority: Major Reporter: Ken Garland 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
[JIRA] (JENKINS-13831) Need a way to copy empty directories with Publish Over SSH Plugin
Ken Garland commented on JENKINS-13831 Need a way to copy empty directories with Publish Over SSH Plugin then it would be best for the author or someone who is willing to contribue to allow extra params to pass to scp. the -r switch should be sending empty directories. check the source of the plugin to see if this is part of the default parameters, in the worst case you can add it yourself. 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
[JIRA] (JENKINS-13831) Need a way to copy empty directories with Publish Over SSH Plugin
Ken Garland commented on JENKINS-13831 Need a way to copy empty directories with Publish Over SSH Plugin can you use rsync instead? 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
[JIRA] (JENKINS-15140) Make shutdown aware of job downstreams
Ken Garland created JENKINS-15140 Make shutdown aware of job downstreams Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: javanet Created: 12/Sep/12 2:49 PM Description: Creating an auto-shutdown capable of understanding downstream jobs. For example, if a job is running and it is the last item in the queue when the auto-shutdown message appears it will shutdown after that job completes. It would be beneficial if it were a aware of dependencies in the downstream and allow those jobs to finish or at the least save their state and resume after restart. However this may break the builds if updates are being applied. Project: Jenkins Labels: jenkins Priority: Major Reporter: Ken Garland 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
[JIRA] (JENKINS-14555) Error 500 org.apache.commons.jelly.JellyTagException
Ken Garland created JENKINS-14555 Error 500 org.apache.commons.jelly.JellyTagException Issue Type: Bug Assignee: ragesh_nair Components: rebuild Created: 24/Jul/12 3:33 PM Description: Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: file:/root/.jenkins/plugins/rebuild/WEB-INF/classes/com/sonyericsson/rebuild/RebuildAction/index.jelly:54:63: No page found 'ExtendedChoiceParameterValue.jelly' for class com.sonyericsson.rebuild.RebuildAction Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: file:/root/.jenkins/plugins/rebuild/WEB-INF/classes/com/sonyericsson/rebuild/RebuildAction/index.jelly:54:63: No page found 'ExtendedChoiceParameterValue.jelly' for class com.sonyericsson.rebuild.RebuildAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.ja
[JIRA] (JENKINS-13701) Parameters lost on retry
[ https://issues.jenkins-ci.org/browse/JENKINS-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162559#comment-162559 ] Ken Garland commented on JENKINS-13701: --- I've also just tried to setup a build that uses file based parameters with "Set environment variables through a file" and the parameters are not sent to the job at run time. Build > Execute shell > Command echo $temp_name [envfile] temp_name=test [workspace] $ /bin/sh -xe /tmp/hudson2757699259452188104.sh + echo As you can see, echo has nothing afterwards. This works on the first run. > Parameters lost on retry > > > Key: JENKINS-13701 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13701 > Project: Jenkins > Issue Type: Bug > Components: naginator >Affects Versions: current > Environment: Jenkins 1.463, Naginator 1.6.1, Parameterized Trigger > 2.14 >Reporter: Ken Garland >Assignee: Nayan Hajratwala > Labels: naginator, plugin, trigger > > Parameters are not passed onto newly started Naginator jobs. > Started by Naginator > [EnvInject] - Loading node environment variables. > Building in workspace /root/.jenkins/jobs/test/workspace > Checkout:workspace / /root/.jenkins/jobs/test/workspace - > hudson.remoting.LocalChannel@2a2bfd5 > Using strategy: Default > [workspace] $ /bin/sh -xe /tmp/hudson3453253707221002170.sh > + python test.py --hostname > There should be a value after "--hostname" as it is in the original build > before failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13701) Parameters lost on retry
[ https://issues.jenkins-ci.org/browse/JENKINS-13701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162559#comment-162559 ] Ken Garland edited comment on JENKINS-13701 at 5/8/12 6:22 PM: --- I've also just tried to setup a build that uses file based parameters with "Set environment variables through a file" and the parameters are not sent to the job at run time. Build > Execute shell > Command echo $temp_name [envfile] temp_name=test [workspace] $ /bin/sh -xe /tmp/hudson2757699259452188104.sh + echo As you can see, echo has nothing afterwards. was (Author: outspoken): I've also just tried to setup a build that uses file based parameters with "Set environment variables through a file" and the parameters are not sent to the job at run time. Build > Execute shell > Command echo $temp_name [envfile] temp_name=test [workspace] $ /bin/sh -xe /tmp/hudson2757699259452188104.sh + echo As you can see, echo has nothing afterwards. This works on the first run. > Parameters lost on retry > > > Key: JENKINS-13701 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13701 > Project: Jenkins > Issue Type: Bug > Components: naginator >Affects Versions: current > Environment: Jenkins 1.463, Naginator 1.6.1, Parameterized Trigger > 2.14 >Reporter: Ken Garland >Assignee: Nayan Hajratwala > Labels: naginator, plugin, trigger > > Parameters are not passed onto newly started Naginator jobs. > Started by Naginator > [EnvInject] - Loading node environment variables. > Building in workspace /root/.jenkins/jobs/test/workspace > Checkout:workspace / /root/.jenkins/jobs/test/workspace - > hudson.remoting.LocalChannel@2a2bfd5 > Using strategy: Default > [workspace] $ /bin/sh -xe /tmp/hudson3453253707221002170.sh > + python test.py --hostname > There should be a value after "--hostname" as it is in the original build > before failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13701) Parameters lost on retry
Ken Garland created JENKINS-13701: - Summary: Parameters lost on retry Key: JENKINS-13701 URL: https://issues.jenkins-ci.org/browse/JENKINS-13701 Project: Jenkins Issue Type: Bug Components: naginator Affects Versions: current Environment: Jenkins 1.463, Naginator 1.6.1, Parameterized Trigger 2.14 Reporter: Ken Garland Assignee: Nayan Hajratwala Parameters are not passed onto newly started Naginator jobs. Started by Naginator [EnvInject] - Loading node environment variables. Building in workspace /root/.jenkins/jobs/test/workspace Checkout:workspace / /root/.jenkins/jobs/test/workspace - hudson.remoting.LocalChannel@2a2bfd5 Using strategy: Default [workspace] $ /bin/sh -xe /tmp/hudson3453253707221002170.sh + python test.py --hostname There should be a value after "--hostname" as it is in the original build before failure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9879) Naginator Plugin: Add retry and retry-delay parameter
[ https://issues.jenkins-ci.org/browse/JENKINS-9879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162417#comment-162417 ] Ken Garland commented on JENKINS-9879: -- I would love to see an option that says "disable adding time to retry period" so that it only waits X minutes each time after failure. > Naginator Plugin: Add retry and retry-delay parameter > - > > Key: JENKINS-9879 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9879 > Project: Jenkins > Issue Type: New Feature > Components: naginator >Affects Versions: current >Reporter: Bruno Marti >Assignee: nhajratw > > the delay between retries and maximum number of re-tries should by available > as plugin parameter (see: schedule-failed-builds plugin) > why not combine it from schedule-failed-builds plugin? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
