[MacPorts] #67594: build.macports.org: implement simple front-end to display status; including "down for maintenance" (if intentional), or "no response from buildbot infrastructure" (for unanticipated issues)
MacPorts
noreply at macports.org
Thu Jun 8 16:41:49 UTC 2023
#67594: build.macports.org: implement simple front-end to display status; including
"down for maintenance" (if intentional), or "no response from buildbot
infrastructure" (for unanticipated issues)
----------------------------+---------------------
Reporter: mascguy | Owner: admin@…
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: buildbot/mpbb | Version:
Resolution: | Keywords:
Port: |
----------------------------+---------------------
Comment (by ryandesign):
When the internet connection that build.macports.org uses is down, as it
was today, and on May 31, and on May 30, there is no way for it to provide
a response.
If you're suggesting routing all build.macports.org web traffic through
another server on a different internet connection so that it could provide
a message when the real server is unreachable, which server would we use
for that?
Conceivably we could use Braeburn, the server that powers www.macports.org
and trac.macports.org. But I'm not sure if it has the capacity to
accommodate that additional traffic. And it is in Germany and the
buildmaster is in Texas. I'm not sure if introducing additional network
delay to all requests is best, since people already complain that it
responds slowly (which is both because of limited upstream network
bandwidth and the amount of time it takes buildbot 0.8 to respond to some
types of requests). It also introduces an additional point of failure. I
usually keep a close eye on the buildmaster and know when it is down and
what I need to do to get it back online, but that changes when additional
servers outside of my control are added in.
When I shut the servers down in anticipation of a thunderstorm and
possible power outage, I leave the internet connection and router on, and
the router could conceivably act as reverse proxy to provide a message
when the backend is down. It might also be nice to let the router handle
TLS and certificates. I did attempt to set that up about a year ago but
didn't complete it.
--
Ticket URL: <https://trac.macports.org/ticket/67594#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list