Docs / Shipping code
Applications and build strategies
Describe what to build from a repository, and which build strategy runs it.
An application is one thing SysJ builds from a repository and deploys. A repository with several services has one application per service.
Fields
| Field | Notes |
|---|---|
| Name and repository | The repository cannot be changed later. |
| Path in the repository | Leave empty for the repository root. |
| Dockerfile | Relative to the path. Dockerfile by default. |
| Build tool | Chooses the build strategy, below. Leave empty for the Dockerfile alone. |
| Minimum coverage % | The build fails below this. Leave empty for no coverage gate. |
Build strategies
SysJ runs a fixed set of build strategies, each with its commands written by SysJ. You choose one by build tool; you cannot supply commands to run, which is what keeps a deployment request from becoming a way to run code on the build system.
| Build tool | Strategy | What runs |
|---|---|---|
empty, docker | dockerfile | The Dockerfile is the whole build. |
node, npm, pnpm, yarn, nest | node-service | pnpm install, build and test, then the Dockerfile. |
next, nextjs | nextjs-app | next build (standalone), tests, then the Dockerfile. |
static, vite | static-site | pnpm build to dist, served by the image. |
maven, mvn | maven-service | mvn verify, then the Dockerfile. |
Use the Dockerfile strategy for any language not listed.