1316117 - Remove "support" for try: -a by defaulting -b to none in buildbot

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

I had assumed that "try: -a" meant the same thing as "try: -b do -p all -u all -t <something>". However, it seems that it doesn't actually do anything for TaskCluster. I'm basing this on https://bugzilla.mozilla.org/show_bug.cgi?id=1272159#c8 and on the fact that I was backed out for Linux64 build bustage despite running try -a.

So at this point it seems that "try: -a" just runs a random collection of jobs. I think it should be removed so that other people don't get backed out for this reason. If you use "try: -a", you should get an error telling you to use a different syntax.

Comment 1

[Phil Ringnalda (:philor)]

See bug 1303663 comment 1 - actual support for -a was removed in 2011, and since then it has been just the defaults for each of -b/-p/-u/-t, the same as "try: garbage". Then, incomprehensibly making different incomprehensible decisions than buildbot's incomprehensible decisions, taskcluster chose to have defaults for -p/-u/-t, but no default for -b.

And an error message is not an option, the only option is to get nothing at all run, ask why, be told that it was a result of using something that hasn't been supported since 2011.

Comment 2

[Phil Ringnalda (:philor)]

Attachment: Fix

Chances are this probably works.

Comment 3

[Phil Ringnalda (:philor)]

Comment on attachment 8816738 [details] [diff] [review]
Fix

https://hg.mozilla.org/build/buildbotcustom/rev/29c538e1ab2a284956415f9956de7d450995ff45