It's MIT licensed. If you want to setup your own CI servers, you're free to fork the code.
But... try getting patches in. Unless you're a paying member of the ISC consortium, you can't. There are performance problems going back a decade which are firmly in the "won't fix" category.
OpenSSL is similar.
TFA is about ubuntu making forking difficult.
"Free software" also means source-code being distributed under an FSF approved license. Unfortunately English doesn't have an equivalent for "libre", like romance languages do, with "free" being overloaded. So of course, usage of "free" has a long history of being overridden depending on context, going back to freemium/freeware/shareware. This is why context is important and why people then feel the need to be precise about the kind of free we are talking about - free as in beer or as in speech. You're talking about free as in beer and in our context Free Software really refers to FSF approved licensing. And Wikipedia does agree. Of course, the set of licenses that are FSF approved and OSI approved does overlap, though in theory you could have some differences, because the definitions are different. For example I think AGPL should not be OSI approved. But I digress.
Back to the point I want to make - source code being able does not make a software open source and having the binaries free as in beer does not make it free software.