Closed Bug 1256347 Opened 9 years ago Closed 9 years ago

replace buidlbot, buildbot-try, buildbot-staging TC clients

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

Details

As part of the login v3 effort, we're replacing the old, slugid-formatted clientIds with longer, more readable clientIds. The credentials used by mozharness to upload are among these: KHa1Y5wARRGL8R6GAsgW3w - buildbot-try Client for buildbot/mozharness to upload build artifacts to S3 instead of FTP for try builds. SUkfDCeyStmQbgu4f4yXCg - buildbot-staging For staging buildbot builds to upload files. yvP37tZ_S52uOeZm-Ep4IA - buildbot Client for buildbot/mozharness to upload build artifacts to S3 instead of FTP. These should be replaced with clientIds like project/releng/mozharness-upload/{production,staging,try}.
I don't see where these are configured -- I've looked in puppetagain, and don't see anything relevant..
Assignee: nobody → dustin
https://dxr.mozilla.org/build-central/source/puppet/modules/buildmaster/templates/BuildSlaves-build.py.erb https://dxr.mozilla.org/build-central/source/puppet/modules/buildmaster/templates/BuildSlaves-try.py.erb Those secrets are updated in hiera. I'll wait a day or two to see if the old clientIds are still in use somewhere else. I don't see where the staging key is defined -- but I suspect we can set that up when it's required (it hasn't been used for two weeks).
>= two days since last use for all three of the old clientIds. Deleted.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.