Closed
Bug 399887
Opened 17 years ago
Closed 13 years ago
Sisyphus - move /work/mozilla/builds to sisyphus/builds
Categories
(Testing Graveyard :: Sisyphus, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bc, Assigned: bc)
References
Details
Currently the build mozconfig files used by Sisyphus live separately in the local directories /work/mozilla/builds/$b/ where b=1.8.1, 1.9.0, etc. These files are not currently under cvs control which makes it more difficult to keep the buildbot slave machines up to date in case of changes. Rob, What would you say to my moving /work/mozilla/builds to /work/mozilla/mozilla.com/test.mozilla.com/www/builds and checking in the mozconfig files into sisyphus/builds/$b/ ?
Flags: in-testsuite-
Flags: in-litmus-
Assignee | ||
Comment 1•17 years ago
|
||
One issue with this move would be if you need to remove the sisyphus directory each time you do an update from CVS. That would result in the build trees being removed as well if they continue to live in builds/$b/mozilla. I could put the checked out source outside of the sisyphus directory, but it would be nice to just be able to cvs update in place. Is there script support I could add that would making cvs updating sisyphus and the js tests easier for you and buildbot?
Comment 2•16 years ago
|
||
Mass move of Sisyphus bugs to Testing : Sisyphus. Filter on SisyphusMassMove to ignore.
Component: Testing → Sisyphus
Flags: in-litmus-
Product: Core → Testing
QA Contact: testing → sisyphus
Assignee | ||
Updated•13 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•