In pyhf we have tutorials in Binder. As part of our CI when we merge a PR into master we try to trigger a Binder build on
master by basically
curling the build API endpoint so that a user never has to wait for Binder to build. This has worked well for a long time and I’ve added this functionality to other projects as well.
However, it seems that between May 24th, 2019 and June 21st, 2019 this seems to have stopped working. It seems that this is because when the url https://mybinder.org/build/gh/diana-hep/pyhf/master gets resolved it redirects to https://gke.mybinder.org/build/gh/diana-hep/pyhf/master. I’m not sure, but given a search on “gke” in the Discourse it seems that GKE is one of the deployments of BinderHub in the Binder Federation (please correct me if I’m wrong).
My question is how can I know what endpoint will actually get resolved so that our
trigger_binder.sh script can actually wait long enough to trigger the build?