Lets decide how to do major version upgrades,,,, can this be automated via commit message? Or should we even worry about it at all?
(just some brainstorming...)
Right now
- we explicitly grep for "ci-skip in commit message".
- we always assume only the minor version is being incremented.
Lets make these key-value pairs sent into the bash script, example:
[ci-skip="false", version="auto"] translates to
--ci-skip=false --version=auto, which results in autoincrement of minor version along with auto publishing of the new version, that way someone who wants to upgrade the major version can do
commit -m "Lets bump to 2.2 [version="2.2.0"]
and then the version, rather than auto incrmented via python script, is explicitly set in the pom.
Lets decide how to do major version upgrades,,,, can this be automated via commit message? Or should we even worry about it at all?
(just some brainstorming...)
Right now
Lets make these key-value pairs sent into the bash script, example:
[ci-skip="false", version="auto"] translates to
--ci-skip=false --version=auto, which results in autoincrement of minor version along with auto publishing of the new version, that way someone who wants to upgrade the major version can do
commit -m "Lets bump to 2.2 [version="2.2.0"]
and then the version, rather than auto incrmented via python script, is explicitly set in the pom.