From 4044ac12863b96b9e1983a95f790b50b5039e287 Mon Sep 17 00:00:00 2001 From: makefu Date: Mon, 24 Jul 2017 10:49:31 +0200 Subject: mv buildbot{-classic,} --- .../simple/buildbot-slave-classic/default.nix | 60 ++++++++++++++++++++++ 1 file changed, 60 insertions(+) create mode 100644 krebs/5pkgs/simple/buildbot-slave-classic/default.nix (limited to 'krebs/5pkgs/simple/buildbot-slave-classic/default.nix') diff --git a/krebs/5pkgs/simple/buildbot-slave-classic/default.nix b/krebs/5pkgs/simple/buildbot-slave-classic/default.nix new file mode 100644 index 00000000..83da05c3 --- /dev/null +++ b/krebs/5pkgs/simple/buildbot-slave-classic/default.nix @@ -0,0 +1,60 @@ +{ stdenv, pkgs, python2Packages, fetchFromGitHub, coreutils }: + +python2Packages.buildPythonApplication (rec { + name = "buildbot-slave-classic-2017-07-23"; + + src = pkgs.buildbot-classic.src; + + postUnpack = "sourceRoot=\${sourceRoot}/slave"; + + propagatedBuildInputs = with python2Packages; [ twisted pathlib ]; + + # 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 = with stdenv.lib; { + homepage = http://buildbot.net/; + + license = stdenv.lib.licenses.gpl2Plus; + + 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. + ''; + maintainers = with maintainers; [ bjornfor ]; + platforms = platforms.all; + }; +}) -- cgit v1.2.3