[JIRA] (JENKINS-56250) Ansible Tower Plugin not injecting Environment Variables for later use
Title: Message Title John Westcott updated JENKINS-56250 Jenkins / JENKINS-56250 Ansible Tower Plugin not injecting Environment Variables for later use Change By: John Westcott Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197817.1550853641000.4799.1578495240528%40Atlassian.JIRA.
[JIRA] (JENKINS-56250) Ansible Tower Plugin not injecting Environment Variables for later use
Title: Message Title John Westcott updated JENKINS-56250 This should be fixed in the next version of the plugin (to be released soon). In a pipeline you will be able to do something like: results = ansibleTower( ... ) println(results.variable_name) Jenkins / JENKINS-56250 Ansible Tower Plugin not injecting Environment Variables for later use Change By: John Westcott Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197817.1550853641000.2040.1565720040584%40Atlassian.JIRA.
[JIRA] (JENKINS-56250) Ansible Tower Plugin not injecting Environment Variables for later use
Title: Message Title
Alex Taylor updated an issue
Jenkins / JENKINS-56250
Ansible Tower Plugin not injecting Environment Variables for later use
Change By:
Alex Taylor
Issue:When creating a ENV variable within the Ansible Tower plugin API calls on a pipeline, that ENV variable is not usable inside of subsequent steps for Jenkins.Steps to reproduce:1. Create a Pipeline job with an Ansible Tower step2. Inside of that step call an ansible script which uses the suggested line:{code:java} - name: Set a Jenkins variable debug:msg: "JENKINS_EXPORT VAR_NAME=value"{code}3. Try to echo that `VAR_NAME` using an `echo ${env.VAR_NAME} in a new stage4. Observe the variable comes back as "null"I even tried to expand the scope of the variable name using a `withEnv(['VAR_NAME=""']) {` at the beginning but that still does not workExpected Result:I would expect to see a ENV variable later in the pipeline but maybe the scope of that variable is only for within the ansible script?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56250) Ansible Tower Plugin not injecting Environment Variables for later use
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-56250
Ansible Tower Plugin not injecting Environment Variables for later use
Issue Type:
Bug
Assignee:
John Westcott
Components:
ansible-tower-plugin
Created:
2019-02-22 16:40
Priority:
Major
Reporter:
Alex Taylor
Issue: When creating a ENV variable within the Ansible Tower plugin API calls on a pipeline, that ENV variable is not usable inside of subsequent steps for Jenkins. Steps to reproduce: 1. Create a job with an Ansible Tower step 2. Inside of that step call an ansible script which uses the suggested line:
- name: Set a Jenkins variable
debug:
msg: "JENKINS_EXPORT VAR_NAME=value"
3. Try to echo that `VAR_NAME` using an `echo ${env.VAR_NAME} in a new stage 4. Observe the variable comes back as "null" I even tried to expand the scope of the variable name using a `withEnv(['VAR_NAME=""']) {` at the beginning but that still does not work Expected Result: I would expect to see a ENV variable later in the pipeline but maybe the scope of that variable is only for within the ansible script?
