Currently the autobuilder has one step "run-config" which runs multiple different steps internally. These go to different log files with confusing names like "step2d". The reason is we can't know in advance how many steps a given target on the autobuilder will have in a given release. From buildbot irc: (15:40:01) aakashja_: RP: they definitely can be added dynamically at execution time based on the data from worker. We do that in WebKit. (15:40:48) aakashja_: RP: for example in https://trac.webkit.org/browser/webkit/trunk/Tools/BuildSlaveSupport/ews-build/steps.py#L113 if the CheckOutSource fails, we invoke CleanUpGitIndexLock build-step. Aaeriele aakashja_ (16:22:44) RP: aakashja_: addStepsAfterCurrentStep sounds promising, an example really helps, thanks! (16:46:22) aakashja_: RP: this is how that dynamic step look like in buildbot build: https://ews-build.webkit.org/#/builders/4/builds/2570 so we should be able to have a step query how many steps a given build run has, then dynamically create them with addStepsAfterCurrentStep(). Bonus marks for creating human readable names for the steps (we could add this to config.json if there were a good way to display it which there now is). The benefit of doing this would be more understandable logs for users which would show individual execution times and warnings/errors.
Updated link https://trac.webkit.org/browser/webkit/trunk/Tools/CISupport/ews-build/steps.py
http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder2/commit/?id=25d5a7d0aec3d24c8247c93b2e4ab704445dd75a