...

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

• The local repository for a JS7 roottop-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 roottop-level folder no longer exists, i.e. if a roottop-level folder is dropped from JOC Cockpit.

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

• JS7 supports use of Git compliant servers to manage remote repositories such as GitLab, GitHub.
• JS7 makes use of a Git CLI Client that has to be provided by the user.

Basic Inventory Operations

Any inventory operations are based on root 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 the action menu Repository to select objects for local and rollout repository use like this:

...

• 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 top-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.

...

• Handle recursively
  • This checkbox allows to select from a root top-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.

...

• Handle recursively
  • This checkbox allows to select from a root top-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.

...