Access on secrets:set:project/relman/coverity and secrets:set:project/relman/coverity-nss
Categories
(Release Engineering :: Firefox-CI Administration, task)
Tracking
(Not tracked)
People
(Reporter: andi, Assigned: mtabara)
References
Details
Attachments
(2 files, 1 obsolete file)
Hello,
I need write access on these two secrets:
secrets:set:project/relman/coverity
secrets:set:project/relman/coverity-nss
I'm the maintainer of coverity analysis and before migrating to firefox-ci I had write access to these secrets.
This blocks the migration to the newest version of Coverity that adds support for clang-9.
Thanks
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
| Assignee | ||
Comment 2•6 years ago
|
||
Citing from a similar request we've had in the recent past, if a mozillian group is needed, the team that is responsible for it should create it, and then we can grant that group scopes. RelEng shouldn't be involved in managing the membership of teams, for security and other related reasons.
To be usable by taskcluster, it needs to be an access group and should be either closed or reviewed.
If I understood correctly, you wanted to include Marco and Bastien in the group as well? If so, please create the related group (coverity or alike) and then I can make amendments on our end to grant that.
| Assignee | ||
Comment 3•6 years ago
|
||
Bug 1607198 - switch coverity secrets to moz group. r=jlorenzo
Updated•6 years ago
|
| Assignee | ||
Comment 4•6 years ago
|
||
| Reporter | ||
Comment 5•6 years ago
|
||
After chating on irc we've decided to use the group code-review-developers. Mihai thanks for the help!
| Assignee | ||
Comment 6•6 years ago
|
||
Deployed the changes. The https://mozillians.org/en-US/group/code-review-developers/ core of developers now have access to these secrets.
Description
•