Commit Graph

316 Commits

Author SHA1 Message Date
Allan Espinosa
491007d0a1 jenkins: 1.647 -> 1.649 2016-02-22 00:37:07 -06:00
zimbatm
b58e26dbf6 cide: init at 0.8.1 2016-02-21 21:11:35 +00:00
Allan Espinosa
60c7bd1237 jenkins: 1.643 -> 1.647 2016-02-17 20:45:01 +01:00
Augustin Borsu
170f91a249 jenkins ci: 1.638 -> 1.643 2015-12-23 15:47:11 +01:00
Domen Kožar
704c8bab41 buildPythonPackage: fix standalone applications using it 2015-11-21 21:44:12 +01:00
Bjørn Forsman
30313d5c6e jenkins: 1.637 -> 1.638 (important security fixes)
I fat fingered the previous update, *this* is the real important
security updates:

https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11
2015-11-12 13:40:09 +01:00
Bjørn Forsman
7a1c4ab324 jenkins: 1.636 -> 1.637 (security fixes)
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11
2015-11-12 13:34:44 +01:00
Bjørn Forsman
eeced1bc51 jenkins: 1.633 -> 1.636 2015-11-02 10:39:16 +01:00
Utku Demir
57ad847982 jenkins: 1.631 -> 1.633 2015-10-14 21:21:12 +03:00
Bjørn Forsman
f35de8ea64 jenkins: 1.594 -> 1.631 2015-09-30 17:25:39 +02:00
Benjamin Staffin
3a371528bb New package: jenkins-job-builder 2015-05-03 10:58:17 -07:00
宋文武
f40a613577 jenkins: update to 1.594 2014-12-18 14:30:14 +08:00
Bjørn Forsman
1a5501889c jenkins: update to latest (v1.579) 2014-09-08 17:08:05 +02:00
Bjørn Forsman
af2334912a jenkins: expression cleanup
* Include version number in package name
* Remove trailing dot in meta.description
* Simplify meta by using "with stdenv.lib;"
2014-09-08 17:05:15 +02:00
Corey O'Connor
4b6e67f6c4 add platform and license to package metadata. 2014-03-13 13:01:49 -07:00
Corey O'Connor
9b79d5b298 Add jenkins continuous integration server and user.
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.
2014-03-13 13:01:49 -07:00