Setting Up Jenkins Integration

Jenkins is a cross-platform, open source build automation tool for delivery pipelines. Whether your goal is continuous integration or continuous delivery Jenkins can help automate it.

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:

  1. Open Jenkins.
  2. Click a blue linked job Name.
    Click to open an item in Jenkins red arrow
  3. Click Configure.
    Click Configure in Jenkins red arrow
  4. Click to select the Trigger builds remotely (e.g., from scripts) checkbox.
    Build Triggers Jenkins red arrow
  5. Type an Authentification Token.
  6. Click Save.

To enable Jenkins Integration:

  1. Go to Settings > Customization.
  2. Click Jenkins.
  3. Click to select the Enable Jenkins Integration checkbox.
    Jenkins integration customization red arrow
  4. Type the Jenkins URL.
  5. Type the Login.
  6. Type the Password.
  7. Click Fetch Jobs. The Job Names column should populate with jobs.
  8. Type the job token into the job’s Job Token field.
  9. Click Submit.

  1. Go to Environments > Environments.
  2. Click to open an Environment.
  3. Click the new tab called Release Automation.
  4. Click to select the Enable checkbox.
    Release Automation tab red arrow
  5. Select Jenkins from the 1. Select Technology drop down menu. Jenkins is currently the only technology available. Plutora will be adding more soon!
  6. Select the job name from the 2. Select Job drop down menu.
  7. Click Save.
  8. Click the Details tab.
    Details tab of Environments pop up red arrow
  9. Click to select a component under the Technical Specs and Configuration panel.
  10. Click Update on Build.
    Select and click update on build red arrow
    The component’s icon becomes a Jenkins icon.
    Jenkins icon red arrow
    The component’s Version will contain a build version number when a build is initiated.Version number produced by Jenkins
    Only one component can be active with Jenkins at a time.
  11. Click Save & Close.

  1. Go to Environments > Environment Requests.
  2. Click the TECR tab.
  3. Click a blue link to open a TECR.
    Environments in the Progression Path of the TECR will contain the Jenkins icon.
    TECR Environments containing Jenkins
    The buttons below the Jenkins icon have the following functions:
    Jenkins in a TECR environment
    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.
    Jenkins logs
    – Build: Starts the build.
  4. Click Build to build a new environment, to your specifications, on the fly!
    Jenkins build success
  5. 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.)

Back to the top arrow

Was this article helpful?

5 found this helpful.