Closed
Bug 1578264
Opened 5 years ago
Closed 5 years ago
generic-worker: Support GCP deployments
Categories
(Taskcluster :: Workers, enhancement)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Assigned: pmoore)
Details
Attachments
(1 file)
Long term we're intending to use something more sophisticated, but for the sake of continuity and having a backup plan, let's adapt worker_type.sh to work with both AWS and GCP worker deployments.
It seems there are equivalent gcloud commands for the aws commands, and probably equivalent URLs we can dump in the logs.
|
Assignee | |
Updated•5 years ago
|
Assignee: nobody → pmoore
|
|
Assignee | |
Comment 1•5 years ago
|
||
:miles has highlighted that monopacker may already be suitable, and that this bug might not be necessary, so we'll meet up to go through it together, and report back in this bug if we intend to continue with this or not.
|
|
Assignee | |
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Updated•5 years ago
|
Summary: Adapt worker_type.sh to work with both AWS and GCP → Support GCP deployments
|
|
Assignee | |
Comment 2•5 years ago
|
||
Released in generic-worker 16.1.0.
|
|
Assignee | |
Comment 3•5 years ago
|
||
|
|
Assignee | |
Updated•5 years ago
|
Summary: Support GCP deployments → generic-worker: Support GCP deployments
You need to log in
before you can comment on or make changes to this bug.
Description
•