Add Or Edit Systems

Add or edit Systems from the Systems Manager page. Users can also duplicate a system.

Use a System to set up and run Builds.

Add or Edit a System

To add or edit a System:

  1. Add or edit:
    1. Add:
      1. By + New:
        1. Go to + New > Other > System.
      2. By System Manager:
        1. Go to Environment > Systems.
        2. Click + New System.
      3. Under the Information panel:
        1. Type the Name. (Mandatory field.)
    2. Edit: Click a blue-linked System Name to edit a System.
      1. To edit the Name:
        1.  Hover your mouse cursor over the Name until the pen appears.
        2. Click the Name and starting typing to edit.
  2. Under the Information panel:
    1. Click to edit the Description.
  3. Under the Additional Information panel:
  4. Under the Recent Builds panel:
    Enable Builds to see this panel.

    The most recent 25 Builds are displayed. To see all the Builds for this System, go to Environment > Builds and filter by System.

    1. Add a manual Systems Build (when the System has no Jenkins jobs).
    2. Add an automated Systems Build (when the System has Jenkins jobs).
    3. Add Builds Via APIs.
    4. The Build Status updates in real-time when an automated Build is run.
    5. Click a blue-linked Build # to open and edit a Build:

      1. Click the pen icon to edit the Build’s name.
      2. Deployment History panel lists the data every time a Build is linked to a new Environment, including:
        • Trigger From which shows whether the Build has been run from a TECR or Deployment Plan Activity.
        • Time Between Deployments which shows the time elapsed between the deployments.
      3. Job Execution History panel lists data from each time the Jenkins jobs in the Build have been executed.
      4. Click to edit:
        • Build Tag.
        • Branch Name.
        • Build Status.
        • Linked Release.
      5. Click to view the Change Log:
        • Automated Builds: If logging has been enabled, the log contains
          • Basic data from Plutora, such as when the Jenkins job was successfully triggered:
          • The console output log commit information from Jenkins. If this log contains sensitive information, such as passwords, it can be disabled.
        • Manual Build: The log contains only basic data from Plutora, such as when the Jenkins job was successfully triggered.
      6. Click Save & Close.
  5. Under the Automated Jobs panel:

    1. View a list of the most recent Jenkins builds for all the Jenkins jobs associated with the System:
      • Jobs cascade down to the System’s Environments and those Environments’ TECRs.
      • Jobs are run from the top of the list to the bottom. Reorder jobs by dragging and dropping.
      • The version number produced by the top-listed job is used as the version number in the Environment, but only if all jobs run successfully.
    2. Add or edit Jenkins jobs:
      Jobs must be enabled in Jenkins Customization before they can be added to a System.

      1. Click + New Job.
      2. Jenkins is currently the only Application that can be selected.
      3. Select a Jenkins Instance.
      4. Select a Job.
      5. Select Approved Users:
        • If selected, only these users or User Groups can run the job.
        • If no user is selected, anyone with permission to edit the System can run the job.
      6. Select Job Type.
      7. Click Save & Close.
  6. Under the Details panel:
    1. Click the Status toggle switch to label the System as active or inactive. (Mandatory field.)
    2. Type a Vendor. (Mandatory field.)
      Vendors now appear as a column on the Systems page and the Systems XLS export file.
    3. Click Portfolio Association and select from the tree menu. (Mandatory field.)
    4. Manage Aliases:
      Aliases are alternative names for the System. They must be unique and cannot be the same as the System’s Name.

      1. Add an Alias:
        System Aliases can now be managed through Plutora’s API.

        1. Type an Alias in the Alias field.
        2. Press the Enter key on your keyboard.
      2. Delete an Alias:
        1. Click the X.
  7. Under the People panel:
    1. Manage Stakeholders:
      1. Manage Stakeholders:
        1. Add a Stakeholder:
          1. Click the circle with a plus sign. 

            When users are added as stakeholders more than once, they will appear as a stakeholder only once with all their Roles and Stakeholder RACI Roles merged.
            For example, if a stakeholder with Role A and all the RACI Roles was added again with Role B and no RACI Roles, the stakeholder would appear only once with Roles A and B and all the RACI Roles.

          2. Select a User Name or a User Group from the Name or User Group drop-down menu.
          3. Select a role from the Role(s) drop-down menu.
            Administrators can add roles using the Stakeholder Role Customization.
          4. The Email field is not editable.
          5. Click to select a Stakeholders RACI checkbox.
          6. To save the Stakeholder and add another Stakeholder: Click Save & Add New.
          7. To save the Stakeholder and close: Click Save & Close.
          8. The Stakeholder will have a red exclamation mark until the System has been saved.
        2. Delete a Stakeholder:
          1. Hover your mouse cursor over the Stakeholder.
          2. Click the delete icon. 
    2. Once there are Stakeholders saved, click the contact Stakeholders button:

      1. Choose one of the following:
        1. To send the email to all the Stakeholders click to select the Send to all Stakeholders radio button.
        2. To select from a list of Stakeholders who will receive the email, click to select the Send to selected Stakeholders radio button:
          1. Click the combo box and click to select the checkboxes of the Stakeholders you would like to email.

            Stakeholders are listed from the selected System, all related Environments, and all related Environment Groups.   
      2. Type a single email address into the From field. (Mandatory field.)
      3. Type an email Subject. (Mandatory field.)
      4. Type an email Body. (Mandatory field.)
      5. Click Send.
    3. Click Environment Booking Approvers and select users or User Groups who will be capable of approving bookings for Environments linked to this System:
      • Any user in the group can approve or reject bookings.
      • Only one user in the group needs to approve or reject bookings.
      • If no user or User Group have been selected, anyone with the Approve Environment Allocation in Scheduler user permission can approve a booking.
  8. Under the System Dependencies panel:

    1. Click the pen icon to open the System Dependencies pop up.
      Click Save & Create New first if adding a new System. 
    2. Drag and drop Systems into Upstream System Dependencies or Downstream System Dependencies:
      Now, drag and drop UI styling is consistent throughout Plutora. Where an item can be dragged and dropped, the mouse cursor turns into a four-headed arrow. Areas where the item can be dropped will be marked Drop Here and will be highlighted in blue, with a darker blue dotted border.

      • Upstream and Downstream Dependencies are consistent across all Systems.
      • If System A is added as an Upstream Dependency in System B, if you open System A, System B will be marked as a Downstream Dependency.
      • Circular references are no longer possible. Selected Systems will not appear for selection in the left-hand panel.
  9. Click:
    1. New System: Save & Create New. (If you haven’t clicked it already. Otherwise, click Save.)
    2. Edited System: Save.


View Audit History

To view Audit History, open a System, then select History from the Action menu.

To see more information about Audit History, click here.


Copy URL to Clipboard

Systems page no longer has a Copy URL to Clipboard button because the URL appears in the browser location or address bar.


Back to the top arrow

Be the first to find out about new features. Subscribe to the Release Notes email. Subscribe Now
Updated on May 24, 2021

Related Articles