Plutora Feature Release Notes For Early October 2020

New Features

Search for Release Owner

Now, for Release Manager:

• The Owner column:
  • Has a grid column filter.
  • Can be filtered using the Query Builder.

Deployment Status

Now:

• Enterprise, Project, and Independent Releases have consistent Deployment Statuses for Impacted Systems:
  • Completed
  • Pending
  • Rejected
  • Rollback.
• Deployment Status is visible in the grid in the Systems tab under Impacted Systems. If more than one deployment is present, only the worst status will appear in the grid.

Jenkins Enhancements

Now:

• For Systems:
  • Jenkins jobs are added to Systems instead of Environments. Environments inherit Jenkins jobs from their System.
  • Approved Users, in the form of individual users and User Groups, can be added to Jenkins jobs:
    • If present, only they can run the job.
    • If not present, anyone who can edit the System can run the job.
• For Environments:
  • Jenkins jobs are displayed under an Environment’s Automated Jobs tab.
  • View Execution History shows the history of the Environment.
• For TECRs:
  • Selected Jenkins jobs and parameter values can now be unique for each TECR.
  • After a job has been run, the status displays the last build status instead of Ready to Build.
    • If more than one job has been run at once, the most recently executed build statuses will be displayed. For example, Failed, even if some of the runs have been Successful.
  • View History shows only the history of the TECR’s jobs.

Environment Booking Blockouts

Now:

• Environment Booking Blockouts can be used to:
  • Allow better forecasting by displaying time periods in the Environment Schedule when an Environment or Environment Group cannot be booked.
  • Prevent bookings from being created during these time periods and display an error message or warning, unless the user has the Book Environments during Blockout permission.
• Users must select the Environment Booking category for a Blockout Period Type and use that Blockout Period Type when adding or editing a Blockout.
  • After selecting a Blockout Period Type with an Environment Booking category, users will be prompted to select the Environments and Environment Groups that will reject booking attempts for the duration of the Blockout.
• Users who lack the Book Environments during Blockout permission will not be able to book those Environments or Environment Groups during that time period or extend existing bookings into that time period for:
  • Enterprise, Project, or Independent Releases.
  • TEBRs (with or without a Release).
  • Duplicate Releases or TEBRs, and anywhere else bookings can be made or extended.
• Blockouts grid can now display Environment and Environment Group columns and can be filtered on these fields by Query Builder.
• For Environment Schedule:
  • If a Blockout with the Environment Booking category exists:
    • It will be displayed in the Environment and Environment Group views if Quick Filter’s Booking Blockout Period checkbox is selected.
  • In Environment Group view, TEBR in Tools by View has been renamed Requests. 
  • In the Quick Filter, under Group by, TEBR has been renamed Request Type.

Automatic System Inheritance Setup

Now:

• Release Managers can have a better understanding of the impacts related to their projects by allowing Systems to be inherited from:
  • Changes to Project or Independent Releases and via the API:
    • PUT /changes/{changeid}/deliveryReleases/{releaseID}
  • Child Project or Independent Releases to their parent Enterprise Release and via the API:
    • PUT /releases/{id}

Release Status Completed

Now:

• The Completed Release Status in Release Status Customization can have its Release Status End-State checkbox unchecked and deleted.

Continuous Delivery Pipeline

Now:

• Clicking on a version number opens a System Details panel only.
• The build execution history pop up will no longer be displayed.