Many teams use Jenkins for continuous integration, but need to coordinate the deployment of builds through environments. They will use Jenkins to create those builds, and pass new builds to IBM UrbanCode Deploy for deployment. Optionally, builds may be automatically deployed to a test environment.
View the Jenkins Plugin and click Download
- Open the website of your Jenkins server
- Click on Manage Jenkins
- Click on Manage Plugins
- Open the Advanced tab
- Click on Browse In the section Upload Plugin
ibm-ucdeploy-publisher.hpi. Click Upload
- Restart your Jenkins server in order to see the new plug-in by using
- Verify that the plug-in is installed and enabled
- Click on the link Manage Jenkins
- Click on Configure System
- Add a profile for your UrbanCode Deploy serverFor example, where
- Profile Name is
- IBM UrbanCode Deploy URL is
- User name is
jenkins (note: especially because the post-build action may trigger a deployment, you should only use an account that can not deploy to secure environments like production. Creating a service account like "jenkins" within UrbanCode Deploy is recommended.
- Password is
UrbanCode Deploy user's password
- Profile Name is
- Click Test connection to verify the configuration and click Apply
- Configure the post-build actions for each job.
- Select the task Publish artifacts to IBM UrbanCode Deploy in the section Post-build Actions
- Select the following options:
- Click Save
- Click on the button Build Now
If a post-build action is not appropriate for your team, or you want to push artifacts from a single build into multiple components, you have some other options.
- Use the command line client as part of your build to push new versions.
- Deliver each component to an alternate repository that UCD is monitoring such as a file system drop area, Maven repo or Rational Asset Manager.