[ 
https://issues.jenkins-ci.org/browse/JENKINS-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

BalagiriPrasad S updated JENKINS-13705:
---------------------------------------

    Description: 
The reason for making "Invoke Maven Target" build step not parallel, may be 
because two concurrent maven calls can corrupt the repository. But when the two 
builds are happening on different nodes then jenkins should run them in 
parallel. I am using nodelableparam to select different nodes, throttle 
Concurrent Builds configured to have 'Maximum Concurrent Builds Per Node' as 1.

Attached the project files. In sleep.xml, update <host:port> with proper values

  was:
The reason for making "Invoke Maven Target" build step is not parallel may be 
because two concurrent maven calls can corrupt the repository. But when the two 
builds are happening on different nodes then jenkins should allow them. I am 
using nodelableparam to select different nodes, throttle Concurrent Builds 
configured to have 'Maximum Concurrent Builds Per Node' as 1.

Attached the project files. In sleep.xml, update <host:port> with proper values

    
> Builds are sequential when there is a "Invoke Maven Target" build step, even 
> though the project is configured for concurrent execution
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13705
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13705
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: current
>         Environment: Master : Windows, Nodes : Linux
>            Reporter: BalagiriPrasad S
>            Priority: Blocker
>              Labels: concurrent-build
>         Attachments: config.xml, sleep.xml
>
>
> The reason for making "Invoke Maven Target" build step not parallel, may be 
> because two concurrent maven calls can corrupt the repository. But when the 
> two builds are happening on different nodes then jenkins should run them in 
> parallel. I am using nodelableparam to select different nodes, throttle 
> Concurrent Builds configured to have 'Maximum Concurrent Builds Per Node' as 
> 1.
> Attached the project files. In sleep.xml, update <host:port> with proper 
> values

--
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

        

Reply via email to