+hinoka@ any ideas what happened here?

+estaab@ because this should be a blocker to migrate infra/infra to swarming.

I will figure it out

FYI, if you want re-trigger CQ, just remove and vote again for CQ label dry run (+1).

buildbot version passes in:
--gerrit_repo https://chromium.googlesource.com/infra/infra --gerrit_ref refs/changes/11/338811/5

luci one doesn't.  the recipe never told bot update to apply any patches.

testing on https://chromium-review.googlesource.com/c/355222/

ok, so the problem is that bot_update recipe module relies on "repository" property which is derived from "changes" build parameters by buildbot.
Perhaps swarmbucket should do the same: pass repo_url of the first change in the "changes" build parameter and copy it to property...

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra.git/+/2abc127a23b679305433bd629942e0131b4c35ee

commit 2abc127a23b679305433bd629942e0131b4c35ee
Author: nodir <nodir@chromium.org>
Date: Fri Jun 24 00:52:31 2016

swarmbucket: support for repository property

add native support for repository build property, see a long comment
about it in code

R=vadimsh@chromium.org, tandrii@chromium.org
BUG= 617472 

Review-Url: https://codereview.chromium.org/2090343006

[modify] https://crrev.com/2abc127a23b679305433bd629942e0131b4c35ee/appengine/cr-buildbucket/swarming/swarming.py
[modify] https://crrev.com/2abc127a23b679305433bd629942e0131b4c35ee/appengine/cr-buildbucket/swarming/test/swarming_test.py

https://luci-milo.appspot.com/swarming/prod/2f98c7bf11802310