You can choose to initialize the build host through Pipelines (Auto) or run the initialization scripts yourself (Manual). Initialization through Pipelines requires you to grant SSH access. If you do not want to grant SSH access for some reason, select Manual as the node initialization type.
All Windows nodes must be manually initialized.
When initializing a Windows node, the script should be run in PowerShell as an Administrator.
To initialize the node through Pipelines:
Enter the SSH port for your build host. This is usually port 22, but is configurable.
Copy the command shown and run it on your build host. This will allow us to run initialization scripts on your node.
Check the checkbox to confirm that you have run the command on your node and click Save Node.
You will be redirected to a page showing you the console log as your node is initialized.
When your node is ready, the status indicator for the node will turn green. Your node is now ready to pick up steps for your pipelines.
GCP CentOS VM
In a CentOS VM on Google Cloud Platform, you must enable SSH root login (which is disabled by default) to perform an auto-initialize. This requires you to:
Open the file
/etc/ssh/sshd_configand update the
To enable the above changes, restart the sshd systemd service by executing
systemctl restart sshdon the VM
To run the initialization scripts yourself:
Click Save and Generate initialization scripts to generate the script.
Click Download initialization scripts to download the script. Copy it to your build machine, make sure the file is executable, and run it.
Your node status will automatically show green at this point. However, there is no way of verifying that the node was in fact successfully initialized so you will need to make sure this was the case by triggering a job.