The java-buildpack is a Cloud Foundry buildpack for running JVM-based applications. It is designed to run many JVM-based applications (Grails, Groovy, Java Main, Play Framework, Spring Boot, and Servlet) with no additional configuration, but supports configuration of the standard components, and extension to add custom components.
To use this buildpack specify the URI of the repository when pushing an application to Cloud Foundry:
$ cf push <APP-NAME> -p <ARTIFACT> -b https://github.com/cloudfoundry/java-buildpack.gitThe following are very simple examples for deploying the artifact types that we support.
The buildpack supports extension through the use of Git repository forking. The easiest way to accomplish this is to use GitHub's forking functionality to create a copy of this repository. Make the required extension changes in the copy of the repository. Then specify the URL of the new repository when pushing Cloud Foundry applications. If the modifications are generally applicable to the Cloud Foundry community, please submit a pull request with the changes.
Buildpack configuration can be overridden with an environment variable matching the configuration file you wish to override minus the .yml extension and with a prefix of JBP_CONFIG. It is not possible to add new configuration properties and properties with nil or empty values will be ignored by the buildpack. The value of the variable should be valid inline yaml, referred to as flow style in the yaml spec (Wikipedia has a good description of this yaml syntax). For example, to change the default version of Java to 7 and adjust the memory heuristics apply this environment variable to the application.
$ cf set-env my-application JBP_CONFIG_OPEN_JDK_JRE '{jre: { version: 1.7.0_+ }}'If the key or value contains a special character such as : it should be escaped with double quotes. For example, to change the default repository path for the buildpack.
$ cf set-env my-application JBP_CONFIG_REPOSITORY '{default_repository_root: "http://repo.example.io"}'If the key or value contains an environment variable that you want to bind at runtime you need to escape it from your shell. For example, to add command line arguments containing an environment variable to a Java Main application.
$ cf set-env my-application JBP_CONFIG_JAVA_MAIN '{arguments: "-server.port=\$PORT -foo=bar"}'Environment variable can also be specified in the applications manifest file. For example, to specify an environment variable in an applications manifest file that disables Auto-reconfiguration.
env:
JBP_CONFIG_SPRING_AUTO_RECONFIGURATION: '{enabled: false}'This final example shows how to change the version of Tomcat that is used by the buildpack with an environment variable specified in the applications manifest file.
env:
JBP_CONFIG_TOMCAT: '{tomcat: { version: 8.0.+ }}'See the Environment Variables documentation for more information.
To learn how to configure various properties of the buildpack, follow the "Configuration" links below. More information on extending the buildpack is available here.
- Design
- Security
- Standard Containers
- Standard Frameworks
- AppDynamics Agent (Configuration)
- Container Certificate Trust Store (Configuration)
- Container Customizer (Configuration)
- Debug (Configuration)
- Dynatrace Application Monitoring Agent (Configuration)
- Dynatrace Ruxit Cloud Native Agent (Configuration)
- Introscope Agent (Configuration)
- Java Options (Configuration)
- JRebel Agent (Configuration)
- JMX (Configuration)
- Luna Security Provider (Configuration)
- MariaDB JDBC (Configuration)
- New Relic Agent (Configuration)
- Play Framework Auto Reconfiguration (Configuration)
- Play Framework JPA Plugin (Configuration)
- PostgreSQL JDBC (Configuration)
- Spring Auto Reconfiguration (Configuration)
- Spring Insight
- YourKit Profiler (Configuration)
- Standard JREs
- Extending
- Debugging the Buildpack
- Buildpack Modes
- Related Projects
The buildpack can be packaged up so that it can be uploaded to Cloud Foundry using the cf create-buildpack and cf update-buildpack commands. In order to create these packages, the rake package task is used.
The online package is a version of the buildpack that is as minimal as possible and is configured to connect to the network for all dependencies. This package is about 50K in size. To create the online package, run:
$ bundle install
$ bundle exec rake package
...
Creating build/java-buildpack-cfd6b17.zipThe offline package is a version of the buildpack designed to run without access to a network. It packages the latest version of each dependency (as configured in the config/ directory) and disables remote_downloads. This package is about 180M in size. To create the offline package, use the OFFLINE=true argument:
To pin the version of dependencies used by the buildpack to the ones currently resolvable use the PINNED=true argument. This will update the config/ directory to contain exact version of each dependency instead of version ranges.
$ bundle install
$ bundle exec rake package OFFLINE=true PINNED=true
...
Creating build/java-buildpack-offline-cfd6b17.zipKeeping track of different versions of the buildpack can be difficult. To help with this, the rake package task puts a version discriminator in the name of the created package file. The default value for this discriminator is the current Git hash (e.g. cfd6b17). To change the version when creating a package, use the VERSION=<VERSION> argument:
$ bundle install
$ bundle exec rake package VERSION=2.1
...
Creating build/java-buildpack-2.1.zipTo run the tests, do the following:
$ bundle install
$ bundle exec rakeRunning Cloud Foundry locally is useful for privately testing new features.
Pull requests are welcome; see the contributor guidelines for details.
This buildpack is released under version 2.0 of the Apache License.