migration app: run analysis iff builder is not prod |
||||||
Issue descriptionNow we allow task force to close bugs themselves: bug 821257 Update migration app to skip analysis of a "LUCI is prod" builder. On the builder page, do not render red bold "outdated" if the builder is "luci is prod".
,
Mar 20 2018
,
Mar 22 2018
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/98146523f4fcf7b1890dbbda05477299b760c5f7 commit 98146523f4fcf7b1890dbbda05477299b760c5f7 Author: Nodir Turakulov <nodir@google.com> Date: Thu Mar 22 19:36:16 2018 [monorail] add GetIssue RPC Add GetIssue RPC to Monorail client. Bug: 823541 Change-Id: I231de09d9e71d197d94d075b3b5835380391cfc6 Reviewed-on: https://chromium-review.googlesource.com/972149 Commit-Queue: Nodir Turakulov <nodir@chromium.org> Reviewed-by: Jao-ke Chin-Lee <jchinlee@chromium.org> [modify] https://crrev.com/98146523f4fcf7b1890dbbda05477299b760c5f7/go/src/infra/monorail/monorailtest/server.go [modify] https://crrev.com/98146523f4fcf7b1890dbbda05477299b760c5f7/go/src/infra/appengine/cr-audit-commits/app/test_utils.go [modify] https://crrev.com/98146523f4fcf7b1890dbbda05477299b760c5f7/go/src/infra/monorail/endpoints.go [add] https://crrev.com/98146523f4fcf7b1890dbbda05477299b760c5f7/go/src/infra/monorail/monorail.mock.pb.go [modify] https://crrev.com/98146523f4fcf7b1890dbbda05477299b760c5f7/go/src/infra/monorail/monorail.pb.go [modify] https://crrev.com/98146523f4fcf7b1890dbbda05477299b760c5f7/go/src/infra/monorail/monorailtest/client.go [modify] https://crrev.com/98146523f4fcf7b1890dbbda05477299b760c5f7/go/src/infra/monorail/monorail.infra_testing [modify] https://crrev.com/98146523f4fcf7b1890dbbda05477299b760c5f7/go/src/infra/monorail/monorail.proto [modify] https://crrev.com/98146523f4fcf7b1890dbbda05477299b760c5f7/go/src/infra/monorail/pb.discovery.go
,
Apr 17 2018
Did we decide to stop analyzing a builder bug is closed? was there any progress?
,
Apr 17 2018
Under previous discussion, this is actually a WontFix, because the migration app and bug state communicate two separate pieces of information (whether LUCI builds are prod and whether Buildbot machines are decommissioned, etc.). This means that taskforce members should communicate them separately at the relevant times by marking LUCI-is-Prod, and closing the bug, respectively. Has any part of this changed such that we again now wish to sync the migration app state with the bug state? I still have the cleanup CL active and can land that; it doesn't affect taskforce workflow and hence is not time-sensitive.
,
Apr 17 2018
,
Apr 17 2018
ah thanks for helping me recalling what we want. You are totally right. Let me repurpose this bug.
,
Apr 27 2018
,
Jun 15 2018
,
Jun 15 2018
Jao-ke/Nodir, can you detail what the remaining work on this?
,
Jun 27 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by efoo@chromium.org
, Mar 20 2018