...

• The JS7 inventory holds scheduling objects such as JS7 - Workflows, JS7 - Calendars and Schedules etc. that are stored with the JS7 - Database.
• Users can integrate the JS7 inventory with Git repositories , see for JS7 - Rollout of Scheduling Objects, see scenarios and use cases from the JS7 - Git Repository Interface article.
• The below sections explain use of operations for Git repositories available from the JOC Cockpit GUI.
• Availability of Git integration is provided along the following iterationsJS7 releases:

  • Display feature availability
    StartingFromRelease 2.2.0

    • 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

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1144

  • Display feature availability
    StartingFromRelease 2.3.0

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1218

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1219

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1213

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1214

    • Jira
      server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JOC-1215

...

• Settings are used to determine which scheduling objects are considered local to an environment and which scheduling objects should be used for rollout to subsequent environments such as in a sequence dev = -> test = -> prod. For details see JS7 - Git Repository Interface, chapter: Configuration Scheduling Object Mappings
• For each scheduling object type settings determine if this should be considered for local use or for rollout to a remote Git repository:
  • git_hold_workflows: see JS7 - Workflows
  • git_hold_resource_locks: see JS7 - Resource Locks
  • git_hold_file_order_sources: see JS7 - Job Resources
  • git_hold_notice_boards: see JS7 - Notice Boards
  • git_hold_script_includes: see JS7 - Script Includes
  • git_hold_job_resources: see JS7 - Job Resources
  • git_hold_calendars: see JS7 - Calendars
  • git_hold_schedules: see JS7 - Schedules

Git Repositories

JS7 configuration scheduling objects are transparently managed in a Git repository via the JOC Cockpit GUI that makes use of the JS7 - REST Web Service API. In addition, tools such as Git Extensions and Git command line clients can be used for repository operations.

...

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

...

When storing objects local to the environment via the Repository=->Local=->Store to repository action then a popup window is displayed like this:

...

When storing objects intended for rollout to other environments via the Repository=->Rollout=->Store to repository action then a popup window is displayed like this:

Explanation:

• 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 to Agents include for example workflows, job resources etc.
    • Objects released within JOC Cockpit include for example calendars and schedules.
• Handle recursively
  • This The checkbox allows to select from a top-level folder any included sub-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.

...

When updating objects local to the environment via the Repository=->Local=->Update from repository action then a popup window is displayed like this:

...

When updating objects intended for rollout to other environments via the Repository=->Rollout=->Update from repository action then a popup window is displayed like this:

Explanation:

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

...

When deleting objects local to the environment via the Repository=->Local=->Delete from repository action then a popup window is displayed like this:

...

When deleting objects intended for rollout to other environments via the Repository=->Rollout=->Delete from repository action then a popup window is displayed like this:

Explanation:

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

...

• JS7 - Git Repository Interface
• JS7 - Rollout of Scheduling Objects