Commit c9c0c4a1 authored by Eric Foo's avatar Eric Foo Committed by Commit Bot

Update section on how to know build was run on LUCI

Change-Id: I80a812501aeb3c4d894d687326dac3777b2f54c5
Reviewed-on: https://chromium-review.googlesource.com/c/1318587Reviewed-by: default avatarRyan Tseng <hinoka@chromium.org>
Commit-Queue: Eric Foo <efoo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605596}
parent 1485506b
docs/images/LUCI-CodeReview-Tag.png

7.79 KB | W: | H:

docs/images/LUCI-CodeReview-Tag.png

33.8 KB | W: | H:

docs/images/LUCI-CodeReview-Tag.png
docs/images/LUCI-CodeReview-Tag.png
docs/images/LUCI-CodeReview-Tag.png
docs/images/LUCI-CodeReview-Tag.png
  • 2-up
  • Swipe
  • Onion skin
...@@ -33,7 +33,7 @@ ensure correctness and performance. Note that times can vary per builder set.* ...@@ -33,7 +33,7 @@ ensure correctness and performance. Note that times can vary per builder set.*
### **Who is involved with the builder migrations?** ### **Who is involved with the builder migrations?**
*We have created a LUCI migration task force *We have created a LUCI migration task force
([infra-dev@chromium.org](mailto:infra-dev@chromium.org)) comprised of Chrome ([infra-dev@chromium.org](mailto:infra-dev@chromium.org)) comprised of Chrome
Operations developers. Owners of Chromium builders are responsible for approvals Operations developers. Owners of Chromium builders are responsible for approvals
for final go ahead to switch a LUCI builder to production.* for final go ahead to switch a LUCI builder to production.*
...@@ -52,8 +52,8 @@ and CI systems effectively.* ...@@ -52,8 +52,8 @@ and CI systems effectively.*
### **What limitations does the migration have?** ### **What limitations does the migration have?**
*While we're working to make the transition as seamless as possible, there can *While we're working to make the transition as seamless as possible, there can
be a few hiccups that may occur when a builder is migrated. Below are the be a few hiccups that may occur when a builder is migrated. Below are the
known limitations:* known limitations:*
* *The blamelist will not be calculated correctly between the first LUCI build * *The blamelist will not be calculated correctly between the first LUCI build
...@@ -90,16 +90,16 @@ main differences to expect are:* ...@@ -90,16 +90,16 @@ main differences to expect are:*
starts with `/p/chromium/builders/…` starts with `/p/chromium/builders/…`
If the build is still running on Buildbot, If the build is still running on Buildbot,
"buildbot" will still be part of the URL path. Also, in "buildbot" will still be part of the URL path. Also, in
the Code Review UI, try-builders running on LUCI are the Code Review UI, try-builders on Buildbot is shown
shown with a LUCI tag as shown below.* with a "Buildbot" tag. The default with no tag represents
a LUCI build.*
![LUCI Code Review UI Tag](images/LUCI-CodeReview-Tag.png ![LUCI Code Review UI Tag](images/LUCI-CodeReview-Tag.png)
"linux%5chromium%5rel%5ng is a LUCI builder")
*In some cases, builds on LUCI can also have the *In some cases, builds on LUCI can also have the
following URL following URL
`ci.chromium.org/p/chromium/builds/b<buildbucket_build_id>`. `ci.chromium.org/p/chromium/builds/b<buildbucket_build_id>`.
This occurs when the build does not have a build number This occurs when the build does not have a build number
which should not occur for any Chromium build* which should not occur for any Chromium build*
### **When will Buildbot be turned down?** ### **When will Buildbot be turned down?**
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment