New issue
Advanced search Search tips

Issue 882990 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature

Blocking:
issue 882994



Sign in to add a comment

Link to CIPD UI https://chrome-infra-packages.appspot.com from swarming task details

Project Member Reported by tandrii@chromium.org, Sep 11

Issue description

A task usually resolves and installs a bunch of CIPD packages.
Linking to exact package instance that was installed will save a bunch of clicks during debug.

Repro:
1. visit https://chromium-swarm.appspot.com/task?id=3fe250d2d8491b10&refresh=10&request_detail=true&show_raw=1
2. click "more details"
3. Scroll down to CIPD packages  https://screenshot.googleplex.com/PGudFOPCsTp 
 
Labels: -Restrict-View-Google
Cc: kjlubick@chromium.org
Status: Available (was: Untriaged)
That's a good idea.
Blocking: 882994
Owner: kjlubick@chromium.org
Status: Assigned (was: Available)
I'd like to be able to do this in a generic way, kind of how we link in the source repos.

I.e. I need to know the infra server (which is already passed in) and some rule for properly linking to https://chrome-infra-packages.appspot.com/p/infra/python/cpython/windows-amd64/+/ for a CIPD package infra/python/cpython/windows-amd64

If we don't mind a chromium-specific fix, then I can have this linkified in short order.  A more generic approach would likely involve a proto update.
The service URL is in the /request as cipd_inputs/client_package/server in the properties, so one per task slice.

So no need to hard code the URL.
The same transform (server + "/p/" + package) can be assumed for all potential CIPD set-ups?
Cc: vadimsh@chromium.org
yes and there's only one
Status: Started (was: Assigned)
Status: Fixed (was: Started)
This change is now live on prod with 3809-a31bbe1.

Sign in to add a comment