In bug 417357 and bug 417626, build.m.o is set to proxy for all CVS/LDAP users to the production-1.9-master and production-1.8-master nightly waterfalls. Can the same be done for mozilla-central? Also, these should probably be publicized more, because it allows developers more control and insight into the environment (e.g. ability to force build, real-time logs, clobber could be exposed here..). Anyway filing in release automation, this will probably need to move to server operations but I wanted to make sure the release team approves of this change. philor reports that the 1.9/1.8 links aren't working anymore, should look into that too, separate bug maybe?
(In reply to comment #0) > philor reports that the 1.9/1.8 links aren't working anymore, should look into > that too, separate bug maybe? (hi rob!) The offset ports like http://production-1.8-master.build.mozilla.org:8811/ went away when we upgraded buildbot to 0.7.7. We'd want http://production-1.8-master.build.mozilla.org:8810/waterfall?category=nightly instead. Probably IT will need to fix up build.mozilla.org.conf on build.m.o.
In triage, seems like a necessary step to start us moving from tinderbox to buildbot. Yes, lets do this. 1) production-1.9-master, production-1.8-master are going away, being replaced with production-master.b.m.o. Lets make production-master visible. 2) Reassigning to IT to change build.mozilla.org.conf.
Assignee: nobody → server-ops
Component: Release Engineering → Server Operations
QA Contact: release → mrz
To add some specifics, we'd like https://build.mozilla.org/mozilla-central-nightly/ to be a proxy for http://production-master.build.mozilla.org:8010/waterfall [There's actionmonkey and tracemonkey builds there too but wth] Please also change https://build.mozilla.org/1.8-nightly/ to be a proxy for http://production-1.8-master.build.mozilla.org:8810/waterfall?category=nightly And https://build.mozilla.org/1.9-nightly/ to proxy http://production-1.9-master.build.mozilla.org:8810/waterfall?category=nightly Thanks.
mrz, need firewall holes for the following: dm-wwwbuild01 -> production-master.build.mozilla.org:8010 dm-wwwbuild01 -> production-1.8-master.build.mozilla.org:8810 dm-wwwbuild01 -> production-1.9-master.build.mozilla.org:8810
Status: NEW → ASSIGNED
access-list into-build permit tcp host 10.2.74.128 host 10.2.71.90 eq 8010 access-list into-build permit tcp host 10.2.74.128 host 10.2.71.76 eq 8810 access-list into-build permit tcp host 10.2.74.128 host 10.2.71.225 eq 8810
RewriteEngine On RewriteRule ^/1.8-nightly$ /1.8-nightly/ [R] RewriteRule ^/1.8-nightly/$ http://production-1.8-master.build.mozilla.org:8810/waterfall?category=nightly [P] RewriteRule ^/1.8-nightly/buildbot.css$ http://production-1.8-master.build.mozilla.org:8810/buildbot.css [P] RewriteRule ^/1.9-nightly$ /1.9-nightly/ [R] RewriteRule ^/1.9-nightly/$ http://production-1.9-master.build.mozilla.org:8810/waterfall?category=nightly [P] RewriteRule ^/1.9-nightly/buildbot.css$ http://production-1.9-master.build.mozilla.org:8810/buildbot.css [P] RewriteRule ^/mozilla-central-nightly[/]?$ /mozilla-central-nightly/waterfall [R] RewriteRule ^/mozilla-central-nightly/(.*) http://production-master.build.mozilla.org:8010/$1 [P]
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.