The Aurora scheduler is written in Java code and built with Gradle.
From the root directory of the Apache Aurora project generate the Gradle wrapper by running:
You will need Java 8 installed and on your
PATH or unzipped somewhere with
JAVA_HOME set. Then
will bootstrap the build system and show available tasks. This can take a while the first time you run it but subsequent runs will be much faster due to cached artifacts.
Aurora has a comprehensive unit test suite. To run the tests use
Gradle will only re-run tests when dependencies of them have changed. To force a re-run of all tests use
./gradlew clean build
To speed up development iteration, the plain gradle commands will not run static analysis tools. However, you should run these before posting a review diff, and always run this before pushing a commit to origin/master.
./gradlew build -Pq
To run the same tests that are run in the Apache Aurora continuous integration environment:
In addition, there is an end-to-end test that runs a suite of aurora commands using a virtual cluster:
Gradle can create a zip file containing Aurora, all of its dependencies, and a launch script with
or a tar file containing the same files with
The output file will be written to
Gradle can generate project files for your IDE. To generate an IntelliJ IDEA project run
and import the generated
New dependencies can be added from Maven central by adding a
compile dependency to
For example, to add a dependency on
example-lib 1.0 add this block:
NOTE: Anyone thinking about adding a new dependency should first familiarize themselves with the Apache Foundation’s third-party licensing policy.
The following files were autogenerated by
gradle wrapper using gradle’s
Wrapper plugin and
should not be modified directly:
./gradlew ./gradlew.bat ./gradle/wrapper/gradle-wrapper.jar ./gradle/wrapper/gradle-wrapper.properties
To upgrade Gradle unpack the new version somewhere, run
/path/to/new/gradle wrapper in the
repository root and commit the changed files.