-
Notifications
You must be signed in to change notification settings - Fork 149
Automated builds and deployments
Builds and deployments are done thanks Travis-CI.
The setup is available in the .travis-.yml in the root directory of sources.
A build is done on each push from any branch to compile and run the tests.
The deployment process allows to upgrade the eclipse update sites. There are two, one for the snapshosts and another for releases.
NOTE: Do not edit their gh-pages, they are overwritten on deployments.
More, a release note is automatically done on the GitHub Releases page of the project with:
- the sources archives (in zip and tar.gz formats)
- an eclipse update site archive (zip)
On each push to the master branch, the deployment script will do:
- a build
- a tag following the semantic versioning with the pattern
MAJOR.minor.patch-buildtimestamp.travisjob. Example:1.0.0-20190109105647.28 - create a
pre-releasein GitHub Releases with assets - deploy to cucumber eclipse update site for snapshosts
The release deployment is automatically done when a release tag is done. The tag must not be done manually, but rather with the maven release plugin. See Doing a release The deployment script will do:
- a build
- create a release in GitHub Releases with assets and a badge
Latest release - deploy to cucumber eclipse update site for releases
NOTE: The Eclipse Marketplace is not automatically updated.