What this means
What this means
We build your application from your repository and run the artefact it produces. That only works if we know exactly what to build, what it produces, how to start it, and how to tell whether it came up. Guessing any of the four produces a machine that builds and then fails to serve.
Before you start
Before you start
Make sure your application builds cleanly from a fresh clone of the branch you give us — no local files, no IDE settings, no untracked configuration.
Step-by-step guidance
Step-by-step guidance
- Pin your JDK. Tell us 21 or 17 and set the same version in your pom.xml or build.gradle. "Latest" is not a supported answer and drifts under you.
- Make your build produce one runnable artefact. For Maven that is usually spring-boot-maven-plugin repackage; for Gradle, bootJar.
- Give us the exact artefact path, not a pattern. target/demo-1.0.0.jar is usable; target/*.jar is not, because a stale jar from an earlier version would match too.
- Read the port from the environment rather than hard-coding it, so we can place the app behind our reverse proxy.
- Expose a health endpoint that returns 200 only when the app can actually serve. Spring Boot's /actuator/health does this; a bare / that returns 200 while the database is down does not.
- Keep secrets out of the repository. Give them to us as environment variables instead.
- Let the JVM size its own heap from the machine, or set -XX:MaxRAMPercentage rather than a fixed -Xmx, so a later resize is actually used.
What CM Cloud support will review
What CM Cloud support will review
Support can tell you whether your artefact path and start command agree with what your build actually produces, and will check your health endpoint reports honestly before we rely on it for monitoring.
What is not automated yet
What is not automated yet
We do not modify your application. If your build needs a private dependency repository, a specific Maven settings file, or credentials at build time, tell us in the notes — we will not discover them on our own.
Safety note
Safety note
Nothing here changes your code. These are checks to run against your own repository before we build, so the first build succeeds rather than failing on something avoidable.
Safe next action
Safe next action
Clone your repository somewhere clean, build it, and run the artefact exactly as you have described it to us. If that works, our build will too.