- Native API
- Variables management
- Release & package deployment:
Next, you need to go to Jenkins' system config screen to tell Jenkins where's your BuildMaster resides. I have found that I need to configure it for NTLM authentication on our network otherwise my account gets locked out. Clicking the "Test Connection" button a few times will confirm whether this is required or not.
Lastly, you need to add a couple of steps to your Jenkins job. Because the Release and Build numbers could be required by several build and post-build actions selecting the application and has been separated from the trigger build action.
To deploy the build to the first environment ensure that you have the post-build step action "Auto-Promote Build to the Next Environment" set in BuildMaster.