Very cut back version of continuous integration build system for IBM Maximo Application Suite, based on Travis CI, utilizing automated semantic versioning of releases.
Managed Branches are ones where any commit will result in a new version being released. These branches take one of two forms:
master(current major version)v1.x,v2.x,v3.x,v4.xetc
Versioning is controlled by the GitHub commit messages:
- A commit comment of
[patch] Fix the thingwill result in a version change from1.0.0to1.0.1 - A commit comment of
[minor] Add the new featurewill result in a version change from1.0.0to1.1.0 - A commit comment of
[major] Rewrite the thingwill result in a version change from1.0.0to2.0.0 - A commit comment without any of the above will result in build with no new release being published
- A commit comment of
[skip ci] Something not worth a new buildwill result in Travis not even running
When a build contains multiple commits the most significant commit "wins".
Commits in Unmanaged Branches will still result in a new build, but any artifacts published will overwrite the previous release. Effectively there is only a latest version for these branches.