![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Components:
|
concurrent-build, github |
|
Created:
|
20/Jun/14 4:40 PM
|
|
Description:
|
Simple Jenkins configuration, 1 master, no slaves. My project has 1 build trigger: "Build when a change is pushed to GitHub". I also have "Execute concurrent builds if necessary" enabled.
If a new trigger occurrs as a result from a push to GitHub, the concurrent workspace is not created. Jenkins waits until the current request is complete, then starts. If there were 2 queued up, it only executes the 'latest' one.
If I use a custom workspace, the concurrent builds DO work. Unfortunately, I cannot use this option as each of the workspaces need to be unique.
|
|
Environment:
|
Ubuntu 12.04.4
Jenkins Version 1.554.1
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Chris Funston
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
