-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
This is really a "locks and latches" kind of request, but since Jenkins is positioning this plugin to replace that plugin...
My use case is not exactly throttling the number of builds, but just that lots of teams have jobs for the trunk plus a few branches, and those 2 or 3 jobs cannot run concurrently due to (typically) database contention issues.
I want to use this plugin to address this use case, but have 2 requirements that block me from using it
- Do not allow all Jenkins users to "Manage Jenkins" (we have hundreds of users)
- Whenever possible, reduce the amount of time/communication/coordination it takes for admins to "Manage Jenkins"
So what I really want is for the owner of those jobs to be able to define their own category without having to call me to set it up for them. And they probably don't care about the "Maximum ..." settings, they just want any job that uses that category to not run at the same time as other jobs with that category. It is okay if they have to just type the category into a text field. It shouldn't be a drop-down or checkbox, because that would be confusing anyways. If it needed to be multiple categories, it could be comma-separated.
[JENKINS-14729] Allow project to configure categories on an ad-hoc basis
Jacob Robertson
created issue -
Jacob Robertson
made changes -
| Component/s | Original: matrix [ 15501 ] | |
| Description |
Original:
I've written an integration test for different OS's and different databases. Now I've created a matrix job with two axis (slaves & "database"). The slaves have multiple executors, being able to run the integration tests in parallel. But for each database there exists only one account, therefor when running the build, axis combinations using the same database must not be running in parallel. How about a (throttle-) flag in the axis definition to mark this axis not to be used in parallel? As a workaround I'm using the "Run each configuration sequentially", but it's unnecessary slow's down the build. |
New:
This is really a "locks and latches" kind of request, but since Jenkins is positioning this plugin to replace that plugin... My use case is not exactly throttling the number of builds, but just that lots of teams have jobs for the trunk plus a few branches, and those 2 or 3 jobs cannot run concurrently due to (typically) database contention issues. I want to use this plugin to address this use case, but have 2 requirements that block me from using it * Do not allow all Jenkins users to "Manage Jenkins" (we have hundreds of users) * Whenever possible, reduce the amount of time/communication/coordination it takes for admins to "Manage Jenkins" So what I really want is for the owner of those jobs to be able to define their own category without having to call me to set it up for them. And they probably don't care about the "Maximum ..." settings, they just want any job that uses that category to not run at the same time as other jobs with that category. It is okay if they have to just type the category into a text field. It shouldn't be a drop-down or checkbox, because that would be confusing anyways. If it needed to be multiple categories, it could be comma-separated. |
| Environment | Original: Linux x64 |
| Workflow | Original: JNJira [ 145425 ] | New: JNJira + In-Review [ 176344 ] |
| Assignee | Original: Andrew Bayer [ abayer ] |