2 Commits (9af7d107ded91d27ef44b67bb94adc9c3b1010c2)

Author	SHA1	Message	Date
Nodir Turakulov	efc95d6b9a	[bot_update] Untie revision and repository properties ... repository and revision have less to do with each other than it seems: revision is for checkout and the part of code that reads revision does not read repository. repository property is used to determine what to apply the patchset to. When initializing their values from buildbucket.build.input, do it separately. Also, initialize repository from Gerrit changes, not Gitiles commit. See also https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1199854 https://chromium-review.googlesource.com/c/infra/luci/recipes-py/+/1199856 Bug: 877161, 694348 Change-Id: I4907a31ce055a3526b15f1a3c8e8f15c2c831437 Reviewed-on: https://chromium-review.googlesource.com/1200065 Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org>	7 years ago
Andrii Shyshkalov	5484b866dc	bot_update: use buildbucket's gitiles_commit as repo/revision input. ... Today, whenever LUCI scheduler sets gitiles_commit, a revision property is also always set, thus this CL will have no effect on today's production. The goal of CL is to pave the way to avoid this duplication. For starters, one could start real writing tests with + api.buildbucket.ci_build(..., revision='sha1') without the need to duplicate the same revision as a property. All recipes which WAI with such input are thus ready to work w/o 'revision' property. After that, we'll be able to stop the duplication in LUCI scheduler. R=hinoka Recipe-Nontrivial-Roll: infra Recipe-Nontrivial-Roll: build Change-Id: I1773b1c3d2a98a9dbd1cfdd9ac2b4fb99745ee99 Reviewed-on: https://chromium-review.googlesource.com/1123713 Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org> Reviewed-by: Ryan Tseng <hinoka@chromium.org>	7 years ago