RealSpamapS

Anyone who agrees with the OP should give Zuul-ci.org a look.

I run Zuul in production with GitHub and AWS, and it's been really useful for us. It scales to the moon, parallelizes everything, and having all job/pipeline configuration in git means you can test things like CI job changes before they're committed.

Cross-repo pre-merge dependency management means I can build whole speculative futures in PR's before it lands and breaks the build.

Funny story, the Zuul build status badge is just a static image, because Zuul does not allow code to merge if it fails tests: https://zuul-ci.org/docs/zuul/user/badges.html

Full disclosure: I worked on a defunct zuul based service for a little while, and still am a core developer with lots of code in Zuul. A few presentations I've given are here:

http://fewbar.com/the-build-is-never-broken/ http://fewbar.com/zuul-ci-crossing-streams/

It's just a simple matter of code. You're not the first to want BitBucket support.

It was a multi-year effort including us asking specifically for the policy to be spelled out at why there could be only one. IMO the Debian security team wrote a policy specifically to target Oracle in this specific instance, as a result. Digging it out is painful, as it all happened back in 2016, but you can start here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793316

To be clear, those who were maintaining MySQL at the time this decision was made were perfectly happy maintaining both (I am one of those people, sort of, not very active the last couple years). The security team and release team is to blame, please direct your complaints to them.

https://tracker.debian.org/pkg/mysql-5.7

This is half correct. MySQL is not available in Debian STABLE.

It was allowed to stay in unstable:

https://packages.debian.org/sid/mysql-server-5.5

However, the maintainers are uninterested in maintaining it there, since the release and security team have overrode them and forcibly removed it from stable.