Page History

...

• Workflows
• Locks
• File Order Sources
• Job Resources
• Boards
• Calendars
• Schedules

Configuration Items

Configuration Items are configuration properties for JOC Cockpit to function properly. The configuration items for JOC Cockpit to work with a Git repository are:

• repository_url
  • Url of the remote repository to connect to
• git_key
  • filename of the private key file
• git_token
  • access token for the Git access

Either git_key or git_token can be used exclusively.

GIT Repository Usage

The JOC web services execute a set of Git commands with the implementation of JGit.

...

• The JOC Cockpit database is the leading system holding the current configuration objects.
  • each JS7 instance is connected to its own database
  • each branch is connected to one JS7 instance
• each branch has its own versionmerges between branches have to be performed outside of JOC Cockpit
• force overwrite is possible

...

• The Git repository is used as a backup storage for JS7 configuration objects.
• Additionally, the Git repository is used to version stored JS7 configuration objects.
• The Git repository is used to rollout JS7 configuration objects to different JS7 instances (e.g. dev → test → prod).The

Git repository

...

Git repository usage:

• storage
• versioning
• rollout
• force overwrite

...

• The JOC Cockpit database is the leading system holding the current configuration objects.
  • each JS7 instance is connected to its own database
  • each branch is connected to one JS7 instance
• each branch has its own version
• merges between branches have to be performed outside of JOC Cockpit
• merges inside a branch are performed inside of JOC Cockpit but only force overwrite is supportedAs JOC Cockpit will not support Git merge operation each user (client) has to have his/her own JOC Cockpit instance.