Split swarm_triggered into 3 builders to make it easier on devs.

Split swarm_triggered into 3 builders to make it easier on devs.

Stop hardcoding swarm_triggered.

The 3 builders do the exact same thing, but it is easier for devs to know
where the test run.

R=xusydoc@chromium.org
BUG=

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=229414

[M-A Ruel, 2013-09-25 18:28:38]

It also have https://codereview.chromium.org/24633002 that is the CQ part, the
CQ will have to have its CL committed and the CQ restarted with internal state
cleared when the TS is restarted with this CL in.

[Mike Stip (use stip instead), 2013-09-26 01:03:05]

lgtm

https://chromiumcodereview.appspot.com/24565004/diff/1/scripts/master/factory...
File scripts/master/factory/swarm_factory.py (right):

https://chromiumcodereview.appspot.com/24565004/diff/1/scripts/master/factory...
scripts/master/factory/swarm_factory.py:13: - One SwarmTestBuilder() builder
named something like 'swarm_triggered'. It is
probably want to say 'named something like linux_swarm_triggered' right?

[M-A Ruel, 2013-10-18 14:38:00]

+today's trooper

I changed the CL to not delete swarm_triggered, so the transition will be
smoother, since the builds that ran on it won't be deleted.

The CQ is currently not using swarm_triggered to also ease the transition, so no
simultaneous CQ restart is needed.

[commit-bot: I haz the power, 2013-10-18 14:38:14]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/maruel@chromium.org/24565004/107001

[commit-bot: I haz the power, 2013-10-18 14:39:20]

Change committed as 229414