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.
Configuration Objects
Configuration objects to be stored in a GIT repository:
- Workflows
- Locks
- File Order Sources
- Job Resources
- Boards
- Calendars
- Schedules
Use Cases
- Single User (Backup and Versioning Tool)
- DB is the leading system (???)
- simple versioning repository
- single branch
- version can overwrite local (DB) versions as new configurations
- new local configurstion share version from repository (next version +1 or next version Snapshot)
- git commands needed:
- add
- delete
- commit
- pull
- push
- tag
- dev, test, prod - single user
- different versioning for different branches (dev, test, prod)
- DB is the leading system (???) (single DB? for each branch?)
- repository used for user versioning only
- merges from branch to branch possible?
- version can overwrite local (DB) versions as new configurations
- new local configuration share latest version from DB (next version +1 or next version Snapshot)
- git commands needed:
- add
- delete
- commit
- pull
- push
- tag
- merge ?
dev, test, prod - multi user
different versioning for different branches (dev, test, prod)
different users each branch can commit (Merge needed! 3rd party Tool like KDiff?)
DB is the leading system (???) (Single DB (dev, test, prod) needed for each branch (Security/Network issues))
repository used for user versioning only
merges from branch to branch possible
version can overwrite local (DB) versions as new configurations
new local configurstion share latest version from DB (next version +1 or next version Snapshot)
git commands needed:
add
delete
commit
pull
push
tag
merge
Overview
Content Tools