Closed dirk-thomas closed 5 years ago
The optimal way to deploy this today would be to manually place the config file in the Jenkins directory (since re-running puppet on master nodes is not a good idea #160) and restart Jenkins, then verify the config was loaded as expected.
I just edited the sections through the web interface.
PS: no need to reboot Jenkins for this. The change is effective immediately for every build started afterwards.
no need to reboot Jenkins for this. The change is effective immediately for every build started afterwards.
No the reboot was to make sure that the config loaded as expected from the file on disk. Since you made the change directly placing the config file manually is itself unnecessary.
Adds three sections for colcon specific output as it is already in use on ci.ros2.org: