...

• 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 for JS7 - Rollout of Scheduling Objects, see . See the scenarios and use cases from in the JS7 - Git Repository Interface article.
• The sections below sections explain the use of the operations for Git repositories that available from the JOC Cockpit GUI. For automation see JS7 - How to rollout from test to prod environments in a CI/CD pipeline.
• Availability of Git integration is provided along with the following JS7 releases:

  • Display feature availability
    StartingFromRelease 2.2.0

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1216

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1217

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1144

  • Display feature availability
    StartingFromRelease 2.3.0

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1218

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1219

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1213

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1214

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1215

...

• 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: Scheduling Object Mappings.
• For Settings for each scheduling object type settings determine if this whether they 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

...

JS7 scheduling objects are transparently managed in a Git repository via the JOC Cockpit GUI that makes use of and using 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 /local and /rollout subfolders of the JETTY_BASE/resources/joc/repositories folders subfolder /local and /rollout. Each top-level folder in the JS7 Configuration view can be mapped to a Git repository. 

• The local repository for a JS7 top-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 using the push operation.
• The JS7 - Cleanup Service removes any local repositories if the JS7 top-level folder no longer exists, i.e. if a top-level folder is has been dropped from JOC Cockpit.

The JS7 JOC Cockpit can be used to interface with remote Git repositories to store and to rollout its scheduling objects such as workflows and jobs.

...

Basic Inventory Operations

Any All inventory operations are based on top-level folders that are mapped to Git repositories, see JS7 - Git Repository Interface, chapter: Folder Mappings. Basic inventory operations do not require a Git Client but are performed directly by JOC Cockpit.

The JOC Cockpit GUI offers provides the Repository action menu Repository to select for selecting objects for local and rollout repository use like thisas shown in the diagram below:

Operations offered by the above The operations available in the action menu items are explained with described in the following chapterssections.

Store Objects to local Repository

This operation is performed to store stores objects managed with the JOC Cockpit database to the file system that which 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 thisas shown in the next diagram:

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

Explanation:

• Filter
  • Filters can be applied to select Draft only 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 to Agents include for example workflows, job resources etc.
    • Objects released within JOC Cockpit include for example calendars and schedules.
• Handle recursively
  • The checkbox allows to select from selection of a top-level folder any included to include any sub-folders and objects.
• Tree
  • The tree allows to navigate navigation of included folders and objects for selection. Individual selection of objects requires the Handle recursively checkbox to be unchecked.
  • The Object types offered, such as Workflows, Resource Locks etc., depend on the settings for the object type, : see chapter the Settings section.

Update Objects from local Repository

This operation is performed to update updates the JOC Cockpit database from objects in the file system that which 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 thisas shown in the next diagram:

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

Explanation:

• Handle recursively
  • This The checkbox allows to select from selection of a top-level folder any included to include any sub-folders and objects.
• Tree
• The Object types offered, such as Workflows, Resource Locks etc., depend on the settings for the object type, : see chapter the Settings section.

Delete Objects from local Repository

This operation is performed to delete deletes objects from the file system that which 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 thisas shown in the next diagram:

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

Explanation:

• Handle recursively
  • This The checkbox allows to select from selection of a top-level folder any included to include any sub-folders and objects.
• Tree
• The Object types offered, such as Workflows, Resource Locks etc., depend on the settings for the object type, : see chapter the Settings section.

Further Resources

• JS7 - Git Repository Interface
• JS7 - Rollout of Scheduling Objects

...