From 9fa9afe71e9be5674e479101d4231dfa8b1c8489 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B8rn=20Forsman?= Date: Tue, 7 May 2013 22:56:22 +0200 Subject: [PATCH] buildbot-slave: new package Tested with buildbot (master). --- .../build-managers/buildbot-slave/default.nix | 64 +++++++++++++++++++ pkgs/top-level/all-packages.nix | 4 ++ 2 files changed, 68 insertions(+) create mode 100644 pkgs/development/tools/build-managers/buildbot-slave/default.nix diff --git a/pkgs/development/tools/build-managers/buildbot-slave/default.nix b/pkgs/development/tools/build-managers/buildbot-slave/default.nix new file mode 100644 index 00000000000..da38bc0a133 --- /dev/null +++ b/pkgs/development/tools/build-managers/buildbot-slave/default.nix @@ -0,0 +1,64 @@ +{ stdenv, buildPythonPackage, fetchurl, coreutils, twisted }: + +buildPythonPackage (rec { + name = "buildbot-slave-0.8.7p1"; + namePrefix = ""; + + src = fetchurl { + url = "http://buildbot.googlecode.com/files/${name}.tar.gz"; + sha256 = "1p7a0srab6ifljh9vi25awvxfrxljj9s0hi1jipiiykyhjihgnxv"; + }; + + patchPhase = '' + substituteInPlace buildslave/scripts/logwatcher.py --replace /usr/bin/tail ${coreutils}/bin/tail + ''; + + propagatedBuildInputs = [ twisted ]; + + # What's up with this?! 'trial' should be 'test', no? + # + # running tests + # usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] + # or: setup.py --help [cmd1 cmd2 ...] + # or: setup.py --help-commands + # or: setup.py cmd --help + # + # error: invalid command 'trial' + doCheck = false; + + postInstall = '' + mkdir -p "$out/share/man/man1" + cp docs/buildslave.1 "$out/share/man/man1" + ''; + + meta = { + homepage = http://buildbot.net/; + + license = "GPLv2+"; + + description = "Continuous integration system that automates the build/test cycle"; + + longDescription = + '' The BuildBot is a system to automate the compile/test cycle + required by most software projects to validate code changes. By + automatically rebuilding and testing the tree each time something + has changed, build problems are pinpointed quickly, before other + developers are inconvenienced by the failure. The guilty + developer can be identified and harassed without human + intervention. By running the builds on a variety of platforms, + developers who do not have the facilities to test their changes + everywhere before checkin will at least know shortly afterwards + whether they have broken the build or not. Warning counts, lint + checks, image size, compile time, and other build parameters can + be tracked over time, are more visible, and are therefore easier + to improve. + + The overall goal is to reduce tree breakage and provide a platform + to run tests or code-quality checks that are too annoying or + pedantic for any human to waste their time with. Developers get + immediate (and potentially public) feedback about their changes, + encouraging them to be more careful about testing before checking + in code. + ''; + }; +}) diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix index 7302b25ac9e..2775448be14 100644 --- a/pkgs/top-level/all-packages.nix +++ b/pkgs/top-level/all-packages.nix @@ -3106,6 +3106,10 @@ let dateutil = pythonPackages.dateutil_1_5; }; + buildbotSlave = callPackage ../development/tools/build-managers/buildbot-slave { + inherit (pythonPackages) twisted; + }; + byacc = callPackage ../development/tools/parsing/byacc { }; casperjs = callPackage ../development/tools/casperjs { };