Excerpts from Nick Coghlan's message of 2014-11-10 15:27 +10:00:
It occurred to me today that with the server side reservation system
added in 0.17, that actually becomes something that could be made
configurable for a previously submitted recipe.
The kinds of cases where that seemed potentially interesting to me were:
* After manually kicking a recipe that stalled for some reason (the case
that prompted the idea)
* After noticing something odd in the execution of a long running recipe
* Switching from "always" to "only on failure" if you forget to make
conditional (or vice-versa)
* Adding or removing the reservation request if simply made a mistake at
Yes, this sounds quite useful. These are all common use cases.
There'd be a bit fiddling involved - new CLI commands to manage
web UI elements on the job details page.
If we did it at all, perhaps it would be best left until after the
results page redesign?
Yes that would be the best time to add it -- during or after.
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Hosted & Shared Services
Red Hat, Inc.