Page History

...

JS7 handles the below separation of Rollout Objects and Local Objects. JOC Cockpit offers to configure per object type which category is applied.

Rollout Objects

JS7 configuration object types that are independent from a specific environment (dev, test, prod) and that can be rolled out across environments include

• Workflows
• Locks
• File Order Sources
• Notice Boards
• Scripts

Such objects can be managed with JS7 in a way that allows to re-use the objects - without any changes - across rollout environments such as dev, test, prod.

Local Objects

• 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

Rollout Objects

JS7 configuration object types that are independent from a specific The following configuration object types typically hold values that are specific for an individual environment (dev, test, prod) and that can be rolled out across environments include

• Workflows
• Resource Locks
• File Order Sources
• Notice Boards
• Script Includes

Such objects can be managed with JS7 in a way that allows to re-use the objects - without any changes - across rollout environments such as dev, test, prod.

Local Objects

The following configuration object types typically hold values that are specific for an individual environment (dev, test, prod) and therefore usually are added to therefore usually are added to a separate repository. Such objects are not rolled out across environments.

...

User access is available in line with JOC Cockpit security levels used for deployment of workflows, see JS7 - Security Architecture:.

• Security level LOW maps to use of a single Git account used by all users. Credentials are stored with the root account's profile in the JS7 database.
• Security level MEDIUM maps to use of an individual Git account per user. Credentials are stored with each user account's profile in the JS7 database.
• Security level HIGH does not allow to store Git credentials with JOC Cockpit. Operations on the remote Git repository have to be performed with tools external to JOC Cockpit such as Git Extensions.

...

If repositories are used from a number of Git servers that require different sets of user credentials then separate user accounts in JOC Cockpit have to be used.

• 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

Repository Access

• The JS7 - REST Web Service API executes a set of Git operations by use of the Git Command Line Client.
• Any operations to add configuration objects to a repository, to stage, commit, push, pull and to merge objects are available from the JS7 REST Web Service API.
• The JOC Cockpit offers the user interface for respective Git operations.
• Users are free to use additional tools such as Git Extensions to manage repositories.

...