[JIRA] (JENKINS-61794) how to pass multiple credentials to ansible tower from jenkins job
Title: Message Title John Westcott updated JENKINS-61794 The suggested steps resolved the issue. Jenkins / JENKINS-61794 how to pass multiple credentials to ansible tower from jenkins job Change By: John Westcott Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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
[JIRA] (JENKINS-61794) how to pass multiple credentials to ansible tower from jenkins job
Title: Message Title John Westcott commented on JENKINS-61794 Re: how to pass multiple credentials to ansible tower from jenkins job The plugin should already support adding multiple credentials back to tower. Try using a comma separated list of credential IDs or names. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205637.1585897505000.9703.1586786580191%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott resolved as Fixed Jenkins / JENKINS-61586 Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Change By: John Westcott Status: In Progress Resolved Resolution: Fixed Released As: 0.14.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.11892.1585050780204%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott stopped work on JENKINS-61586 Change By: John Westcott Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.11888.1585050720329%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott started work on JENKINS-61586 Change By: John Westcott Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.11890.1585050720356%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 I am hoping that the 0.14.1 will fix the issue with the extracting the version which is what is causing the machine credentials to fail. As for the number of days it can vary based on your installation. It appears to be published out on the plugin page but now its a matter of how long will that take to sync down to your installation. i.e. I've seen some installations which have additional proxies between Jenkins and the update center; I'd say to check back later tonight and then again tomorrow. You can also look at what your update center is set to and when your installation last checked for updates. To do this go to manage jenkins => manage plugins => advanced tab. The last field on here Update Site is where you are pulling plugins from and in the bottom right corner of the page there should be text indicating when the installation last pulled that source (i.e. Update information obtained: 4 hr 40 min ago). If that isn't recent you can hit the "check now" button and it should try to fetch the current data. I am seeing the 0.14.1 version of the plugin after hitting the check now button and my update site is set to the default: https://updates.jenkins.io/update-center.json Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 I just checked on the plugin site (https://plugins.jenkins.io/ansible-tower/) its still referencing 0.14.0 but on the Jenkins Update center (https://updates.jenkins.io/current/update-center.json) it looks like 0.14.1 is there. Please check your plugins page in Jenkins and see if the 0.14.1 version is available to you to test. If not, you may need to check over the next couple of days for it to become available. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.11396.1584990360142%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott started work on JENKINS-61586 Change By: John Westcott Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.11337.1584982440490%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 This appears to have been an issue specifically with AWX v8.0.0 which reported its version as 8.0.0.0 (a 4 part notation instead of a three part notation). Jenkins 0.14.1 has been released which should hopefully address this scenario. It may take a couple days to be available for download. Please test and let me know if this now works. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.11335.1584982440452%40Atlassian.JIRA.
[JIRA] (JENKINS-60352) Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-60352 Re: Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1 This appears to have been an issue specifically with AWX v8.0.0 which reported its version as 8.0.0.0 (a 4 part notation instead of a three part notation). Jenkins 0.14.1 has been released which should hopefully address this scenario. It may take a couple days to be available for download. Please test and let me know if this now works. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.203369.1575384648000.11333.1584982440395%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Thanks you for the details, I believe I know what is going on now and am working on a fix. I'll let you know when that has been pushed and is ready for testing. Hopefully that will be later today. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.11255.1584976440221%40Atlassian.JIRA.
[JIRA] (JENKINS-60352) Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-60352 Re: Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1 Thanks you for the details, I believe I know what is going on now and am working on a fix. I'll let you know when that has been pushed and is ready for testing. Hopefully that will be later today. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.203369.1575384648000.11189.1584974580228%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title
John Westcott commented on JENKINS-61586
Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
In Tower 3.5 they changed how credentials are passed through he API. The commit that tried to compensate for that was release as part of 0.14.0. https://github.com/jenkinsci/ansible-tower-plugin/commit/4f2dc4055519fc2c247897209af1a135bfe02864 So we want to be using the latest version of the plugin to get those changes. The NPE exception you sent me is related to this line of code: `this.towerVersion.is_greater_or_equal("3.5.0") ||` Which is telling me that the module was unsuccessful at getting the details about your version of Tower. Can you log into Tower as the same user that the Jenkins plugin is using and then navigate to /api/v2/ping and paste the results into this ticket? I do see an issue where the plugin does not "complain" if its unable to get a version from Tower. But the ping page should be open to all users of Tower so that really shouldn't happen.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.205283.1584626324000.10367.1584731820227%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Thanks for the stack trace, it looks like the plugin was unable to determine the version of Tower you are connecting to. Can you go to Jenkins => Manage Jenkins => Configure System. On this page find the Ansible Tower section and check the "Enable Debugging" option next to the Tower installation you are running. After thats enabled tail your Jenkins log file and run your Jenkins job again. In the log file you should see messages that begin with the string `[Ansible-Tower]` like: ``` [Ansible-Tower] Building GET request to https://10.0.1.24/api/v2/ping/ [Ansible-Tower] Forcing cert trust [Ansible-Tower] Request completed with (200) [Ansible-Tower] Ping page loaded [Ansible-Tower] Successfully got version 3.6.2 [Ansible-Tower] Connecting to Tower version: 3.6.2 ``` Please attach those first couple of lines so we can see if we are getting anything back. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.10225.1584715200118%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 We want to be using the latest version of the plugin. Are you getting a stack trace along with the Null Pointer Exception? If so, can you send that along? Also, are you referencing the credential by ID or by name? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.10213.1584712380097%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott commented on JENKINS-61586 Re: Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Could you please provide more details as to what is happening? Are you getting an error back from the plugin? Is your playbook throwing an error? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.205283.1584626324000.10196.1584710220148%40Atlassian.JIRA.
[JIRA] (JENKINS-60352) Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-60352 Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1 Change By: John Westcott Status: Resolved 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.203369.1575384648000.4828.1578495600588%40Atlassian.JIRA.
[JIRA] (JENKINS-48377) Job Tags don't pass to Ansible Tower/AWX
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48377 Job Tags don't pass to Ansible Tower/AWX Change By: John Westcott Status: Resolved 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.186972.151243328.4823.1578495540249%40Atlassian.JIRA.
[JIRA] (JENKINS-48377) Job Tags don't pass to Ansible Tower/AWX
Title: Message Title John Westcott resolved as Fixed Jenkins / JENKINS-48377 Job Tags don't pass to Ansible Tower/AWX Change By: John Westcott Status: In Progress Resolved Resolution: Fixed 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.186972.151243328.4820.1578495481083%40Atlassian.JIRA.
[JIRA] (JENKINS-48438) Workflow Templates with project sync or inventory update have incorrect links
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48438 Workflow Templates with project sync or inventory update have incorrect links Change By: John Westcott Status: Resolved 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.187037.1512671212000.4817.1578495481040%40Atlassian.JIRA.
[JIRA] (JENKINS-48663) Job Template execution getting 400 request
Title: Message Title John Westcott resolved as Fixed Jenkins / JENKINS-48663 Job Template execution getting 400 request Change By: John Westcott Status: Open Resolved Resolution: Fixed 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.187340.1513821798000.4812.1578495480827%40Atlassian.JIRA.
[JIRA] (JENKINS-48663) Job Template execution getting 400 request
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48663 Job Template execution getting 400 request Change By: John Westcott Status: Resolved 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.187340.1513821798000.4814.1578495480968%40Atlassian.JIRA.
[JIRA] (JENKINS-48835) Testing a connection results in "The item does not exist"
Title: Message Title John Westcott resolved as Fixed Jenkins / JENKINS-48835 Testing a connection results in "The item does not exist" Change By: John Westcott Status: Open Resolved Resolution: Fixed 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.187621.1515346312000.4807.1578495420783%40Atlassian.JIRA.
[JIRA] (JENKINS-49915) ansible-tower-plugin not passing extra variables
Title: Message Title John Westcott closed an issue as Not A Defect Jenkins / JENKINS-49915 ansible-tower-plugin not passing extra variables Change By: John Westcott Status: Resolved 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.188905.1520245664000.4804.1578495420728%40Atlassian.JIRA.
[JIRA] (JENKINS-48835) Testing a connection results in "The item does not exist"
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48835 Testing a connection results in "The item does not exist" Change By: John Westcott Status: Resolved 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.187621.1515346312000.4810.1578495420827%40Atlassian.JIRA.
[JIRA] (JENKINS-54341) Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-54341 Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5 Change By: John Westcott Status: Resolved 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.194994.1540896444000.4802.1578495361710%40Atlassian.JIRA.
[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-58725 Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending. Change By: John Westcott Status: Resolved 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.201018.1564479331000.4795.1578495240435%40Atlassian.JIRA.
[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-56300) New step or option that does not block on individual job completion
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-56300 New step or option that does not block on individual job completion Change By: John Westcott Status: Resolved 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.197880.1551226267000.4797.1578495240468%40Atlassian.JIRA.
[JIRA] (JENKINS-60352) Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott resolved as Fixed Please reopen the ticket if the latest release does not resolve this issue. Jenkins / JENKINS-60352 Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1 Change By: John Westcott Status: Open Resolved Resolution: Fixed Released As: 0.14.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) --
[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.
Title: Message Title John Westcott resolved as Fixed Please try v0.11.0 of the plugin. It will now attempt to cancel a job running in Tower if the Jenkins job is canceled. Jenkins / JENKINS-58725 Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending. Change By: John Westcott Status: Open Resolved Resolution: Fixed Released As: 0.11.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.
Title: Message Title John Westcott commented on JENKINS-58725 Re: Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending. I am either unable to replicate this problem or I am not understanding what is going on exactly in your case. When Jenkins executes a job on Tower is calling the Tower API and Tower will run the job asynchronously from Jenkins but Jenkins will wait for that job to complete before Jenkins moves on to the next step. If you are running two Jenkins jobs concurrently and they both call the same Tower instance as long as the Tower job is configured to run the job concurrently both Jenkins job should run in parallel. Is that what you are seeing as not working? If so can you confirm that your Tower job is correctly set for concurrent execution? Also, if you stop the Jenkins job any further jobs it would have run in Tower will not be run but the currently active Tower job will continue to run until Tower is complete. Are you looking for a feature where a cancelled job in Jenkins would attempt to cancel the Tower job? if so, I can look into the possibility of a feature like this. Also, for async jobs between Tower and Jenkins (i.e. having Jenkins not wait for a job to complete in Tower) this can now be done in the latest version of the plugin so long as your Jenkins job is a pipeline and not a freestyle job. See the "Async Execution" section on https://wiki.jenkins.io/display/JENKINS/Ansible+Tower+Plugin and let me know if that helps this situation at all. If none of this helps can you please try to describe further what is currently happening and what you expect to happen? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56300) New step or option that does not block on individual job completion
Title: Message Title John Westcott resolved as Fixed Please see the 0.10.0 version which now adds an async option to pipeline invocation. Examples of how to use this can be found on the plugin wiki: https://wiki.jenkins.io/display/JENKINS/Ansible+Tower+Plugin Jenkins / JENKINS-56300 New step or option that does not block on individual job completion Change By: John Westcott Status: Open Resolved Resolution: Fixed Released As: 0.10.0 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
[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.
Title: Message Title John Westcott assigned an issue to fen zhou You are seeing jobs in Tower which were launched by Jenkins stuck in a pending state? Can you add more details to this? i.e. what version of Tower are you on. What version of the plugin are you using? Also, can you manually invoke a job in Tower and get it past the pending state? The pending state in Tower means that the job was requested but its waiting to be scheduled (actually run) within the Tower cluster. Once the jobs is scheduled in Jenkins, nothing else is done on the Jenkins side other than monitor the job. Jobs getting stuck in a pending state would indicate (to me) that there is some kind of issue with your Tower installation. Jenkins / JENKINS-58725 Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending. Change By: John Westcott Assignee: John Westcott fen zhou 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
[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-55246) Add credential button is not working on Ansible Tower Plugin configuration
Title: Message Title John Westcott assigned an issue to Elyézer Rezende It looks like this is not an issue with the Ansible Tower plugin specifically as it appears to happen with other plugins. i.e. the gitlab plugin. Please do some testing and let me know if you agree that this may be a larger problem. Jenkins / JENKINS-55246 Add credential button is not working on Ansible Tower Plugin configuration Change By: John Westcott Assignee: John Westcott Elyézer Rezende 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.196329.1545157727000.2038.1565719806422%40Atlassian.JIRA.
[JIRA] (JENKINS-55028) Jenkins considers build as success even if tower plugin fails
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-55028 Jenkins considers build as success even if tower plugin fails Change By: John Westcott Status: Resolved Closed 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-54341) Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5
Title: Message Title John Westcott updated JENKINS-54341 Sorry for the delay, this issue should now be fixed in 0.9.1. Instead of using a version check to determine Token or Bearer we now using the same method as TowerCLI to better determine the correct course of action. If you find that 0.9.1 does not fix this issue please reopen the ticket. Jenkins / JENKINS-54341 Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5 Change By: John Westcott Status: Fixed but Unreleased Resolved Released As: 0.9.1 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-54341) Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5
Title: Message Title John Westcott updated JENKINS-54341 Jenkins / JENKINS-54341 Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54366) Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing
Title: Message Title John Westcott updated JENKINS-54366 Thanks for all of the comments and research on this issue. Since it appears to be an issue in Tower I am going to close this issue out. If you think we need to do more work on the plugin, please let me know and we can reopen the ticket. Jenkins / JENKINS-54366 Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing Change By: John Westcott Status: Fixed but Unreleased Closed Resolution: Fixed Not A Defect 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-54366) Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing
Title: Message Title John Westcott updated JENKINS-54366 Jenkins / JENKINS-54366 Ansible tower 3.3 with plugins 0.9 have issue in workflow extra variables passing 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54503) Ansible tower plugin 0.9.0 issue with Tower 3.3.1
Title: Message Title John Westcott updated JENKINS-54503 Jenkins / JENKINS-54503 Ansible tower plugin 0.9.0 issue with Tower 3.3.1 Change By: John Westcott Status: Fixed but Unreleased Closed 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-54503) Ansible tower plugin 0.9.0 issue with Tower 3.3.1
Title: Message Title John Westcott updated JENKINS-54503 This should be fixed in the 0.9.1 release, thanks for the contribution. Jenkins / JENKINS-54503 Ansible tower plugin 0.9.0 issue with Tower 3.3.1 Change By: John Westcott Status: Open Fixed but Unreleased Resolution: Fixed Released As: Completed 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-51009) Misleading version compatibility message on the plugin
Title: Message Title John Westcott resolved as Fixed Thanks for the code contribution. I've merged it in and released a 0.8.4. Once the wiki is working I'll update that with the new version. Jenkins / JENKINS-51009 Misleading version compatibility message on the plugin Change By: John Westcott Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-51009) Misleading version compatibility message on the plugin
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-51009 Misleading version compatibility message on the plugin Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48835) Testing a connection results in "The item does not exist"
Title: Message Title John Westcott commented on JENKINS-48835 Re: Testing a connection results in "The item does not exist" Filip Reimer you are correct about the API transforming the urls to end with a /. In Jenkins, when you add a / to the end of the URL Jenkins ends up making calls to Tower like https:api/v2/ping (note the double slash at the start of the path in the URL. This is why the test fails with the message "The item does not exist". I just released an 0.8.3 version of the plugin which will string the ending / of the URL so the plugin should now work with a url of https://towerserver.something.com/ or https://towerserver.something.com. It normally takes a couple hours for the new version of the plugin to propagate. If you get a chance can you test this change and let me know if its now working either way for you? Alexandr Suprunevich can you test the 0.8.3 version of the plugin and let me know if this change now remediates the issue you were having? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50370) Return Ansible Tower STDERR only
Title: Message Title John Westcott commented on JENKINS-50370 Re: Return Ansible Tower STDERR only To make sure I am understanding the request, you are running an Ansible Tower job which is failing and you want to access the reason for the failure in a subsequent step. Is that correct? If so, do you have the output from the Tower job displaying in the Build Log? If so, I am wondering if you could scrape the message out of the $BUILD_LOG variable? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50370) Return Ansible Tower STDERR only
Title: Message Title John Westcott assigned an issue to m t Jenkins / JENKINS-50370 Return Ansible Tower STDERR only Change By: John Westcott Assignee: John Westcott m t Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49915) ansible-tower-plugin not passing extra variables
Title: Message Title John Westcott commented on JENKINS-49915 Re: ansible-tower-plugin not passing extra variables Can you test the 0.8.2 to validate that the notes now indicate that prompt on launch is required for the settings to take affect? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50239) Template ID help button returns empty box
Title: Message Title John Westcott closed an issue as Fixed Thanks for the report, I've pushed a 0.8.2 version which now includes the message. Jenkins / JENKINS-50239 Template ID help button returns empty box Change By: John Westcott Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-50031) Ansible Tower 3.3 removes authtoken from API
Title: Message Title John Westcott closed an issue as Fixed Thanks for the confirmation. Jenkins / JENKINS-50031 Ansible Tower 3.3 removes authtoken from API Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50031) Ansible Tower 3.3 removes authtoken from API
Title: Message Title John Westcott updated JENKINS-50031 Jenkins / JENKINS-50031 Ansible Tower 3.3 removes authtoken from API Change By: John Westcott Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50031) Ansible Tower 3.3 removes authtoken from API
Title: Message Title John Westcott assigned an issue to Francois Herbert Francois, please try the 0.8.1 version of the plugin and let me know if it resolves this issue. Jenkins / JENKINS-50031 Ansible Tower 3.3 removes authtoken from API Change By: John Westcott Assignee: John Westcott Francois Herbert Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50031) Ansible Tower 3.3 removes authtoken from API
Title: Message Title John Westcott updated JENKINS-50031 Jenkins / JENKINS-50031 Ansible Tower 3.3 removes authtoken from API Change By: John Westcott Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50031) Ansible Tower 3.3 removes authtoken from API
Title: Message Title John Westcott started work on JENKINS-50031 Change By: John Westcott Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50031) Ansible Tower 3.3 removes authtoken from API
Title: Message Title John Westcott commented on JENKINS-50031 Re: Ansible Tower 3.3 removes authtoken from API Thanks for pointing this out. I will try to get a solution out as soon as possible. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49915) ansible-tower-plugin not passing extra variables
Title: Message Title John Westcott commented on JENKINS-49915 Re: ansible-tower-plugin not passing extra variables Thanks for the follow up. I'll add a task for indicating that in the help entries. In addition, there should be a message in the jenkins job logs like: [WARNING]: Extra variables defined but prompt for variables on launch is not set in tower job Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49915) ansible-tower-plugin not passing extra variables
Title: Message Title John Westcott commented on JENKINS-49915 Re: ansible-tower-plugin not passing extra variables Can you send the output from the Jenkins job run? Also, can you confirm that you have the extra vars "prompt on launch" box is checked in Ansible Tower? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49915) ansible-tower-plugin not passing extra variables
Title: Message Title John Westcott assigned an issue to m t Jenkins / JENKINS-49915 ansible-tower-plugin not passing extra variables Change By: John Westcott Assignee: John Westcott m t Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48654) Modify Ansible Tower Config to have a verbose option
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48654 Modify Ansible Tower Config to have a verbose option Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49109) Don't use Basic Auth on all requests
Title: Message Title John Westcott closed an issue as Fixed Fixed in 0.8.0 Jenkins / JENKINS-49109 Don't use Basic Auth on all requests Change By: John Westcott Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
