Skip to content
Snippets Groups Projects
Select Git revision
  • 2.7.x
  • 2.7.5
  • main default protected
  • 2.7.4
  • 2.7.3
  • 2.8.0-M1
  • 2.6.x
  • 2.5.x
  • 2.4.x
  • 2.3.x
  • 2.1.x
  • 2.2.x
  • 2.0.x
  • 1.3.x
  • 1.1.x
  • v2.7.5
  • v2.7.4
  • v2.7.3
  • v2.8.0-M1
  • v2.7.2
  • v2.7.1
  • v2.6.4
  • v2.7.0
  • v2.6.3
  • v2.7.0-RC1
  • v2.7.0-M2
  • v2.6.2
  • v2.7.0-M1
  • v2.6.1
  • v2.6.0
  • v2.6.0-RC1
  • v2.6.0-M1
  • v2.5.2
  • v2.5.1
  • v2.4.3
35 results
Blame Permalink
  • David Turanski's avatar
    97a0bba9
    Support remote debug host:port syntax for Java 9 and above · 97a0bba9
    David Turanski authored 
     - Add DebugAddress helper to validate and parse the (legacy) debug-port and debug-address. Later has precedence.
 - Streamline the CommandBuilder implementation ensuring that the Java and Docker specific code runs inside the command builder and is not spilled out to the AbstractLocalDeployerSupport or AppLocalDeployer.
 - Update affected tests (also migrate those to JUnit5).
 - Improve code cohesion and remove death code.

 - Change GUID from 'port' to 'deployerId-index'.
 - Allow the Docker and Java command builder use different port range. Needed to allow in-container Skipper to operate with both maven and docker resources.
    97a0bba9
    History
    Support remote debug host:port syntax for Java 9 and above
    David Turanski authored 
     - Add DebugAddress helper to validate and parse the (legacy) debug-port and debug-address. Later has precedence.
 - Streamline the CommandBuilder implementation ensuring that the Java and Docker specific code runs inside the command builder and is not spilled out to the AbstractLocalDeployerSupport or AppLocalDeployer.
 - Update affected tests (also migrate those to JUnit5).
 - Improve code cohesion and remove death code.

 - Change GUID from 'port' to 'deployerId-index'.
 - Allow the Docker and Java command builder use different port range. Needed to allow in-container Skipper to operate with both maven and docker resources.
README.adoc 1.18 KiB

Spring Cloud Local Deployer

Spring Cloud Local Deployer is an implementation of the Spring Cloud Deployer SPI for use to deploy applications on the same machine. This occurs by this application spawning a new JVM process for the deployed application.

It’s important to note that this deployer spawns new JVMs that are not monitored or maintained by this deployer. No attempts at high availability, fault tolerance, or resiliency are provided by the deployer. Since the deployer SPI expects an underlying platform to provide that level of resiliency, any use of this deployer in a production environment should be accompanied with additional monitoring at the app level (the apps this deployer deploys). This deployer will not be updated to take on those requirements. Therefore the user is encouraged to explore the CloudFoundry and Kubernetes variants as ways to meet them.

Building

Build and skip all tests:

./mvnw clean package -DskipTests

Or build project and run tests:

./mvnw clean package

Run the integration tests in Docker mode:

./mvnw clean install -Dspring-cloud-deployer-spi-test-use-docker=true -Dspring.cloud.deployer.local.hostname=localhost