DocumentationNextReading build logs
Builds
The build pipeline
How a project becomes a .jar.
A build runs in a locked-down container with no network access, a read-only file system, a non-root user and limits on CPU, memory, processes and time. Dependencies are fetched before the build by the platform from approved repositories. Steps:
- Prepare: the project files of the snapshot are placed in a fresh workspace.
- Resolve dependencies: the plugin API and the libraries the project declares are staged.
- Compile: Gradle or Maven builds the project and runs tests when src/test exists.
- Inspect artifact: the platform finds the .jar and checks that it is a valid archive.
- Validate plugin metadata: the descriptor must exist, name a main class that is in the .jar and be valid for the platform.
A successful build produces a .jar with a checksum. It stays available for download for 30 days.
