New issue
Advanced search Search tips

Issue 896014 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature



Sign in to add a comment

LUCI Scheduler: Trigger build based on checkin to any git repo in manifest per branch.

Project Member Reported by dgarr...@chromium.org, Oct 16

Issue description

We have an increasing desire to be able to trigger builds based on a checkin to any git repo in a repo manifest on a given branch.

Buildbot had this feature, so losing it is a regression. Buildbot used an external builder which would check for the changes. It's still running here:

https://uberchromegw.corp.google.com/i/chromeos.infra/builders/CrOS%20Repo%20Sync

 
Did buildbot support this natively?

You can migrate CrOS Repo Sync builder to LUCI and trigger LUCI builds via https://chromium.googlesource.com/infra/luci/recipes-py/+/master/recipe_modules/scheduler/api.py#120
That would be a totally acceptable solution from my point of view.

I'm not sure owns that builder now. dnj@ built it originally, and there appear to be a number of projects using it (not just ChromeOS).

+1 to what Vadim wrote in #2. But, since recipe today outsources triggering to the same python script that computes manifest changes, thus this script would instead need to output which bots to trigger in its output json. Then, you can use proposed solution by Vadim.

ownership-wise, it was considered CrOS specific and it even lives in CrOS repo :)

So, luci-scheduler wise, this is WontFix. But maybe move this bug to CrOS component?
Alright.

Note.... who would we break if we shutdown the current builder? Not that we are ready for that.
I have absolutely no idea who will get broken. Recipe itself doesn't say it.

However, since we are migrating everyone off buildbot, we'll discover all those who care.
Status: Available (was: Untriaged)
Components: -Infra>Platform>Scheduler Infra>Client>ChromeOS>CI
Status: Untriaged (was: Available)
Updated wrong bug, sorry :)

Tentatively putting under Infra>Client>ChromeOS>CI as per #3.

Sign in to add a comment