Introduction

• The JS7 inventory holds scheduling objects such as JS7 - Workflows, JS7 - Calendars and Schedules etc. that are stored with the JS7 - Database.
• Users can integrate the JS7 inventory with Git repositories, see scenarios and use cases from the JS7 - Git Repository Interface article.
• The below sections explain use of operations for Git repositories available from the JOC Cockpit GUI.
• Availability of Git integration is provided along the following iterations:
  • FEATURE AVAILABILITY STARTING FROM RELEASE 2.2.0
    • JOC-1216 - Getting issue details... STATUS
    • JOC-1217 - Getting issue details... STATUS
    • JOC-1144 - Getting issue details... STATUS
  • FEATURE AVAILABILITY STARTING FROM RELEASE 2.3.0
    • JOC-1218 - Getting issue details... STATUS
    • JOC-1219 - Getting issue details... STATUS
    • JOC-1213 - Getting issue details... STATUS
    • JOC-1214 - Getting issue details... STATUS
    • JOC-1215 - Getting issue details... STATUS

Settings

The following JS7 - Settings are used for Git integration:

Explanation:

• Settings are used to determine which scheduling objects are considered local to an environment and which scheduling objects should be used for rollout to subsequent environments such as in a sequence dev => test => prod. For details see JS7 - Git Repository Interface, chapter: Configuration Object Mappings
• For each scheduling object type settings determine if this should be considered for local use or for rollout to a remote Git repository:
  • git_hold_workflows: see JS7 - Workflows
  • git_hold_resource_locks: see JS7 - Resource Locks
  • git_hold_file_order_sources: see JS7 - Job Resources
  • git_hold_notice_boards: see JS7 - Notice Boards
  • git_hold_script_includes: see JS7 - Script Includes
  • git_hold_job_resources: see JS7 - Job Resources
  • git_hold_calendars: see JS7 - Calendars
  • git_hold_schedules: see JS7 - Schedules

Git Repositories

JS7 configuration objects are transparently managed in a Git repository via the JOC Cockpit GUI that makes use of the JS7 - REST Web Service API. In addition, tools such as Git Extensions and Git command line clients can be used for repository operations.

JOC Cockpit holds a number of local repositories inside the JETTY_BASE/resources/joc/repositories folder. Each root-level folder in the JS7 Configuration view can be mapped to a Git repository. 

• The local repository for a JS7 root-level folder is created when a user performs the checkout or clone operation for the Git repository via JOC Cockpit.
• The local repository is persistent and is updated from the JOC Cockpit database (store operation) and from the remote Git repository (pull operation).
• The remote Git repository is updated from the local repository by use of the push operation.
• The JS7 - Cleanup Service removes any local repositories if the JS7 root-level folder no longer exists, i.e. if a root-level folder is dropped from JOC Cockpit.

Basic Inventory Operations

Any inventory operations are based on root level folders that are mapped to Git repositories, see JS7 - Git Repository Interface, chapter: Folder Mappings

The JOC Cockpit GUI offers the action menu Repository to select objects for local and rollout repository use like this:

Operations offered by the above action menu items are explained with the following chapters.

Store Objects to local Repository

This operation is performed to store objects managed with the JOC Cockpit database to the file system that holds the local Git repository.

When storing objects local to the environment via the Repository=>Local=>Store to repository action then a popup window is displayed like this:

When storing objects intended for rollout to other environments via the Repository=>Rollout=>Store to repository action then a popup window is displayed like this:

Explanation:

• Filter
  • Filters can be applied to select Draft objects only or objects that have been deployed or released.
    • Valid objects that match the schema for their object type.
    • Objects deployed to a Controller and Agents include for example workflows, job resources etc.
    • Objects released within JOC Cockpit include for example calendars and schedules.
• Handle recursively
  • This checkbox allows to select from a root level folder any included folders and objects.
• Tree
  • The tree allows to navigate included folders and objects for selection. Individual selection of objects requires the Handle recursively checkbox to be unchecked.
  • Object types offered such as Workflows, Resource Locks etc. depend on the settings for the object type, see chapter Settings.

Update Objects from local Repository

This operation is performed to update the JOC Cockpit database from objects in the file system that holds the local Git repository.

When updating objects local to the environment via the Repository=>Local=>Update from repository action then a popup window is displayed like this:

When updating objects intended for rollout to other environments via the Repository=>Rollout=>Update from repository action then a popup window is displayed like this:

Explanation:

• Handle recursively
  • This checkbox allows to select from a root level folder any included folders and objects.
• Tree
  • Object types offered such as Workflows, Resource Locks etc. depend on the settings for the object type, see chapter Settings.

Delete Objects from local Repository

This operation is performed to delete objects from the file system that holds the local Git repository.

When deleting objects local to the environment via the Repository=>Local=>Delete from repository action then a popup window is displayed like this:

When deleting objects intended for rollout to other environments via the Repository=>Rollout=>Delete from repository action then a popup window is displayed like this:

Explanation:

• Handle recursively
  • This checkbox allows to select from a root level folder any included folders and objects.
• Tree
  • Object types offered such as Workflows, Resource Locks etc. depend on the settings for the object type, see chapter Settings.