ICS-JDF-Messaging

This ICS describes the minimum requirements for a solution to be conformant to the CIP4 Job Messaging Format (JMF)

Issue Tracking

TBD

Development Notes

Release a new Version

Creation and publishing of a new version to GitHub Release.

$ git tag -a ICS-JDF-Messaging-[VERSION] -m "[TITLE]"
$ git push origin ICS-JDF-Messaging-[VERSION]

In case a build has been failed, a tag can be deleted using the following command:

$ git tag -d ICS-JDF-Messaging-[VERSION]
$ git push origin :refs/tags/ICS-JDF-Messaging-[VERSION]

Build Artefacts

Each build process produces a single PDF. This is either a release version for public distribution, or a continuous integration (CI) build for use

Build Process

CI builds are triggered by any 'push' to the [MASTER] branch.
There is an option to trigger this build manually in the event that an automated CI build fails due to issues with the build process.

Release builds are triggered by adding a git tag to a commit. The value of tag will be used as the document identifier on both the cover and in the resulting artefact file name.
For example use a tag of 'Draft-IP-4' or 'Version 2.1 Final'.
There is alos an option to trigger this build manually.