#58603 closed defect (wontfix)
Add Azure build system IP addresses to MaxCDN configuration
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | admin@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | server/hosting | Version: | |
| Keywords: | Cc: | ||
| Port: |
Description
We are now using Azure as an additional build system in addition to Travis CI.
But we have configured the packages-private zone at MaxCDN to allow connections only from Travis CI's published list of IP addresses.
We need to add Azure's IP addresses to that configuration too so the Azure build can benefit from pre-compiled nondistributable archives too. I previously mentioned this on the infra mailing list but we forgot to do anything about it.
Does anybody know where the list of Azure IP addresses is?
Change History (7)
comment:1 Changed 5 years ago by l2dy (Zero King)
comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
They're currently not publishing their Mac server IPs. But looking at the CDN log I found an IP address they're using and added it to the allowed list.
comment:3 Changed 4 years ago by neverpanic (Clemens Lang)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
We are no longer using MaxCDN.
comment:4 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
But therefore we need to add those IPs directly to the packages-private server. I think I already did that, using the IP I found above, but if they ever change the IP or if we ever find an official list of published IPs we should use that.
comment:5 Changed 4 years ago by neverpanic (Clemens Lang)
Sounds to me like we should really be using a different mechanism, like a password only available to the CI system.
comment:6 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
I don't know if we had the ability to configure password-protected realms using our former CDN. We do now, since we no longer have the CDN, but we are looking for a new CDN so we may want to wait and see what capabilities it has before we make changes.
Also, I don't know how to give the CI system a password that users would not be able to see.
comment:7 Changed 4 years ago by neverpanic (Clemens Lang)
We can configure secrets in the CI, but only PRs opened from the same repo would have access to them, so that probably doesn't help us as much as I thought initially :/
See https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted#agent-ip-ranges. They might add new IP ranges every week though.