JS7 JobScheduler

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next » 

under construction!!!

Introduction

JS7 JOC should be able to connect to GIT repositories to store JS7 configuration objects. Configuration objects can be versionized (tagged) and rolled out to different JS7 instances via GIT.

The usage of GIT somewhat conrtradicts the usage of a database as the leading system to store configuration data.

JS7 is the leading system to store configuration data. A connection to a GIT repository can only be seen as an additional oportunity to versionize and to rollout JS7 configuration objects.

Configuration Objects

Configuration objects to be stored in a GIT repository:

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

GIT Repository Usage

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

Storage

JS7 configuration objects are stored to a GIT repository via JOC web services.

Commands / Services

  • git-add
    • Adds (new) configuration object(s) from a working copy (currently the DB) to a local repository.
  • git-delete
    • Removes an already added configuration object from the local repository.
  • git-commit
    • Commits newly added, changed or removed configuration objects to a local repository.
  • git-push
    • Pushes the changes from the local repository to the connected remote repository.

Versioning

Versioning of JS7 configuration objects will be done with the tagging functionality of GIT. 

The JOC web services can manage the GIT tagging process.

Commands / Services

  • git-tag
    • tags the current commit with a version label
  • git-push
    • see above

Rollout

Rollout between different JS7 instances can be performed with the GIT functionality.

The JOC web services manage the checkout- and clone processes.

Commands / Services

  • git-checkout
    • checks out a specific branch or tag from the repository.
  • git-clone
    • clones a repository locally for the first time.
  • git-pull
    • pulls the recent changes from the remote repository into the local repository

Force Overwrite

Overwrites forcefully a target connfguration with the chosen source configuration.

  • JOC will not support merging between different GIT repositories or between different branches of one GIT repository as this is standard GIT functionality and can be done with any git tools outside of JOC.

The JOC web services manage the force overwrite process.

A force direction has to be provided.

Commands / Services

  • JS7 instance → GIT repository
    • git-add
      • Adds (new) configuration object(s) from a working copy (currently the DB) to a local repository.
    • git-delete
      • Removes an already added configuration object from the local repository.
    • git-commit
      • Commits newly added, changed or removed configuration objects to a local repository.
    • git-push
      • Pushes the changes from the local repository to the connected remote repository.
  • GIT repository → JS7 instance
    • git-checkout
      • checks out a specific branch or tag from the repository.
    • git-clone
      • clones a repository locally for the first time.
    • git-pull
      • pulls the recent changes from the remote repository into the local repository


Use Cases

Single Client (Single Branch)

Usage:

  • 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.

GIT repository usage:

  • storage
  • versioning
  • rollout

Requirements

  • The JOC database is the leading system holding the current configuration objects.

dev, test, prod - Single Client (Multiple Branches)

Usage:

  • 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).

GIT repository usage:

  • storage
  • versioning
  • rollout
  • force overwrite

Requirements

  • The JOC 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
  • force overwrite is possible

dev, test, prod - Multiple Clients (Multiple Branches)

Usage:

  • 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 is used to merge different changes from different clients in one JS7 instance outside of JOC

GIT repository usage:

  • storage
  • versioning
  • rollout
  • force overwrite

Requirements

  • The JOC 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
  • merges inside one branch are performed inside of JOC but only force overwrite is supported
  • No labels