Page History

...

JS7 scheduling objects are transparently managed in a Git repository via the JOC Cockpit GUI 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.

The JOC Cockpit holds a number of local repositories inside the local and rollout sub-folders of the JETTY_BASE/resources/joc/repositories folders. Each top-level folder in the JOC Cockpit inventory can be mapped to a Git repository. 

• The local repository for a 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 inventory operation) and from the remote Git repository (pull Git operation).
• The remote Git repository is updated from the local repository using the Git push Git operation.
• The JS7 - Cleanup Service removes any local repositories if the top-level folder no longer exists, i.e. if a top-level folder was dropped from JOC Cockpit.

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

• The JOC Cockpit supports use of Git compliant servers to manage remote repositories such as as GitLab, GitHub.
• The JOC Cockpit makes Cockpit makes use of a Git CLI Client that has to be provided by the user and has to be accessible to the run-time account of the JOC Cockpit daemon or Windows Service.

...

This operation stores objects managed with the JOC Cockpit database to in the file system which holds the local Git repository.

...

• Filter
  • Filters can be applied to select only draft objects 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 including workflows, job resources etc.
    • Objects released within JOC Cockpit include calendars and schedules.
• Handle recursively
  • The checkbox allows selection of a top-level folder to include any sub-folders and objects.
• Tree
  • The tree allows navigation of included folders and objects for selection. Individual selection Selection of individual objects requires the 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 the Settings section.

...

Git credentials are managed from a the user account's profile, see JS7 - Profiles - Git Management..

...

A Git repository can be cloned to a new top-level folder in the JOC Cockpit inventory and it can be cloned to an existing top-level folder.

To clone The operation for cloning to an existing top-level folder the operation is available from the respective relevant top-level folder with the using the Repository->Local|Rollout->Git->Clone action menu item like this:

To clone The operation for cloning to a new top-level folder, starting from the root folder, '/ the operation ' is available from the Repository->Local|Rollout->Git->Clone action menu item like this:

...

• Git URL: The URL git@github.com:sos-berlin/js7-demo-inventory-rollout-test.git from the example includes the following parts:
  • git@: The git@ prefix is a constant value used for ssh access to the git server.
  • github.com: The hostname and optionally port - separated by a colon - of the Git Server.
  • :sos-berlin: The owner account of the repository - starting with a colon.
  • /js7-demo-inventory-rollout-test: The path of the repository.
  • .git: The .git suffix is a constant value.
• Git URL for HTTP(S) access: The URL https://github.com/sos-berlin/js7-demo-inventory-rollout-test.git contains similar parts.  
  • https://:  The The protocol to be used to use for access to the git server (HTTP or HTTPS, if available).
  • github.com: The hostname and optionally port - separated by a colon - of the Git Server.
  • /sos-berlin: The owner account of the repository - starting with a slash.
  • /js7-demo-inventory-rollout-test: The path of the repository.
  • .git: The .git suffix is a constant value.
• Folder Name: The input field is available if the clone operation is invoked from the root folder '/' to clone to a new top-level folder. The name of the new top-level folder has to be specified.

After cloning, a popup window presents the will present a feedback message like this:

After cloning, the tree in the left panel includes will include the top-level folder to which the repository has been cloned.

In order to populate the JOC Cockpit inventory top-level folder the , the Repository->Local|Rollout→Update from repository action menu has to be invoked like this:

...

Before pushing changes to a Git repository, such changes have to be stored to the local repository by use of the using the Repository->Local|Rollout->Store to repository action action menu item.

To push changes to scheduling objects from a local repository to the remote Git repository the Repository->Local|Rollout->Git->Push action menu item has to be invoked like this:

...

In response to the push operation a popup window appears will appear with a feedback message like this:

...

Anchor
git_pull git_pull

Pull from remote Git Repository

To pull changes from a remote Git repository to the local repository the The Repository->Local|Rollout->Git->Pull action menu item is available.used to pull changes from a remote Git repository to the local repository as shown below:

In response to the pull operation a operation, a popup window appears will appear with a feedback message like this:

...