Page History

...

• Folders hold configuration objects such as workflows etc. and any level of sub-folders.
• Folders are the basic unit for JS7 - Default Roles and Permissions, for example, users can be granted access to specific folders only.
• Folders allow to perform bulk operations such as to deploy, to release, to remove and to rename configuration objects.

...

• user access:
  • users with JS7 access permissions to manage folders and to access the Git repository can manage configuration objects in JOC Cockpit and can commit, push, pull configuration objects to/from Git,
  • users with JS7 access permissions to manage folders but without access to the Git repository can manage configuration objects in JOC Cockpit,
  • users with JS7 access permissions to view folders do not require Git access.
• folder usage:
  • if a single Git repository should be used then all folders have to be available from a single root top-level folder,
  • for use with a number of Git repositories each folder maps to a different repository,
  • folders can remain without Git integration for local management and deployment.

...

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.

...