Maven plugin for the automated building of Axon Ivy Projects.
- Examples and documentation
- Learn more about Axon Ivy Project building in the Designer Guide under Concepts -> Continuous Integration
- Update the default engine version in:
- Raise the minimal engine version needs to be updated at least if you introduce a new minor or major version:
Since 9.4: Releasing is only possible on a release branch.
-
Create a release branch if it does not exist yet (e.g. release/10.0)
-
Run the release build on the release branch
-
Merge the Pull Request for next development iteration
-
If you have created a new release branch:
-
on
mastermanually raise the version to the next major or minor version by executing the following command in the root of this project and make the steps in 'preperation' on the master branch :mvn versions:set -DnewVersion=10.0.0-SNAPSHOT -DprocessAllModules -DgenerateBackupPoms=false
-
-
If the master reflects a new release-cycle; reflect it in the
versionPrefixquery parameter on the badges below.
Wait until the maven central release is available: this may take several hours until it's fully distributed.
-
Release-Drafter changes, if a new-release train was introduced:
- on github UI (PR View): flag the latest PR which was only merged to master with the label
major.
... now release-drafter action runs should create new draft PRs for the new release; without overwriting the existing master drafts.
- on github UI (PR View): flag the latest PR which was only merged to master with the label
-
Raise project-build-plugin in other repos by triggering this build
- Merge the generated PRs on GitHub
-
If you prepared for a new release train: update the default engine version in the AbstractEngineMojo
-
Inform team-wawa @Teams to update to update Portal onto the latest project-build-plugin version!
-
Raise ch.ivyteam.ivy.library.IvyProjectBuildPlugin.DEFAULT_VERSION in ivy core
The Apache License, Version 2.0