Ian Campbell writes ("[PATCH OSSTEST] cs-adjust-flight: Add job-rename command 
which applies a perlop to job names"):
> My intention was to allow creation of adhoc jobs based on a template
> but modified e.g. to enable/disable XSM with a sequence something
> like:
> 
> ./cs-adjust-flight $flight copy-jobs $template test-foo-xsm
> ./cs-adjust-flight $flight rename-job test-foo-xsm 's/-xsm$//'
> ./cs-adjust-flight $flight runvar-set $job enable_xsm false
> ./cs-adjust-flight ... update %buildjob
> 
> Signed-off-by: Ian Campbell <ian.campb...@citrix.com>

Acked-by: Ian Jackson <ian.jack...@eu.citrix.com>

Although maybe it should be called `jobs-rename' by analogy with the
other modifiers ?

Arguably job-status should be renamed too.  But arguably it ought not
since when it is used to print the status of several jobs its output
is different (and necessarily fiddlier).

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to