GitLab

Using per-milestone buckets caused the scheduler jobs names to have the
bucket name prefixed to them when the number of jobs for a builder with
a given name was >1. To account for this, the bucketed_triggers property
modified the behavior of the chromium recipe to prefix the builder name
with the bucket name to trigger the appropriate builder. A generator
ensured that builders in the ci bucket could be triggered with or
without the bucket prefix so that when new branch builders were added,
outstanding builds wouldn't infra fail attempting to trigger a scheduler
job that no longer existed.

With milestone-based buckets removed, neither of these things is
necessary.

Change-Id: I479d1bcb56908e677f59dfa5b4b8a2394c8ada6e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2458451
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: Erik Staab <estaab@chromium.org>
Commit-Queue: Erik Staab <estaab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#814828}