Java Runtime Builder

A Google Cloud Container Builder pipeline for packaging Java applications into supported Google Cloud Runtime containers. It consists of a series of docker containers, used as build steps, and a build pipeline configuration file.

Running via Google Cloud Container Builder (recommended)

To run via Google Cloud Container Builder, first install the Google Cloud SDK. Then, initiate a Cloud Container Build using the provided java.yaml file:

# Determine the name of your desired output image. Note that it must be a path to a Google Container
# Registry bucket to which your Cloud SDK installation has push access.
OUTPUT_IMAGE=gcr.io/my-gcp-project/my-application-container

# initiate the cloud container build
gcloud builds submit /path/to/my/java/app \ 
    --config java.yaml \
    --substitutions _OUTPUT_IMAGE=$OUTPUT_IMAGE

After the build completes, the built application container will appear in the gcr.io container registry at the specified path.

Running via Docker (without Cloud Container Builder)

Build steps can be run locally, one at a time, using docker. (This requires that the runtime-builder image is available locally.) Note that these commands effectively mirror the steps in the java.yaml pipeline config file.

LOCAL_APPLICATION_DIR=/path/to/my/app

# Generate docker resources
# See java.yaml for the fully specified jdk-runtimes-map server-runtimes-map args
docker run -v $LOCAL_APPLICATION_DIR:/workspace -w /workspace runtime-builder 

# package my application into a docker container
docker build -t my-app-container $LOCAL_APPLICATION_DIR

Configuration

An app.yaml file can be included in the sources passed to the Java Runtime Builder, but is not required. The runtime_config section of this file tells the builder how to build and package your source. In most cases, runtime_config can be omitted.

Alternatively, these settings can be provided as command line arguments to the Java Runtime Builder.

The settings in app.yaml and the command line share the same names. For example, --jdk=openjdk8 can be included in the args: section of java.yaml. If a setting is provided in both app.yaml and the command line, the setting from the command line will be used.

Sample app.yaml

runtime: java
env: flex

# all parameters specified below in the runtime_config block are optional
runtime_config:
  artifact: "target/my-artifact.jar"
  build_script: "mvn clean install -Pcloud-build-profile"
  jetty_quickstart: true

Images

The --jdk-runtimes-map and --server-runtimes-map settings are optional in both java.yaml when using the Cloud Container Builder as well as when building locally. These are the default mappings and will be available unless individually overridden:

These settings are also optional:

Development guide

• See DEVELOPING.md for instructions on how to build and test this pipeline.

Contributing changes

• See CONTRIBUTING.md

Licensing

• See LICENSE