[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined

1 view
Skip to first unread message

pjdarton@gmail.com (JIRA)

unread,
Aug 15, 2019, 12:04:02 PM8/15/19
to jenkinsc...@googlegroups.com
pjdarton commented on Bug JENKINS-46375
 
Re: vSphere template definition doesn't allow environment variables to be defined

It looks like there's a problem in the WebUI "jelly" code that binds the UI to the data that's preventing folks from doing this.
While I don't see why the code doesn't work as-is (as it's doing the same stuff as works elsewhere), I think it's a fairly trivial fix (especially as the docker plugin has a working example we can use for inspiration).

I've started work to fix this in PR#105. Those changes will likely go into the next release.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

pjdarton@gmail.com (JIRA)

unread,
Aug 15, 2019, 12:05:04 PM8/15/19
to jenkinsc...@googlegroups.com
pjdarton assigned an issue to pjdarton
 
Jenkins / Improvement JENKINS-46375
Change By: pjdarton
Issue Type: Bug Improvement
Assignee: pjdarton

pjdarton@gmail.com (JIRA)

unread,
Aug 15, 2019, 12:05:04 PM8/15/19
to jenkinsc...@googlegroups.com
pjdarton started work on Bug JENKINS-46375
 
Change By: pjdarton
Status: Open In Progress

fredrik.bruzelius@qlik.com (JIRA)

unread,
Sep 12, 2019, 3:10:02 AM9/12/19
to jenkinsc...@googlegroups.com
Fredrik Bruzelius commented on Improvement JENKINS-46375
 
Re: vSphere template definition doesn't allow environment variables to be defined

I think this is not limited to just the "Environment variables" node property. I am using the Workspace Cleanup Plugin and would like to set the "Disable deferred wipeout on this node" property, which is also missing.

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

pjdarton@gmail.com (JIRA)

unread,
Sep 12, 2019, 5:20:05 AM9/12/19
to jenkinsc...@googlegroups.com
pjdarton commented on Improvement JENKINS-46375

You'll be pleased to know that

  1. You are correct - this does affect the ws cleanup plugin node property, along with pretty much any other node property.
  2. I've fixed this issue in the as-yet-unreleased code, which I'm intending to release "soon" ... which will be "sooner" if you help ...
  3. ... you can get a pre-release build from here. Please try it out and let me know if it works for you - that'll help me and help speed up the official release.

fredrik.bruzelius@qlik.com (JIRA)

unread,
Sep 17, 2019, 9:17:03 AM9/17/19
to jenkinsc...@googlegroups.com

Sorry for the late reply, I've been out of office for a few days.

I deployed the pre-release to our staging environment, and successfully managed to set both the Ws Cleanup property as well as environment variables and tool locations. So AFAICS the change works out well.

fredrik.bruzelius@qlik.com (JIRA)

unread,
Sep 17, 2019, 9:18:02 AM9/17/19
to jenkinsc...@googlegroups.com
Fredrik Bruzelius edited a comment on Improvement JENKINS-46375
Sorry for the late reply, I've been out of office for a few days.

I deployed the pre-release to our staging environment, and successfully managed to set both the Ws Cleanup node property as well as environment variables and tool locations. So AFAICS the change works out well.

pjdarton@gmail.com (JIRA)

unread,
Sep 24, 2019, 11:26:03 AM9/24/19
to jenkinsc...@googlegroups.com
pjdarton resolved as Fixed
 

Fixed in plugin version 2.21, which was released a few minutes ago.

Change By: pjdarton
Status: In Progress Resolved
Assignee: pjdarton
Resolution: Fixed
Reply all
Reply to author
Forward
0 new messages