Now, Plutora integrates with Jenkins, to bring you easy-to-set-up, one-click environment creation on the fly.
To create an environment with a single click, using Plutora and Jenkins:
To enable Jenkins Integration:
- Go to Environments > Environments.
- Click to open an Environment.
- Click the new tab called Release Automation.
- Click to select the Enable checkbox.
- Select Jenkins from the 1. Select Technology drop down menu. Jenkins is currently the only technology available. Plutora will be adding more soon!
- Select the job name from the 2. Select Job drop down menu.
- Click Save.
- Click the Details tab.
- Click to select a component under the Technical Specs and Configuration panel.
- Click Update on Build.
The component’s icon becomes a Jenkins icon.
The component’s Version will contain a build version number when a build is initiated.
Only one component can be active with Jenkins at a time.
- Click Save & Close.
- Go to Environments > Environment Requests.
- Click the TECR tab.
- Click a blue link to open a TECR.
Environments in the Progression Path of the TECR will contain the Jenkins icon.
The buttons below the Jenkins icon have the following functions:
Status: Shows the green status bar if a build is taking place. Shows No build in progress if the build has finished or not started.
View Log: Opens a pop up with the log file. The log file shows the last build and whether it was successful or not.
– Build: Starts the build.
- Click Build to build a new environment, to your specifications, on the fly!
- Once the build is complete, Jenkins will update the Environment component’s version number.
Currently, data created by Jenkins, such as the build version number, will only exist in Plutora if triggered by Plutora. Any changes made in Jenkins alone will not flow back into Plutora. (Unless the user is viewing the versions in the Pipeline.)
Was this article helpful?
5 found this helpful.