New issue
Advanced search Search tips

Issue 806055 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 810414



Sign in to add a comment

Bisect - Migrate to LUCI?

Project Member Reported by simonhatch@chromium.org, Jan 25 2018

Issue description

Public bots are all on Pinpoint, but the internal bots needs to be supported until they're migrated. See if we need to do anything for this luci migration.
 
So word from infra people is that we don't need to think much about this migration just yet. There's a few small tasks we can pickup to make it easier in a later quarter.

Suggestions are to ensure our builder names are unique (they all have -perf-bisect on them so they almost certainly are), and to try out vpython on the swarmbucket builders.
Owner: simonhatch@chromium.org
Actually, I should check if there needs to be any work on the Pinpoint builder side of things.
Simon: note that I am working on converting perf bots to LUCI this quarter. The guideline say we should convert try & ci builder in close proximity :-/
Sounds good, let's sync and see what needs to be done, threw a quick invite on your calendar for tomorrow since you're booked up today.
Blockedon: 810414
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Labels: -Pri-1 Pri-3
Update: We're just waiting on DEPS inversion and then we're sunsetting the recipe bisect. We almost certainly won't be doing this. Will leave it open until that actually happens.
Owner: dtu@chromium.org

Sign in to add a comment