Yeah, I think I heard about --start-at-task, but unfortunately I'm not sure 
if there's any way to implement that in a Tower job template.  Here's a 
screenshot of what the job template UI looks like:

<https://lh3.googleusercontent.com/-6k5Hy4EPWnk/V2vvv9qTw1I/AAAAAAAABhw/e9anxP_9bbckAAtTGyhcwiNY35PYTKl9wCLcB/s1600/JobTemplate.PNG>


On Thursday, June 23, 2016 at 3:49:29 AM UTC-4, J Hawkesworth wrote:
>
> Sounds like you might need --start-at-task see 
> http://docs.ansible.com/ansible/playbooks_startnstep.html
> It's been a while since I looked at the Tower ui but I think its an option 
> on the each job from what I remember.
>
> Hope this helps,
>
> Jon
>
> On Thursday, June 23, 2016 at 12:49:29 AM UTC+1, mgoldsb wrote:
>>
>> Hi.  I'm trying to implement an ad-hoc "restart" functionality in Ansible 
>> Tower similar to what is in the core Ansible CLI.  My idea is that, if a 
>> deployment fails, I can restart it at the tag that it failed at--however, 
>> if I specify this tag in the deployment, it will ONLY run that tag.  I am 
>> looking for a way such the deployment will *start* running at that specific 
>> tag and then continue to all of the subsequent tasks.
>>
>> I can see one potential method whereby tags are added sequentially with 
>> each task.  For instance,
>>
>>  * - name: First task*
>> *            shell: echo "Kilroy Was Here" > /home/mgoldsb/Hello.txt*
>> *            failed_when: "{{ First }} == true"*
>> *            tags:*
>> *              - First_Task*
>>                 
>> *          - name: Second task*
>> *            shell: echo "Kilroy Was Here" > /home/mgoldsb/World.txt*
>> *            failed_when: "{{ Second }} == true"*
>> *            tags:*
>> *              - First_Task*
>> *              - Second_Task*
>>                 
>> *          - name: Third task*
>> *            #shell: echo "Kilroy Was Here" > /home/mgoldsb/Hows.txt*
>> *            shell: rm -f testthis.txt*
>> *            failed_when: "{{ Third }} == true"*
>>
>> *            tags:              - First_Task*
>> *              - Second_Task*
>> *              - Third_Task*
>>                 
>> *          - name: Fourth task*
>> *            shell: echo "Kilroy Was Here" > /home/mgoldsb/It.txt*
>> *            failed_when: "{{ Fourth }} == true"*
>>
>> *            tags:              - First_Task*
>> *              - Second_Task*
>> *              - Third_Task*
>> *              - Fourth_Task*
>>                 
>> *          - name: Fifth task*
>> *            shell: echo "Kilroy Was Here" > /home/mgoldsb/Going.txt*
>> *            failed_when: "{{ Fifth }} == true"*
>>
>> *            tags:              - First_Task*
>> *              - Second_Task*
>> *              - Third_Task*
>> *              - Fourth_Task*
>> *              - First_Task*
>>
>> However, I would much rather prefer only having a single tag for each 
>> task that uniquely refers to that task.
>>
>> Can anyone offer any suggestions?
>>
>> Thanks in advance.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/34dd6637-04e9-4e80-b0cf-0d7ead2caad2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to