Closed
Bug 1352229
Opened 9 years ago
Closed 9 years ago
Create S3 bucket for Treeherder artifacts
Categories
(Cloud Services :: Operations: Miscellaneous, task, P5)
Cloud Services
Operations: Miscellaneous
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: davehunt, Assigned: ckolos)
Details
Please create a new S3 bucket named net-mozaws-stage-fx-test-treeherder for publishing our Treeherder artifacts (build logs, results, reports). This is very similar to the existing net-mozaws-stage-fx-test-activedata bucket for ActiveData, and requires the same permissions (write from fx-test-jenkins.stage.mozaws.net, public read).
| Assignee | ||
Comment 1•9 years ago
|
||
Bucket and associated credentials created. Config is under the TreeHerder profile.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 2•9 years ago
|
||
Could you clarify "Config is under the TreeHerder profile", as I'm unable to view the configuration. I was expecting that the existing "ActiveData" profile could be shared (and later renamed to be more appropriate). Is there a reason we need separate profiles? If we do indeed need separate profiles, could this one be renamed "Treeherder" (note the lower-case "h").
Flags: needinfo?(ckolos)
| Assignee | ||
Comment 3•9 years ago
|
||
fixed to use common credentials for all s3 publishing. This is done under the fx-test-jenkins-s3-publisher profile in the S# publisher plugin configuration. bucket permissions are managed on a per-bucket basis and all existing buckets have been configured to use the credentials associated with this common account.
Flags: needinfo?(ckolos)
| Reporter | ||
Updated•9 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•