It's a handy way to implement cleanup actions, such as de-provisioning a duffy machine regardless of whether or not a job succeeds.
I'm already using this for several jobs, exactly for the use case of cleaning up nodes and collecting nodes.
Is it not working for you ? Is post-tasks the same thing ?
This is what it looks like in a Jenkins Job Builder template: https://github.com/rdo-infra/ci-config/blob/master/jenkins/jobs/weirdo-defau...
David Moreau Simard Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter] It's a handy way to implement cleanup actions, such as de-provisioning a duffy machine regardless of whether or not a job succeeds. _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
On Fri, May 13, 2016, at 06:20 PM, David Moreau Simard wrote:
I'm already using this for several jobs, exactly for the use case of cleaning up nodes and collecting nodes. Is it not working for you ? Is post-tasks the same thing ?
Looks like that's a different plugin, but indeed seems pretty close. I actually ended up using:
``` publishers: - trigger-parameterized-builds: ```
Which is installed now, because I wanted to serialize around a single cleanup builder for duffy. I'lll post more about this later.
Thanks though for the link to your JJB - it's really useful to see what other people are doing in this area. What I'm working on now is in: https://github.com/cgwalters/sig-atomic-buildscripts/tree/pr-testing/centos-... for those interested.
-
Colin Walters -
David Moreau Simard