Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-49915

ansible-tower-plugin not passing extra variables

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Trivial Trivial
    • ansible-tower-plugin
    • None
    • Jenkins ver. 2.109
      Ansible Tower Plugin 0.8.0

      Ansible Tower 3.2.1
      Ansible 2.5.0rc1

      The extra variables from Jenkins job are not being passed to Ansible Tower. Tried both Yaml and Json format for extra variables without success.

      Please see the screen shots attached.

        1. jenkins-tower-plugin-tower-job.PNG
          jenkins-tower-plugin-tower-job.PNG
          23 kB
        2. jenkins-tower-plugin-json.PNG
          jenkins-tower-plugin-json.PNG
          14 kB

          [JENKINS-49915] ansible-tower-plugin not passing extra variables

          m t created issue -
          m t made changes -
          Attachment New: jenkins-tower-plugin-json.PNG [ 41725 ]
          Attachment New: jenkins-tower-plugin-tower-job.PNG [ 41726 ]

          John Westcott added a comment -

          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?

          John Westcott added a comment - 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?
          John Westcott made changes -
          Assignee Original: John Westcott [ johnwestcottiv ] New: m t [ mmt ]
          m t made changes -
          Priority Original: Major [ 3 ] New: Trivial [ 5 ]
          m t made changes -
          Comment [ [~johnwestcottiv] thanks for quick reply. Seems that this was a user error. I was not aware that the extra vars "prompt on launch" box needs to checked in Ansible Tower in order to pass the vars via API.

          It may be a good idea to add that information into the "help ((?))" field in the plugin's job box. ]

          m t added a comment -

          johnwestcottiv thanks for quick reply. Seems that this was a user error. I was not aware that the extra vars "prompt on launch" box needs to checked in Ansible Tower in order to pass the vars via API.

          It may be a good idea to add that information into the "help ( )" field in the plugin's job box.

          m t added a comment - johnwestcottiv  thanks for quick reply. Seems that this was a user error. I was not aware that the extra vars "prompt on launch" box needs to checked in Ansible Tower in order to pass the vars via API. It may be a good idea to add that information into the "help ( )" field in the plugin's job box.
          m t made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          John Westcott added a comment -

          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

          John Westcott added a comment - 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

          John Westcott added a comment -

          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?

          John Westcott added a comment - 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?

            mmt m t
            mmt m t
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: