[JIRA] (JENKINS-49623) Resource list stored in env variable empty when label is used in locking

3 views
Skip to first unread message

jmyllyla@gmail.com (JIRA)

unread,
Feb 19, 2018, 6:09:03 AM2/19/18
to jenkinsc...@googlegroups.com
Janne Myllyla created an issue
 
Jenkins / Bug JENKINS-49623
Resource list stored in env variable empty when label is used in locking
Issue Type: Bug Bug
Assignee: Unassigned
Components: lockable-resources-plugin
Created: 2018-02-19 11:08
Environment: Jenkins 2.89.4
Lockable resources 2.1
Priority: Minor Minor
Reporter: Janne Myllyla

When using lock from jenkinsfile and using label, then the list stored to env variable is empty.  Lock seemed to work, but in my use case I need to have access to the fields of locked resource. Unfortunately there does not seem to be any easy way to access locked resources name and details, except via the env variable. 

I tried locking with resources name and then list was populated properly, but this is not an option when the lock is used to monitor access to multiple resources of same type and there is a need to have the name and details field of the resource.

 

 

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

amuniz@cloudbees.com (JIRA)

unread,
Mar 7, 2018, 6:22:02 AM3/7/18
to jenkinsc...@googlegroups.com
Antonio Muñiz commented on Bug JENKINS-49623
 
Re: Resource list stored in env variable empty when label is used in locking

2.2 ships JENKINS-40997 which should cover your use case. Actually I don't know what variable are you talking about as the feature did not exist before.

tobias-jenkins@23.gs (JIRA)

unread,
Feb 26, 2020, 4:19:03 PM2/26/20
to jenkinsc...@googlegroups.com
Tobias Gruetzmacher assigned an issue to Tobias Gruetzmacher
 
Change By: Tobias Gruetzmacher
Assignee: Tobias Gruetzmacher
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

tobias-jenkins@23.gs (JIRA)

unread,
Feb 26, 2020, 4:21:02 PM2/26/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages