[
https://issues.jenkins-ci.org/browse/JENKINS-13619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163614#comment-163614
]
Louis Poudrier-Racette commented on JENKINS-13619:
--------------------------------------------------
We are using Jenkins to test code running on embedded devices.
We have multiple nodes in our setup, each one has only *one (1)* embedded
device attached to it.
We have two types of Jobs:
# Some of our jobs require an embedded devices, they run tests on them. This
type of jobs are matrix configurations because there are many versions of the
embedded devices to test.
# Some of our jobs *do not* require the embedded devices, they only compile
code, they don't run any tests.
When tests are running on an embedded device (Job type 1), the node's CPU is
mostly free. However, we cannot take advantage of this free CPU to run type 2
jobs because we can only have one executor per node.
We cannot have more then one executor per node because we don't have the
_"ability to throttle number of concurrent builds of matrix configurations per
node"_ for type 1 jobs.
We need the _"ability to throttle number of concurrent builds of matrix
configurations per node"_ so that different configurations of a type 1 Job are
not concurrently run on one node as each node only has one embedded device.
This would improvement would greatly increase the effectiveness of our
continuous integration setup.
> Add ability to throttle number of concurrent builds of matrix configurations
> per node
> -------------------------------------------------------------------------------------
>
> Key: JENKINS-13619
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13619
> Project: Jenkins
> Issue Type: New Feature
> Components: throttle-concurrents
> Reporter: Austen Dicken
> Assignee: abayer
> Priority: Minor
>
> It would be extremely useful to be able to throttle the number of concurrent
> builds of matrix configurations that can take place on a given node. The
> reason for this is when you have a matrix project in which all subprojects
> share the same parent workspace data. It is possible then to run concurrent
> builds across separate nodes, but not on the same node.
> The specific use case I am running into is for building Android. I have a
> matrix project that defines configurations for each device I wish to build.
> Every sub-project shares the same android source tree to build off of, so
> concurrent builds are not possible on the same node as they would clobber
> each other, but concurrent builds on separate nodes would be fine.
--
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
