Introduction The Environment Schedule page allows users to find and fix conflicting Environment Bookings by providing four different views from the View drop-down menu: Environment View: Environment Bookings and TECRs by Environment. Environment Group View: Environment Bookings and TECRs by Environment Group. Release View: Environment Bookings and TECRs by Release and their Phases. Overview: Environment Bookings
Introduction Environment Impact Matrix gives you a graphical view of bookings and shows whether they are Approved, Pending or Rejected against Releases. Pre-requisite You must have ‘View Impact Matrix’ user permission. Navigation Environment > Impact Matrix Environment Impact Matrix Layout a: Filter and view options b: Releases with implementation date
Introduction The Environment Map page displays a selected Environment Group and its connections. Pre-requisite You must have the ‘View Map’ user permission. Navigation Environment > Map Access Environment Map Navigate to Environment > Map and select an Environment Group from the drop-down. Then click . Administrators can prevent users from
Introduction Environments represent each instance of a System that you have within your organization. For example, if you have ‘System 1’ and you have an individual instance for DEV, SIT, UAT, STAGE, and PROD. This would be represented by 5 individual Environments and linked to the same System 1. Environment Manager
Introduction Environment Stack displays an interactive diagram of Environments. You can view the technical specs of an Environment and do a side-by-side comparison between the tech and specs of different Environments. Pre-requisite You must have the ‘View Stack’ user permission. Navigation Environment > Stack Access Environment Stack Navigate to Environment
Introduction Systems in Plutora represent the applications and microservices that your organization is responsible for in terms of ongoing development and operational support. This may also include third party vendor applications that you use internally or as part of the services you provide for your customers. Capturing the details of
Introduction Continuous Delivery Pipeline displays the Environment Groups that have been booked for a selected Release and allows users to track Systems and their version numbers within each Environment Group from development to production. For example: If a company’s Development, Testing, UAT, Preproduction, and Production areas each had an Environment Group,
Introduction Health Check Dashboard provides a view of the health of the selected Environments. Click an Environment to see the health of the Environment over the past 24 hours and 7 days and any associated TECRs and TEBRs. Any health status recorded in Plutora will only be valid for 7
Introduction As applications are broken down into smaller components and microservices that can be built and deployed independently, the Release Management process needs to track various CI/CD pipelines that are doing all of the builds, deployments, and even some of the automated testing. Plutora’s Builds entity provides visibility and tracking of build
Introduction Plutora Environment Management enables you to visualize, book, schedule, and manage any contention of your non-Production environments. It also provides environment maintenance, as well as Change & Configuration Management functions. Here, you can add and maintain builds, book environments (TEBR and TECR) and view Environment Schedules, CI/CD Pipeline, and