[JIRA] (JENKINS-13236) start identical job with different parameters in parallel execution
[ https://issues.jenkins-ci.org/browse/JENKINS-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161756#comment-161756 ] ttgtg ttgtg commented on JENKINS-13236: --- Thanks, I missed that, this option is not available in the Matrix job, that is where I looked for it. start identical job with different parameters in parallel execution --- Key: JENKINS-13236 URL: https://issues.jenkins-ci.org/browse/JENKINS-13236 Project: Jenkins Issue Type: New Feature Components: core Reporter: ttgtg ttgtg Labels: build, parallel Have the option for a job to run several instances in parallel. The use case: We have a job that gets the branch name as an input and then it builds the project and run the test. If two or more developers want to build different branches the first one blocks the others. The build and test take a lot of time but with many nodes we can do several in parallel. There may be a problem with this option if the jobs use the same workspace, but on our setup the workspace is set by time and date with the branch name to prevent this problem. As this option has potential for destruction it should be under the advance options. -- 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-13236) start identical job with different parameters in parallel execution
[ https://issues.jenkins-ci.org/browse/JENKINS-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ttgtg ttgtg closed JENKINS-13236. - start identical job with different parameters in parallel execution --- Key: JENKINS-13236 URL: https://issues.jenkins-ci.org/browse/JENKINS-13236 Project: Jenkins Issue Type: New Feature Components: core Reporter: ttgtg ttgtg Labels: build, parallel Have the option for a job to run several instances in parallel. The use case: We have a job that gets the branch name as an input and then it builds the project and run the test. If two or more developers want to build different branches the first one blocks the others. The build and test take a lot of time but with many nodes we can do several in parallel. There may be a problem with this option if the jobs use the same workspace, but on our setup the workspace is set by time and date with the branch name to prevent this problem. As this option has potential for destruction it should be under the advance options. -- 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-13258) Set the default params in parametrized build as env variables in the SCM poll
[ https://issues.jenkins-ci.org/browse/JENKINS-13258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ttgtg ttgtg updated JENKINS-13258: -- Component/s: scm-sync-configuration Set the default params in parametrized build as env variables in the SCM poll - Key: JENKINS-13258 URL: https://issues.jenkins-ci.org/browse/JENKINS-13258 Project: Jenkins Issue Type: Improvement Components: accurev, core, scm-sync-configuration Reporter: ttgtg ttgtg Assignee: Scott Tatum use case: Be able to set the stream name (in accurev) as the parametrized input of the job and have a default value for that param used to poll SCM trigger. In this case it uses the default value to poll the accurev and uses the input when the job starts manually or by another job. -- 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-13258) Set the default params in parametrized build as env variables in the SCM poll
ttgtg ttgtg created JENKINS-13258: - Summary: Set the default params in parametrized build as env variables in the SCM poll Key: JENKINS-13258 URL: https://issues.jenkins-ci.org/browse/JENKINS-13258 Project: Jenkins Issue Type: Improvement Components: accurev, core Reporter: ttgtg ttgtg Assignee: Scott Tatum use case: Be able to set the stream name (in accurev) as the parametrized input of the job and have a default value for that param used to poll SCM trigger. In this case it uses the default value to poll the accurev and uses the input when the job starts manually or by another job. -- 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-13236) start identical job with different parameters in parallel execution
ttgtg ttgtg created JENKINS-13236: - Summary: start identical job with different parameters in parallel execution Key: JENKINS-13236 URL: https://issues.jenkins-ci.org/browse/JENKINS-13236 Project: Jenkins Issue Type: New Feature Components: build-pipeline Reporter: ttgtg ttgtg Have the option for a job to run several instances in parallel. The use case: We have a job that gets the branch name as an input and then it builds the project and run the test. If two or more developers want to build different branches the first one blocks the others. The build and test take a lot of time but with many nodes we can do several in parallel. There may be a problem with this option if the jobs use the same workspace, but on our setup the workspace is set by time and date with the branch name to prevent this problem. As this option has potential for destruction it should be under the advance options. -- 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
