Hi Brad, thanks for the clarification. I really dislike using unpackaged software in a package-managed environment, so I’d gladly use the APT repo anytime. But since you stated it this way, I think I’ll have a look at how I can integrate it in the script parts (which I maintain) that will make CMake and other stuff available.
But the joke’s still on us regarding the broken CI, because technically the colleagues who run the CI processes should IMO use an APT caching proxy of sorts. There are enough ways to decouple from external resources while also keeping an eye on the use of said external resources. My remark was more meant as confirmation, because I reported another “issue” in January which turned out to be PEBKAC.
Also noticed the apt.kitware.com page changed ever so slightly overnight 
(and yeah I confirmed this hadn’t been mentioned before):
This repository is intended for developers to install packages on their own machines. Please do not use this apt repository in CI jobs. Our official release binaries are hosted by GitHub’s CDN.
Side-note: the script which does use the APT repo is in fact geared to developers. In fact to manual preparation of a developer machine. It was co-opted by our CI folks into their process, because it’s so convenient.