873273 - mozharness action groups

Status: RESOLVED WONTFIX

(Release Engineering :: Applications: MozharnessCore, defect, P5)

Description

[Aki Sasaki (not active)]

For the beagle script, I'm considering creating a meta-action, --update-loop, which will call the actions --update-stage-mirror --update-work-mirror --push --upload --notify.

I can do this by adding update-loop as a non-default action, and defining it as a method that calls the other action methods, possibly with self.info()s that describe what I'm doing.

However, this will show up in the action list the same as the other actions, and it's quite possible to run all actions, which would run this loop twice (once by the individual actions, once by this meta action).

I could also do away with the individual actions entirely, and clump it all together in a single action/method.  But this gets rid of some granular testing/troubleshooting niceness.

To allow for meta-actions, I could change the actions list to allow for a list of dictionaries.  That way I could add meta-data, e.g. --help information or |"meta_action": True|, which might behave differently.

Eventually we could even list which actions are collected under this meta-action, and have default behavior without forcing you to define a new method (self.update_loop() in this example).


This could make various scripts a lot nicer, e.g. |script --setup| then |script --run-tests|, where setup is a meta-action.  I imagine |script --setup --no-clobber| would still have to work.