Closed Bug 1589760 Opened 6 years ago Closed 6 years ago

Temporarily Adjust TASKCLUSTER_ACCESS_TOKEN for four of the GCP dev workers

Categories

(Cloud Services :: Operations: Product Delivery, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mtabara, Assigned: oremj)

References

Details

We're trying to make some of the GCP dev workers talk to the new dedicated Firefox CI instance.

In order for that to happen, we've replicated the same Tasckluster Clients IDs (obviously with new tokens which I'll send in a bit privately).

Summary: Adjust TASKCLUSTER_ACCESS_TOKEN for four of the GCP dev workers → Temporarily Adjust TASKCLUSTER_ACCESS_TOKEN for four of the GCP dev workers

Bumping this in Severity as meeting for go/no-go happens on Monday and we need to validate a staging release before than in order to confirm that we're ready to switch to the new cluster.

Assignee: nobody → oremj

Status update: @oremj updated credentials on CloudOps side and I pushed

diff --git a/docker.d/init.sh b/docker.d/init.sh
index 6e3812d..46a40c1 100755
--- a/docker.d/init.sh
+++ b/docker.d/init.sh
@@ -22,6 +22,8 @@ if [ "$ENV" == "prod" ]; then
   test_var_set 'ED25519_PRIVKEY'
 fi
 
+# XXX: bug 1589703 temp hack to test the new Firefox CI cluster
+export TASKCLUSTER_ROOT_URL=https://stage.taskcluster.nonprod.cloudops.mozgcp.net

to our `dev-{signingscript, beetmoverscript, balrogscript, bouncerscript}

Jeremy updated the credentials, closing this and moving the conversation in the main bug 1589703.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
See Also: → 1591385
You need to log in before you can comment on or make changes to this bug.