$ mvn clean install -Dquickly
$ cd optaplanner-examples
$ mvn exec:java

Every change must be submitted through a GitHub pull request (PR). OptaPlanner uses continuous integration (CI). The OptaPlanner CI runs checks against your branch after you submit the PR to ensure that your PR doesn’t introduce errors. If the CI identifies a potential problem, our friendly PR maintainers will help you resolve it.

1. Fork it (https://github.com/kiegroup/optaplanner).

2. Create your feature branch: (git checkout -b feature).

3. Commit your changes with a comment: (git commit -am 'Add some feature').

4. Push to the branch to GitHub: (git push origin feature).

5. Create a new pull request.

Your code is automatically formatted according to the Import and Code Style conventions during every Maven build. CI checks enforce those conventions too, so be sure to build your project with maven before creating your PR:

For information about how to set up code style checks, see IDE Setup Instructions.

Use one of the following ways to build your OptaPlanner project:

• build-fast: mvn clean install -Dquickly skips any checks and code analysis (~1 min)

• build-normally: mvn clean install runs tests, checks code style, skips documentation (~17 min)

• :receipt: build-doc: mvn clean install at optaplanner/optaplanner-docs creates asciidoctor documentation target/optaplanner-docs-*/html_single/index.html (~2 min)

• :mechanical_arm: build-all: mvn clean install -Dfull runs all checks + creates documentation and distribution files (~20 min)

All Jenkins jobs can be found under the OptaPlanner folder: https://eng-jenkins-csb-business-automation.apps.ocp-c1.prod.psi.redhat.com/job/KIE/job/optaplanner

Interesting Jenkins CI jobs (need VPN access):

• Update Quarkus version

• Update Drools version

• Release pipeline (only available on release branches)

• Post-Release pipeline (only available on release branches)