tirsdag 13. mars 2018 15.52.32 UTC+1 skrev Steven Foster følgende:
>
> On Tuesday, March 13, 2018 at 1:02:02 PM UTC, Sverre Moe wrote:
>>
>> Looks like there is a fix for this in the works.
>> https://github.com/jenkinsci/lockable-resources-plugin/pull/70
>>
>
> I *think* this fix is just for manua
On Tuesday, March 13, 2018 at 1:02:02 PM UTC, Sverre Moe wrote:
>
> Looks like there is a fix for this in the works.
> https://github.com/jenkinsci/lockable-resources-plugin/pull/70
>
I *think* this fix is just for manual reservation/unreservation of a
resource by a user (there's a button in the
Looks like there is a fix for this in the works.
https://github.com/jenkinsci/lockable-resources-plugin/pull/70
--
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
Running two builds of pipeline-test2 works fine. The second build gets all
three resources when the first build has released them.
So seems the problem is when locking on label. The build will only get the
first release lock.
tirsdag 13. mars 2018 08.44.21 UTC+1 skrev Sverre Moe følgende:
>
> I
I created two seperate pipeline jobs to test this with.
Got the same behaviour.
*pipeline-test1*
*def stepsForParallel = [:]stepsForParallel["nodeName4"] =
transformIntoStep("nodeName4")parallel stepsForParalleldef
transformIntoStep(nodeName) {return {node("master") {
torsdag 8. mars 2018 17.06.12 UTC+1 skrev Sverre Moe følgende:
>
>
>
> torsdag 8. mars 2018 12.37.47 UTC+1 skrev Reinhold Füreder følgende:
>>
>> Very naïve thought(s):
>>
>>
>>
>> While “*Do not know why nodeName1 acquired the lock before nodeName
>> released.*“ might be just a matter of output
torsdag 8. mars 2018 12.37.47 UTC+1 skrev Reinhold Füreder følgende:
>
> Very naïve thought(s):
>
>
>
> While “*Do not know why nodeName1 acquired the lock before nodeName
> released.*“ might be just a matter of output flushing/buffering,
>
I thought so also, probably because of parallell exe
Very naïve thought(s):
While “Do not know why nodeName1 acquired the lock before nodeName released.“
might be just a matter of output flushing/buffering, “The entire build hangs
and goes no further.” sounds really frightening to me.
Maybe it is the usage of lock inside parallel step and/or some
Lockable Resource Plugin
Lockable Resources Manager
Lockable Resources
resource: testing1-repository, labels:testing-repository
resource: testing2-repository, labels:testing-repository
resource: testing3-repository, labels:testing-repository
Configured these 3 resources in Jenkin
