Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
Can you put your lock step inside a step block? We still use Imperative
Pipeline so I'm less familiar with Declarative Pipeline. But it seems like
inside a step block that NODE_NAME should resolve correctly, because--I
think--the block is running in a node context.
On Monday, February 11, 2019 at 5:33:44 AM UTC-8, Vitaly Karasik wrote:
>
> I started to play with the lockable resources plugin.
> I'd like to prevent parallel execution of my pipeline (multibranch
> pipeline) on the same Jenkins slave, so I tried to use "$NODE_NAME" as
> lockable resource, like this:
>
> pipeline {
> agent { label 'slave-parallel' }
> options {
> lock ("${NODE_NAME}")
>}
>
> stages()
> {
> ..
> }
>
> But unfortunately $NODE_NAME isn't available on this step. Is there simple
> workaround for thaT?
>
> On Thursday, January 31, 2019 at 11:43:30 AM UTC+2, Daniel Butler wrote:
>>
>> You could use the lockable resources plugin (v2.2+):
>>
>> Set up a single resource for each node and give them all a common label
>>
>> Then your Jenkinsfile would be:
>>
>> lock(label: "common-label", variable: "LOCKED_NODE"){
>> node(env.LOCKED_NODE){
>> //build project
>> }
>> }
>>
>> Regards,
>> Daniel.
>>
>> On Thu, Jan 31, 2019 at 7:48 AM Vitaly Karasik wrote:
>>
>>> I'd like to mark *whole* pipeline job as throttling resource; and unlike
>>> freestyle jobs, Throttleling plugin does't know to do that. I.e. I cannot
>>> use "throttle" in pipeline options.
>>>
>>> On Wednesday, January 30, 2019 at 7:47:20 PM UTC+2, Den Slobozhanskyi
>>> wrote:
Just to clarify - does it mean that Throttling plugin throttles not the
job as a whole, but each step in parallel? My assumption was that
throttling is only for the job, and nested threads have nothing to do with
throttle. By your words it looks like setting throttling to "1" for the
job
reduce the possible parallel threads execution to a single thread at a
time
as well, is that true?
If this is not true, you just gather all the jobs under one throttling
category and set the concurrent builds limit to 1.
BR,
Denys
среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik
написал:
>
> I have multibranch job, whole pipeline runs on certain node.
>
> Currently I have a slaves with single executor, so multiple jobs
> cannot run on the same node. I'd like to use parallel steps inside my
> pipeline, so I need to increase number of executors.
>
> What is the best way to prevent concurrent job execution?
>
> Such configuration was trivial with Jenkins freestyle job and
> Throttling plugin - I simple used "Maximum Concurrent Builds Per Node".
> But
> in pipeline it seems that I cannot use "throttle" for whole pipeline, I
> need to use it for each step. Is there more elegant solution?
>
> TIA, Vitaly
>
--
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/d6b76faf-f9e6-4960-8dc5-ab79c6c6ac0f%40googlegroups.com
>>>
>>>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/d54117cb-3251-4cca-9f98-50b8887fc2de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
Can you put your lock step inside a steps block? We still use Imperative
Pipeline so I'm less familiar with Declarative Pipeline. But it seems like
inside a step block that NODE_NAME should resolve correctly, because--I
think--the block is running in a node context.
On Monday, February 11, 2019 at 5:33:44 AM UTC-8, Vitaly Karasik wrote:
>
> I started to play with the lockable resources plugin.
> I'd like to prevent parallel execution of my pipeline (multibranch
> pipeline) on the same Jenkins slave, so I tried to use "$NODE_NAME" as
> lockable resource, like this:
>
> pipeline {
> agent { label 'slave-parallel' }
> options {
> lock ("${NODE_NAME}")
>}
>
> stages()
> {
> ..
> }
>
> But unfortunately $NODE_NAME isn't available on this step. Is there simple
> workaround for thaT?
>
> On Thursday, January 31, 2019 at 11:43:30 AM UTC+2, Daniel Butler wrote:
>>
>> You could use the lockable resources plugin (v2.2+):
>>
>> Set up a single resource for each node and give them all a common label
>>
>> Then your Jenkinsfile would be:
>>
>> lock(label: "common-label", variable: "LOCKED_NODE"){
>> node(env.LOCKED_NODE){
>> //build project
>> }
>> }
>>
>> Regards,
>> Daniel.
>>
>> On Thu, Jan 31, 2019 at 7:48 AM Vitaly Karasik wrote:
>>
>>> I'd like to mark *whole* pipeline job as throttling resource; and unlike
>>> freestyle jobs, Throttleling plugin does't know to do that. I.e. I cannot
>>> use "throttle" in pipeline options.
>>>
>>> On Wednesday, January 30, 2019 at 7:47:20 PM UTC+2, Den Slobozhanskyi
>>> wrote:
Just to clarify - does it mean that Throttling plugin throttles not the
job as a whole, but each step in parallel? My assumption was that
throttling is only for the job, and nested threads have nothing to do with
throttle. By your words it looks like setting throttling to "1" for the
job
reduce the possible parallel threads execution to a single thread at a
time
as well, is that true?
If this is not true, you just gather all the jobs under one throttling
category and set the concurrent builds limit to 1.
BR,
Denys
среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik
написал:
>
> I have multibranch job, whole pipeline runs on certain node.
>
> Currently I have a slaves with single executor, so multiple jobs
> cannot run on the same node. I'd like to use parallel steps inside my
> pipeline, so I need to increase number of executors.
>
> What is the best way to prevent concurrent job execution?
>
> Such configuration was trivial with Jenkins freestyle job and
> Throttling plugin - I simple used "Maximum Concurrent Builds Per Node".
> But
> in pipeline it seems that I cannot use "throttle" for whole pipeline, I
> need to use it for each step. Is there more elegant solution?
>
> TIA, Vitaly
>
--
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/d6b76faf-f9e6-4960-8dc5-ab79c6c6ac0f%40googlegroups.com
>>>
>>>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/7eabfb51-9587-41c8-a40e-7fdbc9f92416%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
I started to play with the lockable resources plugin.
I'd like to prevent parallel execution of my pipeline (multibranch
pipeline) on the same Jenkins slave, so I tried to use "$NODE_NAME" as
lockable resource, like this:
pipeline {
agent { label 'slave-parallel' }
options {
lock ("${NODE_NAME}")
}
stages()
{
..
}
But unfortunately $NODE_NAME isn't available on this step. Is there simple
workaround for thaT?
On Thursday, January 31, 2019 at 11:43:30 AM UTC+2, Daniel Butler wrote:
>
> You could use the lockable resources plugin (v2.2+):
>
> Set up a single resource for each node and give them all a common label
>
> Then your Jenkinsfile would be:
>
> lock(label: "common-label", variable: "LOCKED_NODE"){
> node(env.LOCKED_NODE){
> //build project
> }
> }
>
> Regards,
> Daniel.
>
> On Thu, Jan 31, 2019 at 7:48 AM Vitaly Karasik > wrote:
>
>> I'd like to mark *whole* pipeline job as throttling resource; and unlike
>> freestyle jobs, Throttleling plugin does't know to do that. I.e. I cannot
>> use "throttle" in pipeline options.
>>
>> On Wednesday, January 30, 2019 at 7:47:20 PM UTC+2, Den Slobozhanskyi
>> wrote:
>>>
>>> Just to clarify - does it mean that Throttling plugin throttles not the
>>> job as a whole, but each step in parallel? My assumption was that
>>> throttling is only for the job, and nested threads have nothing to do with
>>> throttle. By your words it looks like setting throttling to "1" for the job
>>> reduce the possible parallel threads execution to a single thread at a time
>>> as well, is that true?
>>>
>>> If this is not true, you just gather all the jobs under one throttling
>>> category and set the concurrent builds limit to 1.
>>>
>>> BR,
>>> Denys
>>>
>>> среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik
>>> написал:
I have multibranch job, whole pipeline runs on certain node.
Currently I have a slaves with single executor, so multiple jobs cannot
run on the same node. I'd like to use parallel steps inside my pipeline,
so
I need to increase number of executors.
What is the best way to prevent concurrent job execution?
Such configuration was trivial with Jenkins freestyle job and
Throttling plugin - I simple used "Maximum Concurrent Builds Per Node".
But
in pipeline it seems that I cannot use "throttle" for whole pipeline, I
need to use it for each step. Is there more elegant solution?
TIA, Vitaly
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/d6b76faf-f9e6-4960-8dc5-ab79c6c6ac0f%40googlegroups.com
>>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/d7a4d843-79ba-4b46-aaf5-66fe45c00e34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
My job is Multibranch job, for some reason such job, unlike 'regulal' pipeline job, doesn't provide this checkbox. On Thursday, January 31, 2019 at 3:25:53 PM UTC+2, Den Slobozhanskyi wrote: > > [image: Screenshot from 2019-01-31 12-35-45.png] > what plugin do you use precisely? I run jenkins 2.150.1 and this > throttling plugin > https://github.com/jenkinsci/throttle-concurrent-builds-plugin/blob/master/README.md > > . It clearly gives me an option to throttle a pipeline job in job > configurations (yep, 100% pipeline job type) > > четверг, 31 января 2019 г., 8:48:14 UTC+1 пользователь Vitaly Karasik > написал: >> >> I'd like to mark *whole* pipeline job as throttling resource; and unlike >> freestyle jobs, Throttleling plugin does't know to do that. I.e. I cannot >> use "throttle" in pipeline options. >> >> On Wednesday, January 30, 2019 at 7:47:20 PM UTC+2, Den Slobozhanskyi >> wrote: >>> >>> Just to clarify - does it mean that Throttling plugin throttles not the >>> job as a whole, but each step in parallel? My assumption was that >>> throttling is only for the job, and nested threads have nothing to do with >>> throttle. By your words it looks like setting throttling to "1" for the job >>> reduce the possible parallel threads execution to a single thread at a time >>> as well, is that true? >>> >>> If this is not true, you just gather all the jobs under one throttling >>> category and set the concurrent builds limit to 1. >>> >>> BR, >>> Denys >>> >>> среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik >>> написал: I have multibranch job, whole pipeline runs on certain node. Currently I have a slaves with single executor, so multiple jobs cannot run on the same node. I'd like to use parallel steps inside my pipeline, so I need to increase number of executors. What is the best way to prevent concurrent job execution? Such configuration was trivial with Jenkins freestyle job and Throttling plugin - I simple used "Maximum Concurrent Builds Per Node". But in pipeline it seems that I cannot use "throttle" for whole pipeline, I need to use it for each step. Is there more elegant solution? TIA, Vitaly >>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c1350fac-3c06-4c57-9017-a19c8f776054%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
[image: Screenshot from 2019-01-31 12-35-45.png] what plugin do you use precisely? I run jenkins 2.150.1 and this throttling plugin https://github.com/jenkinsci/throttle-concurrent-builds-plugin/blob/master/README.md . It clearly gives me an option to throttle a pipeline job in job configurations (yep, 100% pipeline job type) четверг, 31 января 2019 г., 8:48:14 UTC+1 пользователь Vitaly Karasik написал: > > I'd like to mark *whole* pipeline job as throttling resource; and unlike > freestyle jobs, Throttleling plugin does't know to do that. I.e. I cannot > use "throttle" in pipeline options. > > On Wednesday, January 30, 2019 at 7:47:20 PM UTC+2, Den Slobozhanskyi > wrote: >> >> Just to clarify - does it mean that Throttling plugin throttles not the >> job as a whole, but each step in parallel? My assumption was that >> throttling is only for the job, and nested threads have nothing to do with >> throttle. By your words it looks like setting throttling to "1" for the job >> reduce the possible parallel threads execution to a single thread at a time >> as well, is that true? >> >> If this is not true, you just gather all the jobs under one throttling >> category and set the concurrent builds limit to 1. >> >> BR, >> Denys >> >> среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik >> написал: >>> >>> I have multibranch job, whole pipeline runs on certain node. >>> >>> Currently I have a slaves with single executor, so multiple jobs cannot >>> run on the same node. I'd like to use parallel steps inside my pipeline, so >>> I need to increase number of executors. >>> >>> What is the best way to prevent concurrent job execution? >>> >>> Such configuration was trivial with Jenkins freestyle job and Throttling >>> plugin - I simple used "Maximum Concurrent Builds Per Node". But in >>> pipeline it seems that I cannot use "throttle" for whole pipeline, I need >>> to use it for each step. Is there more elegant solution? >>> >>> TIA, Vitaly >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5ed835bb-43fb-434d-9b5c-15d48e47b040%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
>Set up a single resource for each node and give them all a common label
Thank you - I thought about using lockable resources, but didn't know
that I can mark each node as separate resource.
I'll check it.
On Thursday, January 31, 2019 at 11:43:30 AM UTC+2, Daniel Butler wrote:
>
> You could use the lockable resources plugin (v2.2+):
>
> Set up a single resource for each node and give them all a common label
>
> Then your Jenkinsfile would be:
>
> lock(label: "common-label", variable: "LOCKED_NODE"){
> node(env.LOCKED_NODE){
> //build project
> }
> }
>
> Regards,
> Daniel.
>
> On Thu, Jan 31, 2019 at 7:48 AM Vitaly Karasik > wrote:
>
>> I'd like to mark *whole* pipeline job as throttling resource; and unlike
>> freestyle jobs, Throttleling plugin does't know to do that. I.e. I cannot
>> use "throttle" in pipeline options.
>>
>> On Wednesday, January 30, 2019 at 7:47:20 PM UTC+2, Den Slobozhanskyi
>> wrote:
>>>
>>> Just to clarify - does it mean that Throttling plugin throttles not the
>>> job as a whole, but each step in parallel? My assumption was that
>>> throttling is only for the job, and nested threads have nothing to do with
>>> throttle. By your words it looks like setting throttling to "1" for the job
>>> reduce the possible parallel threads execution to a single thread at a time
>>> as well, is that true?
>>>
>>> If this is not true, you just gather all the jobs under one throttling
>>> category and set the concurrent builds limit to 1.
>>>
>>> BR,
>>> Denys
>>>
>>> среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik
>>> написал:
I have multibranch job, whole pipeline runs on certain node.
Currently I have a slaves with single executor, so multiple jobs cannot
run on the same node. I'd like to use parallel steps inside my pipeline,
so
I need to increase number of executors.
What is the best way to prevent concurrent job execution?
Such configuration was trivial with Jenkins freestyle job and
Throttling plugin - I simple used "Maximum Concurrent Builds Per Node".
But
in pipeline it seems that I cannot use "throttle" for whole pipeline, I
need to use it for each step. Is there more elegant solution?
TIA, Vitaly
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/d6b76faf-f9e6-4960-8dc5-ab79c6c6ac0f%40googlegroups.com
>>
>>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/01769347-83f1-4b9c-8a98-204d1a0b5ca2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
You could use the lockable resources plugin (v2.2+):
Set up a single resource for each node and give them all a common label
Then your Jenkinsfile would be:
lock(label: "common-label", variable: "LOCKED_NODE"){
node(env.LOCKED_NODE){
//build project
}
}
Regards,
Daniel.
On Thu, Jan 31, 2019 at 7:48 AM Vitaly Karasik wrote:
> I'd like to mark *whole* pipeline job as throttling resource; and unlike
> freestyle jobs, Throttleling plugin does't know to do that. I.e. I cannot
> use "throttle" in pipeline options.
>
> On Wednesday, January 30, 2019 at 7:47:20 PM UTC+2, Den Slobozhanskyi
> wrote:
>>
>> Just to clarify - does it mean that Throttling plugin throttles not the
>> job as a whole, but each step in parallel? My assumption was that
>> throttling is only for the job, and nested threads have nothing to do with
>> throttle. By your words it looks like setting throttling to "1" for the job
>> reduce the possible parallel threads execution to a single thread at a time
>> as well, is that true?
>>
>> If this is not true, you just gather all the jobs under one throttling
>> category and set the concurrent builds limit to 1.
>>
>> BR,
>> Denys
>>
>> среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik
>> написал:
>>>
>>> I have multibranch job, whole pipeline runs on certain node.
>>>
>>> Currently I have a slaves with single executor, so multiple jobs cannot
>>> run on the same node. I'd like to use parallel steps inside my pipeline, so
>>> I need to increase number of executors.
>>>
>>> What is the best way to prevent concurrent job execution?
>>>
>>> Such configuration was trivial with Jenkins freestyle job and Throttling
>>> plugin - I simple used "Maximum Concurrent Builds Per Node". But in
>>> pipeline it seems that I cannot use "throttle" for whole pipeline, I need
>>> to use it for each step. Is there more elegant solution?
>>>
>>> TIA, Vitaly
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/d6b76faf-f9e6-4960-8dc5-ab79c6c6ac0f%40googlegroups.com
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAO37hbgQQWsggy8VdYxnn6RhWmYP%3DVBh4A%3D8JxO-etH6iOSpTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
I'd like to mark *whole* pipeline job as throttling resource; and unlike freestyle jobs, Throttleling plugin does't know to do that. I.e. I cannot use "throttle" in pipeline options. On Wednesday, January 30, 2019 at 7:47:20 PM UTC+2, Den Slobozhanskyi wrote: > > Just to clarify - does it mean that Throttling plugin throttles not the > job as a whole, but each step in parallel? My assumption was that > throttling is only for the job, and nested threads have nothing to do with > throttle. By your words it looks like setting throttling to "1" for the job > reduce the possible parallel threads execution to a single thread at a time > as well, is that true? > > If this is not true, you just gather all the jobs under one throttling > category and set the concurrent builds limit to 1. > > BR, > Denys > > среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik > написал: >> >> I have multibranch job, whole pipeline runs on certain node. >> >> Currently I have a slaves with single executor, so multiple jobs cannot >> run on the same node. I'd like to use parallel steps inside my pipeline, so >> I need to increase number of executors. >> >> What is the best way to prevent concurrent job execution? >> >> Such configuration was trivial with Jenkins freestyle job and Throttling >> plugin - I simple used "Maximum Concurrent Builds Per Node". But in >> pipeline it seems that I cannot use "throttle" for whole pipeline, I need >> to use it for each step. Is there more elegant solution? >> >> TIA, Vitaly >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d6b76faf-f9e6-4960-8dc5-ab79c6c6ac0f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
Just to clarify - does it mean that Throttling plugin throttles not the job as a whole, but each step in parallel? My assumption was that throttling is only for the job, and nested threads have nothing to do with throttle. By your words it looks like setting throttling to "1" for the job reduce the possible parallel threads execution to a single thread at a time as well, is that true? If this is not true, you just gather all the jobs under one throttling category and set the concurrent builds limit to 1. BR, Denys среда, 30 января 2019 г., 14:17:15 UTC+1 пользователь Vitaly Karasik написал: > > I have multibranch job, whole pipeline runs on certain node. > > Currently I have a slaves with single executor, so multiple jobs cannot > run on the same node. I'd like to use parallel steps inside my pipeline, so > I need to increase number of executors. > > What is the best way to prevent concurrent job execution? > > Such configuration was trivial with Jenkins freestyle job and Throttling > plugin - I simple used "Maximum Concurrent Builds Per Node". But in > pipeline it seems that I cannot use "throttle" for whole pipeline, I need > to use it for each step. Is there more elegant solution? > > TIA, Vitaly > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/08107dc8-9bb4-4979-89c3-302a00183bc1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?
I have multibranch job, whole pipeline runs on certain node. Currently I have a slaves with single executor, so multiple jobs cannot run on the same node. I'd like to use parallel steps inside my pipeline, so I need to increase number of executors. What is the best way to prevent concurrent job execution? Such configuration was trivial with Jenkins freestyle job and Throttling plugin - I simple used "Maximum Concurrent Builds Per Node". But in pipeline it seems that I cannot use "throttle" for whole pipeline, I need to use it for each step. Is there more elegant solution? TIA, Vitaly -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/cab8c3e6-694c-4329-bc08-6414d4e318a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
