[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-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 discussio
[JIRA] (JENKINS-56300) New step or option that does not block on individual job completion
Title: Message Title Thomas Cooper updated an issue Jenkins / JENKINS-56300 New step or option that does not block on individual job completion Change By: Thomas Cooper Priority: Major Minor 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-56300) New step or option that does not block on individual job completion
Title: Message Title
Thomas Cooper updated an issue
Jenkins / JENKINS-56300
New step or option that does not block on individual job completion
Change By:
Thomas Cooper
Using Ansible Tower in a pipeline, there is no way to trigger multiple Tower jobs to be run concurrently then poll each for completion status. I'd like some sort of option on the ansibleTower step that prevents the AnsibleTowerRunner from blocking on job completion before continuing. This might warrant a separate step. Below is my use case: {noformat}script { def myapps = [...] def jobs = myapps.collect {ansibleTower( jobTemplate: 'deploy-one-app', extraVars: "---\napp_to_deploy: ${it}", throwExceptionWhenFail: false, waitForCompletion: false) // return Job ID? } timeout(10) {waitUntil { jobs.every { def job = ansibleTowerJob(id: it )job . JOB_RESULT status == " SUCCESS successful " }} }}{noformat}
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-56300) New step or option that does not block on individual job completion
Title: Message Title
Thomas Cooper created an issue
Jenkins / JENKINS-56300
New step or option that does not block on individual job completion
Issue Type:
Improvement
Assignee:
John Westcott
Components:
ansible-tower-plugin
Created:
2019-02-27 00:11
Labels:
plugin
Priority:
Major
Reporter:
Thomas Cooper
Using Ansible Tower in a pipeline, there is no way to trigger multiple Tower jobs to be run concurrently then poll each for completion status. I'd like some sort of option on the ansibleTower step that prevents the AnsibleTowerRunner from blocking on job completion before continuing. This might warrant a separate step. Below is my use case:
script {
def myapps = [...]
def jobs = myapps.collect {
ansibleTower(
jobTemplate: 'deploy-one-app',
extraVars: "---\napp_to_deploy: ${it}",
throwExceptionWhenFail: false,
waitForCompletion: false
)
}
timeout(10) {
waitUntil {
jobs.every {
it.JOB_RESULT == "SUCCESS"
}
}
}
}
