Ticket #1862 (closed enhancement: fixed)
Opened 2013-05-10T15:00:10-05:00
Last modified 2013-05-10T15:03:05-05:00
Make skynet a restricted Jenkins node
Reported by: | dscho | Owned by: | dscho |
---|---|---|---|
Priority: | major | Milestone: |
|
Component: | Server Admin | Version: | |
Severity: | serious | Keywords: | |
Cc: | curtis | Blocked By: | |
Blocking: | #1743, #1857, #1860 |
Description
To let Jenkins handle the backups, including reports when the backup failed, and also to make it possible for a Jenkins job to monitor the disk usage of http://sites.imagej.net/, we need to make skynet a Jenkins node. It should only be used for jobs bound to said node, of course.
Change History
comment:1 Changed 2013-05-10T15:03:05-05:00 by dscho
- Status changed from new to closed
- Resolution set to fixed
I added a new user, jenkins-node, made /var/jenkins/ its home, then created a new SSH key pair on dev and added the public key to the jenkins-node account on skynet. Then I cloned the configuration from the node running on server, changing description, label, name and location of the private key. It is online now.