JS7 JobScheduler

Space shortcuts

Page tree

Introduction

JOC Cockpit offers managing changes to inventory objects such as workflows

The above operations will be applied to objects assigned the change. A change includes the objects added by the user and any dependencies referencing the object or being referenced by the object, see JS7 - Inventory Object Dependencies.

This allows a number of users to work on inventory objects in parallel and to assign their objects to different changes. Later deployment/export/rollout operations can be performed individually per change.

FEATURE AVAILABILITY STARTING FROM RELEASE 2.7.4

Managing Changes

The top menu of any JOC Cockpit page offers the administrative menu with the Manage Changes menu item.


Selecting the Manage Changes menu item displays the list of available changes like this:


When adding or updating a change, a popup window will be displayed like this:

Explanations:

  • The name of a change is a unique identifier that can hold most common Unicode characters.
  • The status of a change is one of OPEN or CLOSED.
  • Changes have to be created before objects can be assigned.


When  clicking the icon from the list of changes, then the objects included with the change will be displayed like this:

Working with Changes

Most of the work is done in the Configuration -> Inventory view that offers to

  • add/remove objects to/from changes,
  • deploy objects in scope of changes,
  • export objects in scope of changes,
  • store objects to a Git repository in scope of changes.

Adding and removing Objects to/from Changes

In the Configuration -> Inventory view the tree panel for any scheduling object offers the Add to Change and Remove from Change action menu items like this:


A popup window willl be displayed that allows to select the change and that offers to add/remove the object to/from the change like tihs:

Checking Objects assigned to Changes

The Configuration -> Inventory view offers to display objects assigned a change by invoking the Change button like this:


A popup window will be displayed that allows to select the change and that will display related objects like this:

Deplyoing Changes

To deploy objects assigned a change, users invoke the deployment operation from the tree's action menu at folder level like this:


The operation will invoke a popup window that offers

  • to choose the deployment type from radio buttons that select objects individually, from folders and from changes,
  • to select the change for which deployment should be performed. When a change is selected then
    • objects assigned the change will be displayed.
    • objects that hold dependencies to the change will be displayed. Dependencies include Referencing Objects and Referenced Objects.

Users cannot unselect individual objects or dependencies for the reason that a change must be consistent and will include all objects to/from which dependencies exist.

Objects that are already in (blue) deployed status will not be deployed once more.

Exporting Changes

When exporting objects then users can select the operation at any folder level in the tree like this:


The operation will invoke a popup window that offers 

  • to choose the export type from radio buttons that select objects individually, from folders and from changes,
  • to select the change for which export should be performed. When a change is selected then
    • objects assigned the change will be displayed.
    • objects that hold dependencies to the change will be displayed if the Include Dependencies checkbox is checked. Dependencies include referencing objects and referenced objects.

Users cannot unselect individual objects or dependencies for the reason that a change must be consistent and will include all objects to/from which dependencies exist.


Storing Changes to Git Repositories

If JS7 - Inventory Git Integration is in place and an inventory folder is assigned a Git repository, then users can store inventory objects to the Git repository. To this purpose the tree's action menu can be invoked for the related inventory folder and operation: Git Repository -> local/rollout -> Store to Git Repository.


The operation will invoke a popup window that offers to select the change for which the operation should be performed. When a change is selected then

    • objects assigned the change will be displayed.
    • objects that hold dependencies to the change will be displayed if the Include Dependencies checkbox is checked. Dependencies include Referencing Objects and Referenced Objects.

Users cannot unselect individual objects or dependencies for the reason that a change must be consistent and will include all objects to/from which dependencies exist.

The objects and dependencies of a change will be stored to the Git repository like this:



Resources


  • No labels