[luci.chromium.try] define mastername property

recipes depend on mastername property. Specify it in builders.

Remove mastername=luci.chromium.try. Nothing expects mastername to be that.

R=tandrii@chromium.org, estaab@chromium.org

Bug:
Change-Id: I9b792100f8cdd114af33e7abc27463ac6e8a5e22
No-Presubmit: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/677044
Commit-Queue: Nodir Turakulov <nodir@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
1 file changed
tree: 14e94b52bd00dd0f03910a8d45fce1f10aceacb7
  1. OWNERS
  2. README.md
  3. codereview.settings
  4. cr-buildbucket-dev.cfg
  5. cr-buildbucket.cfg
  6. luci-logdog-dev.cfg
  7. luci-logdog.cfg
  8. project.cfg
README.md

infra/config branch

This branch contains chromium project-wide configurations for chrome-infra services. For example, cr-buildbucket.cfg defines builders.

Making changes

It is recommended to have a separate checkout for this branch, so switching to/from this branch does not populate/delete all files in the master branch.

Initial setup:

mkdir config
cd config
git init
git remote add origin https://chromium.googlesource.com/chromium/src
git fetch origin infra/config
git reset --hard origin/infra/config
git config depot-tools.upstream origin/infra/config

Now you can create a new branch to make changes:

git new-branch add-new-builder
# edit cr-buildbucket.cfg
git commit -a
git cl upload