nixlib - Alyssa's collection of Nix expressions

	Commit message (Collapse)	Author	Age
*	all tests: added meta.maintainers section	Joachim Schiele	2015-07-12
\|
*	nixos/tests/jenkins: increase timeout to 6 minutes	Bjørn Forsman	2015-02-10
\| \| \| \|	Fixes the test failure, at least on my system.
*	nixos: munin/jenkins: specify timeout correctly	Domen Kožar	2014-09-28
\|
*	nixos: increase timeout for jenkins/munin systemd services	Domen Kožar	2014-09-27
\|
*	Increase systemd timeout on Jenkins and Munin tests	Eelco Dolstra	2014-09-05
\| \| \| \| \| \| \|	These were timing out a lot. http://hydra.nixos.org/build/13991108 http://hydra.nixos.org/build/13991107
*	name nixos tests, close #3078	Florian Friesdorf	2014-06-28
\|
*	resolve issue #2308	Corey O'Connor	2014-05-13
\|
*	Make it easier to run the tests	Eelco Dolstra	2014-04-14
\| \| \| \| \| \| \| \| \| \| \|	You can now run a test in the nixos/tests directory directly using nix-build, e.g. $ nix-build '<nixos/tests/login.nix>' -A test This gets rid of having to add the test to nixos/tests/default.nix. (Of course, you still need to add it to nixos/release.nix if you want Hydra to run the test.)
*	Fix tests broken due to the firewall being enabled by default	Eelco Dolstra	2014-04-11
\|
*	remove users.jenkins config start on slave config.	Corey O'Connor	2014-03-13
\| \| \| \| \| \|	Uses standard NixOS user config merging. Work in progress: The slave config does not actually start the slave agent. This just configures a jenkins user if required. Bare minimum to enable a nice jenkins SSH slave.
*	Add jenkins continuous integration server and user.	Corey O'Connor	2014-03-13
	By default the jenkins server is executed under the user "jenkins". Which can be configured using users.jenkins.* options. If a different user is requested by changing services.jenkins.user then none of the users.jenkins options apply. This patch does not include jenkins slave configuration. Some config options will probably change when this is implemented. Aspects like the user and environment are typically identical between slave and master. The service configs are different. The design is for users.jenkins to cover the shared aspects while services.jenkins and services.jenkins-slave cover the master and slave specific aspects, respectively. Another option would be to place everything under services.jenkins and have a config that selects master vs slave.