commit | 0b77504b8e3049068de715d933b9b067a7b320bf | [log] [tgz] |
---|---|---|
author | Thomas Bouron <thomas.bouron@cloudsoftcorp.com> | Mon Dec 16 11:57:01 2019 +0000 |
committer | Thomas Bouron <thomas.bouron@cloudsoftcorp.com> | Mon Dec 16 11:57:01 2019 +0000 |
tree | 2b620b3f8d1a8a8ea31d0f43533e5b36d4feb331 | |
parent | 56d817db61a3186ec88dc9d20fd5dc2cf38cce65 [diff] |
Update Jenkinsfile to: - add the pipeline trigger on comment only if we are building a PR - not deploy artifacts when building master. This will be taken care of during the full brooklyn build on master (see Jenkinsfile configuration at the brooklyn root)
This sub-project contains various entities not needed for Brooklyn, but useful as building blocks, including entities for webapps, datastores, and more.
Two methods are available to build this project: within a docker container or directly with maven.
Simply run:
mvn clean install
The project comes with a Dockerfile
that contains everything you need to build this project. First, build the docker image:
docker build -t brooklyn:library .
Then run the build:
docker run -i --rm --name brooklyn-library -u $(id -u):$(id -g) \ --mount type=bind,source="${HOME}/.m2/settings.xml",target=/var/maven/.m2/settings.xml,readonly \ -v ${PWD}:/usr/build -w /usr/build \ brooklyn:library mvn clean install -Duser.home=/var/maven -Duser.name=$(id -un)
You can speed this up by using your local .m2 cache:
docker run -i --rm --name brooklyn-library -u $(id -u):$(id -g) \ -v ${HOME}/.m2:/var/maven/.m2 \ -v ${PWD}:/usr/build -w /usr/build \ brooklyn:library mvn clean install -Duser.home=/var/maven -Duser.name=$(id -un)