Issue 671844 link

Starred by 1 user

Issue metadata

Status:	Archived
Owner:	dgarr...@chromium.org
Closed:	Jan 2017
Cc:	█ nxia@chromium.org
Components:	Infra>Client>ChromeOS
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	2
Type:	Bug
VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

Use Milo links to Trybot builds when scheduling tryjobs.

Project Member Reported by dgarr...@chromium.org, Dec 7 2016

Issue description

We currently use links to buildbot when linking to PreCQ buildslaves as we annotate CLs. We should use Milo links instead.

Here is a somewhat related CL:

https://chromium-review.googlesource.com/#/c/411513/6

Example annotation today:

Tryjob submitted!
Go to https://uberchromegw.corp.google.com/i/chromiumos.tryserver/waterfall?committer=dgarrett@google.com&builder=paladin to view the status of your job.

Comment 1 by dgarr...@chromium.org, Dec 7 2016

It has been suggested that if we start embedding a unique id in each PreCQ buildbucket request (or the requestors ID), we can us that to link to a build-status page like:

https://cros-build-status.appspot.com/builds/query?bucket=master.chromeos&tag=buildset:$LATEST_PALADIN_BUILD&titletag=cbb_config&sorttag=cbb_config&bucket=master.chromiumos.tryserver&max=20

Comment 2 by dgarr...@chromium.org, Dec 7 2016

The relevant code to generate the link can be found here:

https://cs.corp.google.com/chromeos_public/chromite/cbuildbot/remote_try.py?rcl=10d9055ee399ed14c74dc483436ae0f9f5e0138f&l=329