Hi John,

I did all above steps as per your response, getting like below.

 
HTTP 200 OKAllow: GET, HEAD, OPTIONS*Content-Type:* application/json*Vary:* Accept*X-API-Node:* awx-77996979f4-gbtkn*X-API-Time:* 0.011s{"ha": false,"version": "8.0.0.0","active_node": "awx-77996979f4-gbtkn","install_uuid": "f04571db-6ac8-4e9e-8e2f-7f7ceaa1c834","instances": [

],"instance_groups": [

]}
 

Hi John,

for NPE the main issue is with towerVersion variable .

I saw below comment on JENKINS-60352 issue 

This patch cause a NullPointerException (with AWX) because towerVersion attribute is apparently not properly filled.

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.

Hi John,

Thank you for the update ,please let me know once it is done.

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. 

If it is taking couple of days to download then how we can test it

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. 

I am not able to see 0.14.1 version in plugin page of Jenkins,
Do you have any idea how many days it will take,
Can I expect this version will handle machine credentials of ansible tower correctly

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

Hi John,

Thank you very much for your support, finally it successfully passing machine credentials from Jenkins job to ansible tower