menu
Jenkins Logo - White

Plutora integration with Jenkins

Enhance visibility and management of multiple release pipelines

Continuous integration practices regularly integrate new code into a shared codebase, producing testable builds at high velocity. For complex enterprise releases, as the build rate increases, the probability that any given change will impact multiple systems also increases. Test environments encompass a seemingly unlimited combination of components and architectures, and environment managers with hundreds, if not thousands, of test environments face the daunting task of maintaining accurate configurations. Executing tests on incorrect configurations or waiting for a test environment update wastes valuable resources that test teams can’t spare.

Plutora Environments provides a single resource to schedule, manage, and maintain test environments. The consolidated calendar shows where and when environments have been assigned, and centralized booking avoids conflicts that result in testing delays. Integration with Jenkins build automation enhances visibility and management of multiple release pipelines across the enterprise portfolio.

Integration Benefits

  • Trigger Jenkins builds with push-button ease
  • Track application status at each phase of the delivery pipeline
  • Incorporate Jenkins build versions into audit history
  • Increase visibility of fast moving CD pipelines at scale
  • Ensure stable test environments

Expedite the hand-off of new code from dev to test

Efficiently move binaries down the delivery pipeline

Plutora Environments supports faster production release cycles by managing test environments in a continuous delivery (CD) model. Test environment change requests initiate workflows, alerting environment managers to assign tasks, view status, and manage approvals. Plutora links Jenkins jobs to test environments, where a build is triggered on-demand to expedite the hand-off of new code from dev into test environments.

Consolidate reporting of multiple CD pipelines

Enterprise releases are a complex dance of moving parts. Multiple CD pipelines, multiple teams, and multiple developers working on a portfolio of applications generates a massive volume of release activity with limited visibility. Associating Jenkins build version numbers with test environments means test, release, ops, and business teams can track application status at each stage of the delivery pipeline.

Automatically incorporate component versions into audit history

Release audit history is automatically updated to include Jenkins build numbers assigned to each test environment over the course of a release. Establish traceability of where each change has been introduced, when versions were deployed, and what tests have been run.

Gain actionable insight of validation efforts

With both Jenkins and Jira integration, release managers gain visibility of fast moving CD pipelines at scale. Evaluate code quality by tracking defect backlog from phase to phase, view burndown rates, and sort defects by severity level. Schedule risk can be assessed using detailed dashboards, highlighting cycle time of each release phase and uncovering the barriers impacting progress.test plans.

Build stable test environments prior to new code deployment

Configurations for large, complex test environments are hard to maintain. Don’t force fast moving test teams to triage issues with environments when they should be focusing on code. With Jenkins integration, environment managers kick off a Jenkins job that leverages Chef and Puppet to configure and verify stability of the test environment prior to installing a new version of code.

Jenkins Integration - Progression
Build test environments on-demand.
Jenkins Integration - Configuration
Associate Jenkins build version numbers with test environments.

Ready to get started?
Get a personalized demo now