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)
1 file changed
tree: 2b620b3f8d1a8a8ea31d0f43533e5b36d4feb331
  1. .mvn/
  2. catalog-aliases/
  3. examples/
  4. karaf/
  5. qa/
  6. sandbox/
  7. software/
  8. .gitattributes
  9. .gitignore
  10. Dockerfile
  11. Jenkinsfile
  12. LICENSE
  13. NOTICE
  14. pom.xml
  15. README.md
README.md

Brooklyn

Library of Entities for Apache Brooklyn

This sub-project contains various entities not needed for Brooklyn, but useful as building blocks, including entities for webapps, datastores, and more.

Building the project

Two methods are available to build this project: within a docker container or directly with maven.

Using maven

Simply run:

mvn clean install

Using docker

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)