-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
throttle-concurrents 1.9.0
Jenkins ver. 2.7.1
Number of Executors: 2
If two jobs are configured as shown below, both jobs are started and executed at the same time. What i expected is that one of them starts and the second one is in the build queue.
The same behavior occurs, if they are triggered by a post-commit hook.
The real use case is triggered by a post-commit hook, the example depicted below is only to reproduce this behavior.
Cofiguration of job A:
Throttle Concurrent Builds
- Throttle this project as part of one or more categories
- Maximum Total Concurrent Builds: 1
- Maximum Concurrent Builds Per Node: 1
- Multi-Project Throttle Category: Catergory_1
Build periodically
Schedule 30 11 * * *
Configuration of job B:
Throttle Concurrent Builds
- Throttle this project as part of one or more categories
- Maximum Total Concurrent Builds: 1
- Maximum Concurrent Builds Per Node: 1
- Multi-Project Throttle Category: Catergory_1
Build periodically
Schedule 30 11 * * *