Closed
Bug 1164612
Opened 10 years ago
Closed 9 years ago
Encrypt the relengapi token when submitting Android jobs to TC
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
The RELENGAPI_TOKEN variable needs to be set for Android builds, since they need to use tooltool.
It's not clear to me where this token would come from for a try job or a scheduled job -- is it up to the scheduler to find the value and encrypt it?
Updated•10 years ago
|
Assignee: dustin → winter2718
Comment 1•10 years ago
|
||
There is currently no way to do this in tree. A promising solution seems to be adding a proxy container which doles out keys to workers based on their scopes.
Comment 2•9 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] from comment #0)
> The RELENGAPI_TOKEN variable needs to be set for Android builds, since they
> need to use tooltool.
>
> It's not clear to me where this token would come from for a try job or a
> scheduled job -- is it up to the scheduler to find the value and encrypt it?
Removing myself from this, since you're working on the proxy. No sense for it to sit in my queue.
Updated•9 years ago
|
Assignee: winter2718 → nobody
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → dustin
Assignee | ||
Comment 3•9 years ago
|
||
Closing this in favor of bug 1170753, which will be closed shortly.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•