I think that it's also important to be as close as we can from the official bots on this tryserver. This will mean that we'll need to run the official_[upload|signing|symbols] script to make sure that everything works fine. 

Agreed, we should run as much of the process as we can.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build/+/d7d0c757a49923b8c30d6e9f240cd310627b2a92

commit d7d0c757a49923b8c30d6e9f240cd310627b2a92
Author: dimu <dimu@google.com>
Date: Fri Feb 24 00:23:22 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build/+/2cac68e3b61da723d3dd37408a9ac0724ef10f9d

commit 2cac68e3b61da723d3dd37408a9ac0724ef10f9d
Author: dimu <dimu@google.com>
Date: Mon Feb 27 19:20:16 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/release/scripts/+/b38561d9cbe9f4929d8eedd5be557b11b89b8739

commit b38561d9cbe9f4929d8eedd5be557b11b89b8739
Author: dimu <dimu@google.com>
Date: Thu Mar 16 18:22:44 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build/+/c6d6e656c0ddf870986b3316119cfff31436d8ba

commit c6d6e656c0ddf870986b3316119cfff31436d8ba
Author: dimu <dimu@google.com>
Date: Tue Mar 21 22:15:03 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build/+/2ebb518e244dfc2a4356193f4905dd582113bb1a

commit 2ebb518e244dfc2a4356193f4905dd582113bb1a
Author: dimu <dimu@google.com>
Date: Wed Mar 22 18:10:57 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build/+/3d1cce5bf6ad50624d88938d1537b4f723923b30

commit 3d1cce5bf6ad50624d88938d1537b4f723923b30
Author: dimu <dimu@google.com>
Date: Wed Mar 29 22:59:11 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infradata/master-manager/+/8b024adb21dfa244ed87d148426a4d99608d9fe4

commit 8b024adb21dfa244ed87d148426a4d99608d9fe4
Author: dimu <dimu@google.com>
Date: Fri Mar 31 22:40:09 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/release/scripts/+/4bd5a06ceda074b75109853ac56c5bd907f68d2f

commit 4bd5a06ceda074b75109853ac56c5bd907f68d2f
Author: dimu <dimu@google.com>
Date: Wed May 03 23:10:17 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/release/scripts/+/4bd5a06ceda074b75109853ac56c5bd907f68d2f

commit 4bd5a06ceda074b75109853ac56c5bd907f68d2f
Author: dimu <dimu@google.com>
Date: Wed May 03 23:10:17 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/release/scripts/+/68f99118f85cd7ebd6efbefd55283d452f022db1

commit 68f99118f85cd7ebd6efbefd55283d452f022db1
Author: dimu <dimu@google.com>
Date: Thu Jun 15 17:54:45 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/a8eefb0f864bc20a19cbe794120a6e3e9dd61d08

commit a8eefb0f864bc20a19cbe794120a6e3e9dd61d08
Author: dimu <dimu@google.com>
Date: Fri Jun 30 03:48:50 2017

Enable Kitchen on internal.official.tryserver

R=dnj, iannucci

Bug:663061
Change-Id: Iad399c05b3f90ecd3ec2a75c4346377b203811a1
Reviewed-on: https://chromium-review.googlesource.com/557283
Reviewed-by: Daniel Jacques <dnj@chromium.org>
Commit-Queue: Di Mu <dimu@chromium.org>

[modify] https://crrev.com/a8eefb0f864bc20a19cbe794120a6e3e9dd61d08/scripts/slave/remote_run.py

dpranke@, can you summarize our current thinking on this? Are we willing to forego full internal tryservers and just have public branch builders[1], which should catch the vast majority of branch issues, but without the complications of failures/rejections that public contributors might not be able to see (I feel like there was actually another bug about doing exactly that, maybe from +amineer, but I can't find it right now).


[1] Once we have the public branches as the branch source-of-truth, as in Issue 773935

Actually, your  Issue 773936  might be the other bug I'm thinking of. Should this just dupe into that?

assigning to dpranke to decide if this should merge with  Issue 773936 

 Issue 773936  has been merged into this issue.

Yes, that bug was effectively a dup of this.

To answer the question in #c21, yes, we should have public builders at the very least, and then eventually if we can, also have private/official builders.

Thanks. Assigning to me, at least for first step of getting to public branch builders, which is included in the plan for migrating branch source-of-truth from buildspecs to the source repos (Issue 773935).

Linked to  Issue 859822  to point out an example where trybots for the official builds would have prevented regressions from being introduced on a branch due to merge-backs.

No longer on the Chrome team, e-mail me @google.com if any attention still required from me here, otherwise good luck!

Issue 331156 has been merged into this issue.