Closed
Bug 1554825
Opened 6 years ago
Closed 6 years ago
Please set up stage environment for beetmover scriptworker
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Cloud Services
Operations: Miscellaneous
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Assigned: oremj)
References
Details
Please create a deployment for stage beetmover scriptworkers. Some information below.
- No special cluster requirements. This scriptworker will be communicating to S3, which is public.
- It should track the docker image from
mozilla/beetmoverscript:*
(all tags if possible) - use the default docker CMD, no need to override
- use /bin/healthcheck for health checks
- Set the grace period to 240 seconds. The workers stop handling new tasks after they receive a SIGTERM signal.
- Set the replica count to 1, we will deploy another worker to scale them up and down
- Our current capacity is 10 stage workers. We may want to have a pool sizable to 10-20 stage workers probably.
- The following env variables should be set:
COT_PRODUCT=firefox
WORKER_GROUP=beetmoverworker-v1
WORKER_TYPE=beetmoverworker-dev
TASKCLUSTER_CLIENT_ID=xxxx
TASKCLUSTER_ACCESS_TOKEN=xxx
APP_CHANNEL=stage
DEP_PARTNER_ID=xxx
DEP_PARTNER_KEY=xxx
MAVEN_STAGING_ID=xxx
MAVEN_STAGING_KEY=xxx
DEP_ID=xxx
DEP_KEY=xxx
ED25519_PRIVKEY=
(I'll send the secrets when needed)
Thank you in advance and feel free to ping me anytime if something is missing or not clear enough.
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → oremj
Reporter | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•