-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Closed
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem teamTriaged by Ecosystem team
Description
We need access to gcloud to run FTL tests. On the Cirrus side we do this in the Dockerfile, which for most things we have been replacing with cipd packages. However, for gcloud the existing cipd package isn't in the Flutter-owned location, so we can't just reference it in the dependencies section of .ci.yaml.
To avoid making a duplicate cipd package, my plan is to explore having a property we can set in .ci.yaml that will trigger using recipe_modules/gcloud/api.py to install gcloud. If I'm understanding that code correctly, once it's installed we can run it from gcloud/bin/gcloud.
Metadata
Metadata
Assignees
Labels
P1High-priority issues at the top of the work listHigh-priority issues at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem teamTriaged by Ecosystem team