[JIRA] (JENKINS-50879) The secretVolume is not mounted to "jnlp" container in the multicontainer pod
Title: Message Title Jacobo Jimenez edited a comment on JENKINS-50879 Re: The secretVolume is not mounted to "jnlp" container in the multicontainer pod Same proble problem here with "emptyDirVolume". Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-50879) The secretVolume is not mounted to "jnlp" container in the multicontainer pod
Title: Message Title Jacobo Jimenez commented on JENKINS-50879 Re: The secretVolume is not mounted to "jnlp" container in the multicontainer pod Same proble here with "emptyDirVolume". Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-19513) Jenkins should reconnect to a node after ChannelClosedException
Title: Message Title Jacobo Jimenez commented on JENKINS-19513 Re: Jenkins should reconnect to a node after ChannelClosedException Same problem here using real SUSE Linux Enterprise Server 11.3 (x86_64) slaves. 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] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Jack Wang commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect Any update for this issue? I am having the same problem but my case is a little more complicated as I have jobs using github and bitbucket respectively. commit url for github is correct but not for bitbucket due to the extra "s" in "commits" in url. 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] (JENKINS-13872) Counter Parameter Factory
[ https://issues.jenkins-ci.org/browse/JENKINS-13872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacobo Jimenez updated JENKINS-13872: - Due Date: (was: 18/May/12) Counter Parameter Factory - Key: JENKINS-13872 URL: https://issues.jenkins-ci.org/browse/JENKINS-13872 Project: Jenkins Issue Type: Bug Components: parameterized-trigger Affects Versions: current Environment: GNU/Linux x86_64 2.6.16 Tomcat Reporter: Jacobo Jimenez Assignee: huybrechts Labels: builds, exception, parallel, parameterized, trigger Defining a Trigger/call builds on other projects build step with Counter Parameter Factory as follow: FROM = 1 TO = $VARIABLE STEP = 1 It should do nothing, I mean, do not build step, if $VARIABLE is zero but it is failing with following exception: FATAL: Counting with step size 0 will not terminate! java.lang.RuntimeException: Counting with step size 0 will not terminate! -- 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-13871) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job
[ https://issues.jenkins-ci.org/browse/JENKINS-13871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacobo Jimenez updated JENKINS-13871: - Due Date: (was: 18/May/12) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job Key: JENKINS-13871 URL: https://issues.jenkins-ci.org/browse/JENKINS-13871 Project: Jenkins Issue Type: Bug Components: conditional-buildstep, parameterized-trigger, run-condition Affects Versions: current Environment: GNU/Linux x86_64 2.6.16.60-0.69.1-smp Tomcat Reporter: Jacobo Jimenez Assignee: domi Labels: diamond, exception, interlock, parallel, parameter, stuck Attachments: QueueInterlockTest_main#config.xml, QueueInterlockTest_subtask#config.xml Job A triggers a variable number of job B depending on a environment variable. It can be zero but since Counter Parameter Factory doesnt allow zero repetitions (Java exception) I had to include this step as a conditional build step. Job A must wait until the end of all B jobs so option Block until the triggered projects finish their builds is selected (because it is really a diamond execution). This jobs configuration works fine but if you launch another A (in parallel) when it finish its first step and reach conditional step, it get stuck waiting until the end of all the jobs from first execution, once first A execution finished second execution continue executing its B jobs. This is a kind of interlocking process between executions. -- 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-13871) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job
[ https://issues.jenkins-ci.org/browse/JENKINS-13871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacobo Jimenez updated JENKINS-13871: - Attachment: QueueInterlockTest_main#config.xml QueueInterlockTest_subtask#config.xml I have attached an example project with this problem, executable job is QueueInterlockTest_main. To test this problem you must launch two executions of this job (in parallel), you will notice how second execution do not trigger QueueInterlockTest_subtask until first execution is finished. Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job Key: JENKINS-13871 URL: https://issues.jenkins-ci.org/browse/JENKINS-13871 Project: Jenkins Issue Type: Bug Components: conditional-buildstep, parameterized-trigger, run-condition Affects Versions: current Environment: GNU/Linux x86_64 2.6.16.60-0.69.1-smp Tomcat Reporter: Jacobo Jimenez Assignee: domi Labels: diamond, exception, interlock, parallel, parameter, stuck Attachments: QueueInterlockTest_main#config.xml, QueueInterlockTest_subtask#config.xml Job A triggers a variable number of job B depending on a environment variable. It can be zero but since Counter Parameter Factory doesnt allow zero repetitions (Java exception) I had to include this step as a conditional build step. Job A must wait until the end of all B jobs so option Block until the triggered projects finish their builds is selected (because it is really a diamond execution). This jobs configuration works fine but if you launch another A (in parallel) when it finish its first step and reach conditional step, it get stuck waiting until the end of all the jobs from first execution, once first A execution finished second execution continue executing its B jobs. This is a kind of interlocking process between executions. -- 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-13871) Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job
Jacobo Jimenez created JENKINS-13871: Summary: Using Conditional build step and Parameterized build step in same step is preventing parallel executions of same job Key: JENKINS-13871 URL: https://issues.jenkins-ci.org/browse/JENKINS-13871 Project: Jenkins Issue Type: Bug Components: conditional-buildstep, parameterized-trigger, run-condition Affects Versions: current Environment: GNU/Linux x86_64 2.6.16.60-0.69.1-smp Tomcat Reporter: Jacobo Jimenez Assignee: domi Job A triggers a variable number of job B depending on a environment variable. It can be zero but since Counter Parameter Factory doesnt allow zero repetitions (Java exception) I had to include this step as a conditional build step. Job A must wait until the end of all B jobs so option Block until the triggered projects finish their builds is selected (because it is really a diamond execution). This jobs configuration works fine but if you launch another A (in parallel) when it finish its first step and reach conditional step, it get stuck waiting until the end of all the jobs from first execution, once first A execution finished second execution continue executing its B jobs. This is a kind of interlocking process between executions. -- 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-13872) Counter Parameter Factory
Jacobo Jimenez created JENKINS-13872: Summary: Counter Parameter Factory Key: JENKINS-13872 URL: https://issues.jenkins-ci.org/browse/JENKINS-13872 Project: Jenkins Issue Type: Bug Components: parameterized-trigger Affects Versions: current Environment: GNU/Linux x86_64 2.6.16 Tomcat Reporter: Jacobo Jimenez Assignee: huybrechts Defining a Trigger/call builds on other projects build step with Counter Parameter Factory as follow: FROM = 1 TO = $VARIABLE STEP = 1 It should do nothing, I mean, do not build step, if $VARIABLE is zero but it is failing with following exception: FATAL: Counting with step size 0 will not terminate! java.lang.RuntimeException: Counting with step size 0 will not terminate! -- 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
