Are pipeline locks expected to behave when used by two nodes simultaneously?
My Jenkinsfile defines the following helper -
def log(msg) {
echo((new Date().format("-MM-dd'T'HH:mm:ss: ")) + msg)
}
def lockDB(number, callback) {
try {
log "${number}: Acquiring lock ..."
lock(resour
Hi there - Has anyone run into problems with pipeline's lock command? On a
multibranch project with 2 nodes (master + 1 slave), it occasionally seems
to allow two concurrent jobs to acquire the same lock. I have Jenkins
2.45 with Lockable Resources 1.11 and Pipeline 2.9.
--
You received this m
assign a
> branch to be built, though I don't want that git "branch to be built" to
> merge between long-lived branches.
>
> Mark Waite
>
> On Sun, Jun 5, 2016 at 6:10 AM Jonathan del Strother > wrote:
>
>> Is there any way to get the multibranch plugi
u choose git in
> the snippet generator.
>
> I still haven't found the "best" way to handle those additional git plugin
> options when dealing with merges between long-lived git branches. When I
> assign those types of options, I seem to also be required to assign a
&g
Is there any way to get the multibranch plugin to share its git checkouts?
It's fetching a fresh clone from github for every single branch, which
seems excessive when I have 30 branches and a 500MB repo. I'm struggling
to get it working because the initial checkouts keep getting killed due to
