Re: Sporadic MSBuild errors / possible durable task issue?

2019-01-31 Thread Daniel Becroft 
On Fri, Feb 1, 2019 at 2:31 AM Steven Foster 
wrote:

> After updating Jenkins with plugins from early April 2018, I'm seeing
> inconsistent failures in my pipelines' calls to MSBuild which I cannot
> reproduce outside of Jenkins. It occurs in both powershell and bat steps.
>
> The error presents as
>
> 0>MSBUILD : error MSB4166: Child node "14" exited prematurely. Shutting
> down. Diagnostic information may be found in files in the temporary files
> directory named MSBuild_*.failure.txt.
>
> There is no such extra information file. This looks a bit like an
> interrupt to me, is there a way I can reproduce how Jenkins sends
> interrupts so I can verify that?
> Are there any advanced durable task debugging techniques I could use to
> find out what could be causing an interrupt or something else?
>

We had a similar issue, and it ended up being related to MSBuild itself,
not Jenkins. The jobs seemed to work correctly when run from a command
line, but it took a while and they eventually started failing as well.

Our issue was due to the maximum number of temp files in %TEMP% being
exceeded (see the GetTempFileNameA[1] function, it has an internal limit of
65,535). Once we cleared those out (and resolved the bug in our code that
wasn't cleaning them up), the builds worked again.

[1] -
https://docs.microsoft.com/en-us/windows/desktop/api/fileapi/nf-fileapi-gettempfilenamea

-- 
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/CAJM0iSQNCSNi3Z0oQSfZTJD9ZmbjKwCyNO8VNuhgimiXDwLk8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Sporadic MSBuild errors / possible durable task issue?

2019-01-31 Thread Steven Foster 


On Thursday, January 31, 2019 at 4:45:40 PM UTC, Simon Richter wrote:
>
>
> There are a few things going on: 
>
>  - MSBuild sticks around after a build if the same project is rebuilt 
>  - Jenkins kills processes belonging to a build after it believes the 
> build has finished 
>  - MSBuild has serious issues with memory management 
>
> All of these are somewhat unpredictable. 
>
> I've found that it becomes a bit better if you set an environment variable 
>
> MSBUILDDISABLENODEREUSE=1 
>
> as suggested[1] by the VS team, disable the Jenkins Process Tree 
> Killer[2] and try to use the 64 bit version of MSBuild[3] to avoid 
> running out of virtual memory (which MSBuild sometimes, but not always 
> reports as the reason for termination in the log files in %APPDATA%\Temp) 
>

Thanks for the leads, I will look into those. Just to note that the issue 
only appeared after updating Jenkins (identical build agent images) and the 
builds were running fine before.

-- 
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/e7a25c32-ed5d-489b-8f63-f87902b12e57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Sporadic MSBuild errors / possible durable task issue?

2019-01-31 Thread Simon Richter 
Hi,

On 31.01.19 17:31, Steven Foster wrote:

> There is no such extra information file. This looks a bit like an
> interrupt to me, is there a way I can reproduce how Jenkins sends
> interrupts so I can verify that?

There are a few things going on:

 - MSBuild sticks around after a build if the same project is rebuilt
 - Jenkins kills processes belonging to a build after it believes the
build has finished
 - MSBuild has serious issues with memory management

All of these are somewhat unpredictable.

I've found that it becomes a bit better if you set an environment variable

MSBUILDDISABLENODEREUSE=1

as suggested[1] by the VS team, disable the Jenkins Process Tree
Killer[2] and try to use the 64 bit version of MSBuild[3] to avoid
running out of virtual memory (which MSBuild sometimes, but not always
reports as the reason for termination in the log files in %APPDATA%\Temp)

   Simon

[1]
https://developercommunity.visualstudio.com/content/problem/301840/msbuild-not-terminating.html

[2] https://wiki.jenkins.io/display/JENKINS/ProcessTreeKiller

[3] https://gitlab.kitware.com/cmake/cmake/issues/18219

-- 
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/115f850e-abd8-f380-0157-9a6676f382c6%40hogyros.de.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Sporadic MSBuild errors / possible durable task issue?

2019-01-31 Thread Steven Foster 
After updating Jenkins with plugins from early April 2018, I'm seeing 
inconsistent failures in my pipelines' calls to MSBuild which I cannot 
reproduce outside of Jenkins. It occurs in both powershell and bat steps.

The error presents as 
 
0>MSBUILD : error MSB4166: Child node "14" exited prematurely. Shutting down
. Diagnostic information may be found in files in the temporary files 
directory named MSBuild_*.failure.txt.

There is no such extra information file. This looks a bit like an interrupt 
to me, is there a way I can reproduce how Jenkins sends interrupts so I can 
verify that?
Are there any advanced durable task debugging techniques I could use to 
find out what could be causing an interrupt or something else?

-- 
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/6e8d5f7f-7713-4052-9054-220d92b66a6f%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?

2019-01-31 Thread Vitaly Karasik 
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: Unable to run git repository on jenkins which is deplyed under tomcat8

2019-01-31 Thread Mark Waite 
Did you assign a private key credential to that job?  A username.password
credential won't work with an SSH URL.  A private key credential won't work
with an http or https URL.

If the private key has a passphrase, did you provide the passphrase when
defining the credential in Jenkins?

Did you confirm that the private key will authenticate from the command
line?

Mark Waite

On Tue, Jan 29, 2019 at 3:17 PM  wrote:

> Hi All,
>
> I am not able to run my git repo on Jenkins ,attach is the screen shot for
> your reference.
>
> Regards,
> Archana Srichandan
>
> --
> 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/50dd7ccf-9ad6-45e3-a5fc-9cee050a7737%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
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/CAO49JtGvL%3DxHGju7a%2BbGvVd7Bhs7gvhr09Qd%3Dr3zkY1OOs2DhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Cannot use credentialsId in multibranchPipelineJob

2019-01-31 Thread Polina Koornneef 
Hello,

I am trying to create multibranchPipelineJob using DSL. Here is my script:

multibranchPipelineJob('job name') {
branchSources {
branchSource {
source {
git {
remote('git-url')
credentialsId('credentialsId')
}
}
}
}
}


but I get:


Processing DSL script JenkinsItems.groovy
ERROR: (JenkinsItems.groovy, line 44) No signature of method: 
java.lang.String.call() is applicable for argument types: (java.lang.String) 
values: [656567d3-7645-4289-a0dd-fb1ef0f09536]
Possible solutions: wait(), any(), wait(long), split(java.lang.String), 
any(groovy.lang.Closure), each(groovy.lang.Closure)
Finished: FAILURE


Do you have any idea why credentialsId is not accepted?




-- 
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/8840de15-21dc-4077-a824-98c8386a8bce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

What is the journey to migrate my jenkins1(Build flow DSL) jobs to jenkins2 pipeline. Can Anybody out here can guide me in this jouney as I am just a new entrant in this area Please its urgent

2019-01-31 Thread davish bhardwaj 
What is the journey to migrate my jenkins1(Build flow DSL) jobs to jenkins2 
pipeline. Can Anybody out here can guide me in this jouney as I am just a 
new entrant in this area Please its urgent

-- 
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/e3d6dc69-f358-4481-b653-14d3d8931342%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?

2019-01-31 Thread Den Slobozhanskyi 


[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.

Windows farm | jenkins slave configuration via "Launch agent via execution of command on the master"

2019-01-31 Thread LnT 

Hello -

Looking for help - w.r.t jenkins slave configuration via *"Launch agent via 
execution of command on the master"*
As I'm looking to minimize the memory consumption in remote slave machine 
via Availability *"Take this agent online when in demand and offline when 
idle"*

Jenkins master is Windows 2008 Server
jenkins slave is Windows 2008 Server

Installed psexec in Jenkins master (ref : 
https://docs.microsoft.com/en-us/sysinternals/downloads/psexec)
Please find below log of lauching the slave agent. Agent is not getting 
connected. 




*--just
 
before slave test_node gets launched ...executing pre-launch scripts 
...[01/31/19 14:06:52] Launching agent$ C:\PSTools\psexec **\\RemoteServer* 
* -u jenkinsUser -p Password cmd /C "java -jar 
C:\slave\agent.jar"*


*PsExec v2.2 - Execute processes remotelyCopyright (C) 2001-2016 Mark 
RussinovichSysinternals - **www.sysinternals.com* 


*<===[JENKINS REMOTING CAPACITY]===Exception in thread "main" Connecting to 
RemoteServer...*

*Starting PSEXESVC service on RemoteServer...*

*Connecting with PsExec service on RemoteServer...*

*Starting cmd on RemoteServer...*






















*cmd exited on RemoteServer with error code 1.ERROR: Unable to launch the 
agent for test_nodejava.io.EOFException at 
java.io.ObjectInputStream$PeekInputStream.readFully(Unknown Source) at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown Source) at 
java.io.ObjectInputStream.readStreamHeader(Unknown Source) at 
java.io.ObjectInputStream.(Unknown Source) at 
hudson.remoting.Capability$2.(Capability.java:151) at 
hudson.remoting.Capability.read(Capability.java:151) at 
hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:435) at 
hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:354) at 
hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:415) at 
hudson.slaves.CommandLauncher.launch(CommandLauncher.java:153) at 
hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:288) at 
jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
 at 
jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
 at 
java.util.concurrent.FutureTask.run(Unknown Source) at 
java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at 
java.lang.Thread.run(Unknown Source)ERROR: Process terminated with exit 
code 
1--*

-- 
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/e6df1c91-217c-40dd-a759-d90369201650%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Historic graph for CSV data

2019-01-31 Thread Simon Richter 
Hi,

we have a repository with translations and a script that verifies that
the translated strings are still up to date with the source code. The
script generates a CSV file like

LANG;TRANSLATED;FUZZY;UNTRANSLATED
bg;1272;2991;1323
ca;2752;1848;986
cs;2762;2198;626

Now I'd like to visualize that in a kind of dashboard, with historical
data from the last builds.

The "hacky" way would be to import the current data into an RRD file
that is kept between builds, and used to generate graphs. For that, I'd
need a way to keep the RRD file, i.e. tell Jenkins that this file is to
be preserved between builds and moved to new workspaces. I'm not sure
there is a mechanism for that, is there?

Is there a non-hacky way as well? I can use the Plot plugin to generate
a graph for the first language over time, but the Plugin does not read
multiple lines from CSV. In theory, I could make one CSV per language
and instantiate the Plot plugin once per language as well, but I'd
really like something that takes the list of languages from the CSV file
as well.

Ideas?

   Simon

-- 
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/6266ff6c-1b62-4af1-0721-d3cc63ed1f85%40hogyros.de.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?

2019-01-31 Thread Vitaly Karasik 
>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?

2019-01-31 Thread Daniel Butler 
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.