Closed
Bug 813515
Opened 12 years ago
Closed 8 years ago
don't create index files in partner-repacks directory on stage
Categories
(Release Engineering :: Release Automation: Other, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cbook, Unassigned)
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2498] )
when i go to http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/17.0-candidates/build2/partner-repacks/ i get the "thanks for the interest, We aren't quite finished qualifying Firefox 17.0 yet" so i guess its now linking to ftp.mozilla. Can we bring it back to stage like we did before always thanks!
Comment 1•12 years ago
|
||
So, I verified this was due to our index.html block hanging around all the partner-repack dir's. With Tomcats r+ in IRC I did a find -name index.html, and then an rm -f {}; based on that list, in the -candidates dir. We should resolve this going forward somehow though (even if thats just to hand out ftp://ftp.m.o links in the future)
Comment 2•12 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #1) > With Tomcats r+ in IRC I did a find -name index.html, and then an rm -f {}; > based on that list, in the -candidates dir. For clarity, I *only* removed the index.html's in the partner-repacks/** subdir of the candidate dir for build2
Comment 3•12 years ago
|
||
I though that we put those files intentionally, don't we? Maybe we should we skip partner-repacks directory?
Updated•12 years ago
|
Component: Release Engineering → Release Engineering: Automation (Release Automation)
QA Contact: bhearsum
Reporter | ||
Comment 4•12 years ago
|
||
(In reply to Rail Aliiev [:rail] from comment #3) > I though that we put those files intentionally, don't we? Maybe we should we > skip partner-repacks directory? yeah we should just skip partner-repacks i think. The reason for this bug was that we point partners to stage because there are the repacks available after creation and partners normally need some time to qa a repack etc. also for the history we always kept partner-repacks open on stage like http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/16.0-candidates/build1/partner-repacks/
Comment 5•12 years ago
|
||
Just need to adjust this find command to do fix this: https://github.com/mozilla/build-tools/blob/master/scripts/release/stage-tasks.py#L163
Summary: partner repacks for Firefox 17 Build 2 missing on stage → don't create index files in partner-repacks directory on stage
Updated•12 years ago
|
Priority: -- → P3
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2498]
Comment 6•8 years ago
|
||
We stopped doing this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•