buildbot: 1.4.0 -> 1.8.1

[lopsided98]

Motivation for this change

Update all of buildbot to 1.8.0 (the master package had previously been updated to 1.5.0), and make it build again.

Things done

I also disabled buildbot's tests due to some failures. These failures were not caused by the upgrade to 1.7.0, but already occurred with 1.4.0. They are likely due to an upgrade of a dependency. I tried to bisect, but buildbot was previously broken because some of its dependencies failed to build, so I could not figure out when the tests started to fail.

I ran the NixOS tests and they passed.

• Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
• Built on platform(s)
  • NixOS
  • macOS
  • other Linux distributions
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
• Tested execution of all binary files (usually in ./result/bin/)
• Determined the impact on package closure size (by running nix path-info -S before and after)
• Assured whether relevant documentation is up to date
• Fits CONTRIBUTING.md.

---

[FRidh]

cc @nand0p @ryansydnor

[lopsided98]

1.7.0 has been released, so this PR now updates buildbot to this version.

[lopsided98]

1.8.0 has been released, so this PR now updates buildbot to this version.

A change to SQLite broke sqlalchemy-migrate, which was causing the tests to fail. This PR includes an update of sqlalchemy-migrate to 0.12.0 which fixes the issue. Therefore buildbot's tests have been re-enabled.

[veprbl]

@lopsided98 Can you please update this to at least 1.8.1. That would fix https://github.com/buildbot/buildbot/wiki/CRLF-injection-in-Buildbot-login-and-logout-redirect-code then

[lopsided98]

I updated to 1.8.1. I don't have time to do the update to 2.0.0 update right now since it requires changes to the tests and possibly the NixOS module (because it drops support for Python 2).

Maybe this PR should just be merged and then I'll create a new one for the update to 2.0.0?

[veprbl]

@lopsided98 Yes, I had the same idea.

@GrahamcOfBorg build python2Packages.buildbot python2Packages.buildbot-full
@GrahamcOfBorg build python3Packages.buildbot python3Packages.buildbot-full
@GrahamcOfBorg test buildbot

[veprbl]

Thank you!