![]() |
|
|
|
|
Change By:
|
Jacob Robertson
(08/Aug/12 1:06 PM)
|
|
Environment:
|
Linux x64
|
|
Description:
|
I've written an integration test for different OS's and different databases. Now I've created
This is really
a
matrix job with two axis (slaves &
"
database
locks and latches
"
). The slaves have multiple executors
kind of request
,
being able
but since Jenkins is positioning this plugin
to
run the integration tests in parallel
replace that plugin
.
..
But for each database there exists only one account, therefor when running
My use case is not exactly throttling
the
build
number of builds
,
axis combinations using
but just that lots of teams have jobs for
the
same
trunk plus a few branches, and those 2 or 3 jobs cannot run concurrently due to (typically)
database
must not be running in parallel
contention issues
.
How about a
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"
(
throttle-
we have hundreds of users
)
flag in
* Whenever possible, reduce
the
axis definition
amount of time/communication/coordination it takes for admins
to
mark this axis not
"Manage Jenkins"
So what I really want is for the owner of those jobs
to be
used in parallel? As a workaround I
able to define their own category without having to call me to set it up for them. And they probably don
'
m using
t care about
the "
Run each configuration sequentially
Maximum ...
"
settings
,
but it
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
'
s unnecessary slow's
t be a drop-
down
the build
or checkbox, because that would be confusing anyways
.
If it needed to be multiple categories, it could be comma-separated.
|
|
Component/s:
|
matrix
|
|
|
|
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
|
