Closed
Bug 657361
Opened 14 years ago
Closed 12 years ago
move update-bump-unit-tests off build.mozilla.org
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dustin, Unassigned)
References
Details
(Whiteboard: [updates])
Attachments
(1 file)
4.36 KB,
patch
|
Details | Diff | Splinter Review |
I'm not entirely sure what these are. The text says:
still used for the patcher and update verify config bumpers in tools/release
and the link is
http://build.mozilla.org/update-bump-unit-tests/
It looks like the following could be changed to point this elsewhere:
./release/patcher-config-creator.pl: # Using this update-bump-unit-tests dir makes the mar URLs less realistic
./release/patcher-config-creator.pl: my $stagingServer = 'build.mozilla.org/update-bump-unit-tests';
./release/update-verify-bump.pl: oldCandidatesDir => '/update-bump-unit-tests/pub/mozilla.org/firefox/nightly/3.0.2-candidates/build6',
./release/update-verify-bump.pl: oldCandidatesDir => '/update-bump-unit-tests/pub/mozilla.org/firefox/nightly/3.1b1-candidates/build2',
./release/update-verify-bump.pl: oldCandidatesDir => '/update-bump-unit-tests/pub/mozilla.org/firefox/nightly/3.6a1-candidates/build1',
./release/update-verify-bump.pl: oldCandidatesDir => '/update-bump-unit-tests/pub/mozilla.org/firefox/nightly/3.5.5-candidates/build1',
./release/update-verify-bump.pl: oldCandidatesDir => '/update-bump-unit-tests/pub/mozilla.org/firefox/nightly/3.5.5-candidates/build1',
I'm assuming this is an inside-the-build-network-only resource? Any additional pointers?
Comment 1•14 years ago
|
||
These can live anywhere, I'll take this bug and figure out exactly what to do with them.
Assignee: nobody → bhearsum
Comment 2•14 years ago
|
||
Let's put these on a new vhost/cname, "updatetests.build.mozilla.org".
Assignee: bhearsum → nobody
Comment 3•14 years ago
|
||
Updated•14 years ago
|
Priority: -- → P3
Whiteboard: [updates]
Reporter | ||
Comment 4•13 years ago
|
||
Should this be internal-access only?
Comment 5•13 years ago
|
||
No, they don't need to be.
Reporter | ||
Comment 6•13 years ago
|
||
I added update-tests.pub.build.mozilla.org, pulling from a different directory: /mnt/netapp/relengweb/update-tests
I've rsync'd the contents of that directory from the old location,
/mnt/netapp/relengweb/oldstuff/var-www-html/build/update-bump-unit-tests/
but not set up any automated process to do so. If that's useful, I can add a crontask; otherwise, let's just get this transitioned to the new vhost and be done with it.
DNS isn't resolving correctly yet for me, but hopefully that will clear up shortly.
http://update-tests.pub.build.mozilla.org/pub/mozilla.org/firefox/nightly/2.0.0.16-candidates/build1/linux_info.txt
I'll double-check the DNS in a bit, but otherwise I think this is ready for an updated version of bhearsum's config patch in comment 3.
Reporter | ||
Comment 7•13 years ago
|
||
DNS is OK now.
Comment 8•12 years ago
|
||
bhearsum, coop, dustin:
Found in triage; anything left to do here?
Reporter | ||
Comment 9•12 years ago
|
||
Yes, a new version of the attachment in comment 3 needs to be landed.
Reporter | ||
Comment 10•12 years ago
|
||
I'd like to wrap bug 604688 up this quarter, if possible. Is this a config change we could make fairly expeditiously?
Comment 11•12 years ago
|
||
We can WONTFIX, actually! Both of these scripts are now dead.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•