Closed Bug 821772 Opened 13 years ago Closed 13 years ago

remove try server support of otoro builds

Categories

(Release Engineering :: General, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Unassigned)

Details

As cleanup after bug#819225, and meetings w/jishnu, we're more tightly restricting access to otoro builds. Should we remove otoro builds as an option from tryserver? Anyone with try access (L1 - includes moco+contractors+community) being able to generate otoro builds seems like it should be turned off, based on the meeting yesterday. If you agree that we should turn off, please say so here and reassign the bug to RelEng. However, if its ok to leave on, please close this bug as WONTFIX. In this context, "turning off" means: * removing from trychooser * removing ability for users pushing to try to generate an otoro build
Assignee: nobody → jmenon
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: under legal review
(In reply to John O'Duinn [:joduinn] from comment #0) > As cleanup after bug#819225, and meetings w/jishnu, we're more tightly > restricting access to otoro builds. > > Should we remove otoro builds as an option from tryserver? Anyone with try > access (L1 - includes moco+contractors+community) being able to generate > otoro builds seems like it should be turned off, based on the meeting > yesterday. If you agree that we should turn off, please say so here and > reassign the bug to RelEng. However, if its ok to leave on, please close > this bug as WONTFIX. jishnu: ping? How should we proceed here? > In this context, "turning off" means: > * removing from trychooser > * removing ability for users pushing to try to generate an otoro build
(In reply to John O'Duinn [:joduinn] from comment #1) > (In reply to John O'Duinn [:joduinn] from comment #0) > > As cleanup after bug#819225, and meetings w/jishnu, we're more tightly > > restricting access to otoro builds. > > > > Should we remove otoro builds as an option from tryserver? Anyone with try > > access (L1 - includes moco+contractors+community) being able to generate > > otoro builds seems like it should be turned off, based on the meeting > > yesterday. If you agree that we should turn off, please say so here and > > reassign the bug to RelEng. However, if its ok to leave on, please close > > this bug as WONTFIX. > > jishnu: ping? How should we proceed here? > ping? > > In this context, "turning off" means: > > * removing from trychooser > > * removing ability for users pushing to try to generate an otoro build
Yes - let's disable this in try. If this is burden for developers, they can use project branches and we can grant access as-needed based on the whitelist for the PDT build share.
Group: legal
Component: Boot to Gecko → Release Engineering
Product: Legal → mozilla.org
Version: unspecified → other
Changing assignee
Assignee: jmenon → joduinn
Whiteboard: under legal review
(In reply to Jishnu Menon from comment #3) > Yes - let's disable this in try. > > If this is burden for developers, they can use project branches and we can > grant access as-needed based on the whitelist for the PDT build share. Thanks Jishnu. will do.
Component: Release Engineering → Release Engineering: Developer Tools
QA Contact: hwine
Assignee: joduinn → nobody
Otoro builds were disabled everywhere except mozilla-b2g18 on december 13th. They're now also enabled on the mozilla-b2g18-v1_0_0 and mozilla-b2g18-v1_0_1 branches.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.