You're reading the documentation for a version of ROS 2 that has reached its EOL (end-of-life), and is no longer officially supported. If you want up-to-date information, please have a look at Iron.
How to setup a Windows Jenkins node
Table of Contents
See this older (private) document for previous instructions:
We use the normal Windows 10 version, not the enterprise, but other than that we just do system updates and use default settings otherwise.
Follow our Windows “from source” installation instructions.
Ensure that the git installation has a (garbage) email and name, otherwise it will fail if it ever needs to make merge commits when merging branches with “master”.
Note that this must be done in the context of the “System” user, which is what the Jenkins service will run as.
Become the system user by using
Download it from: https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
Then extract the zip, open a command-prompt as administrator, and run:
psexec -i -s cmd.exe
This is all pieced together from a couple of pages here:
Once you are the system user, set the git config:
> git config --global user.email "email@example.com" > git config --global user.name "nobody"
Download and install Java from Oracle:
Go to https://ci.ros2.org and select: Manage Jenkins -> Manage Nodes -> New node
Copy an existing node and choose a working Windows node (at the time of the writing Windshield or Portable), fill in all the description fields, set the label to “windows slave” and save.
Hit the “launch” button to download the “Java Web Start App” and save it on the desktop.
Open an Administrator
cmd.exe and then:
> cd \path\to\downloaded\file > .\slave-agent.jnlp
Once open, go to File->”Install as a Service”. Then you can close the slave agent as it will start on boot.
Download and install Connext binary:
Make sure to also install the security plugins.
Download the license file from our private GitHub repository:
Run the RTI launcher application and point it at the license file.
Finally, just need to reboot to be sure the node comes online as expected.