*Please Excuse & advise, if this is not appropriate to continue post in an
old post. *
We are using the cloudbees jenkins. And are optimizing the workflows (the
new name: pipeline) to get some concurrency going. The way i understand
concurrency is the simultaneous execution. So a value of
concurrency: 1 --> allow only one instance for the stage
concurrency: n --> allow 'n' number of instance for the stage
Am i am interpreting it correctly?
What if the concurrency is not specified (and the option to execute
concurrently in the workflow config is not checked)? Will the jobs run
serially, meaning stay as pending until the first job is over?
What is concurrency: 0 (a came accross that 0 means unlimited concurrency!
is this correct)?
And to get some clarity, i used the workflow given by Sebastien here. But
to get some clarity on the timelines, i entered the date command to mark
the timelines for the stage's start and end. below is the script.
stage name: 'sync'
node("master") {
echo "before sync"
sh "sleep 10"
echo "after sync"
sh "date"
}
stage name: 'build_and_test', concurrency: 1
node("master") {
stage name: 'build'
echo "before build"
sh "date"
sh "sleep 10"
echo "build 1/3"
sh "sleep 10"
echo "build 2/3"
sh "sleep 10"
echo "build 3/3"
sh "date"
stage name: 'test', concurrency: 1
echo "before test"
sh "date"
sh "sleep 10"
echo "test 1/3"
sh "sleep 10"
echo "test 2/3"
sh "sleep 10"
echo "test 3/3"
sh "date"
}
I still notice the issue reported by Sebastien. i have set up 7 executors
and fired 4 jobs on the same workflow.
1. All the 4 jobs triggered the first stage of sync
2. All the 4 jobs triggered the second stage of build_and_test which have a
concurrency: 1
3. NOT all the 4 triggers the proceeds to the 'stage name: 'test',
concurrency: 1'
Why are the jobs running concurrently for 'stage name: 'build_and_test',
concurrency: 1' ??
IS my understanding on the concurrency flawed?
job console output:
http://pastebin.com/n6tJJ0Zu
http://pastebin.com/x9tryKUV
http://pastebin.com/6hsan1KY
http://pastebin.com/kPbtxKbj
This is a simple timeline for all the 4 jobs
Stage Sync 'build_and_test', concurrency: 1 'test', concurrency:
1
26 Fri Jan 29 16:20:39 UTC 2016 Fri Jan 29 16:20:40 UTC 2016 Fri Jan 29
16:21:10 UTC 2016 Fri Jan 29 16:21:11 UTC 2016 Fri Jan 29 16:21:41 UTC
2016
27 Fri Jan 29 16:20:43 UTC 2016 Fri Jan 29 16:20:43 UTC 2016 Fri Jan 29
16:21:14 UTC 2016 Entering stage test/Waiting for builds [26]/Canceled
since #28 got here
28 Fri Jan 29 16:20:46 UTC 2016 Fri Jan 29 16:20:47 UTC 2016 Fri Jan 29
16:21:17 UTC 2016 Entering stage test/Canceling older #27/Waiting for
builds [26]/Canceled since #29 got here
29 Fri Jan 29 16:20:51 UTC 2016 Fri Jan 29 16:20:51 UTC 2016 Fri Jan 29
16:21:22 UTC 2016 Fri Jan 29 16:21:42 UTC 2016 Fri Jan 29 16:22:12 UTC
2016
On Tuesday, March 10, 2015 at 6:23:39 AM UTC-6, sebastien....@gmail.com
wrote:
>
> On Thursday, February 26, 2015 at 11:39:45 PM UTC+1, Jesse Glick wrote:
>>
>> On Thu, Feb 26, 2015 at 3:59 PM, <sebastien....@gmail.com> wrote:
>> > Did you test my simple workflow?
>>
>> No, sorry, was just guessing that your issue was a duplicate.
>>
>> > Or is there as way for me to test it on a daily build of the plugin?
>>
>> $ git clone https://github.com/jenkinsci/workflow-plugin.git
>> $ mvn -f workflow-plugin -DskipTests install
>> $ mvn -f workflow-plugin/aggregator hpi:run
>> $ <your-browser> http://localhost:8080/jenkins/
>>
>
> Hi Jesse,
>
> I just tested with workflow-1.3-39-g694a0f0, and cannot reproduce the
> issue.
>
> Thank you!
>
--
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/32329f05-41a8-45a5-9552-31fa48a8283a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
