In our environment we use Jenkins CI for doing continuous integration of developer code. Setting up Jenkins server is plenty easy, but getting a node up and running has some road bumps. Here’s the process of getting any Windows7 desktop to perform builds of .NET4 code:
Install Required Build Tools
- Java JDK
- .NET 4 Framework
- SDK for Windows 7 & .NET4 (you only need the .NET Development components)
- Visual Studio 2010 Shell
- Visual Studio Web Development Projects
- All Microsoft Updates (be sure to use Microsoft Update, not Windows Update so that it’ll update all the components you just installed)
Once you’ve got all that installed, copy aspnet_merge.exe from C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\NETFX 4.0 Tools to C:\Program Files (x86)\MSBuild\Microsoft\WebDeployment\v10.0\
Create Node in Jenkins
Perform the following tasks from the new Jenkins slave
- Log into Jenkins, click Manage Jenkins, Manage Nodes, New Node
- Give it a name, and choose Dumb Slave
- Set up options for you new slave
- Description: optional
- # of executors: number of processors on the slave
- Remote FS Root: where Jenkins will store data (try to use a second drive/partition so you don’t accidentally fill up the boot partition.
- Labels: separate labels with spaces, useful for designating what projects can be compiled on each system – ex. “.NET4” “Java”, or for grouping systems. Jobs can be configured to use only nodes with appropriate labels.
- Usage: whatever you prefer
- Launch Method: Launch Slave agents via Java Web Start
- Availability: whatever you prefer
- Click the name of the slave you just created
- Click the Launch button
- Accept security warnings to run plugin
- A tiny window will pop up that says “Connected”
- Click File > Install as a Windows service if you want it to become available on restart.
The system should now appear in Jenkins as an online slave.