Build and publish an application
Deployment runs a published application image. The build must therefore include the code and assets your users need: backend classes and dependencies, frontend assets where applicable, and the correct entry point. A running frontend development server is not automatically included in a production package.
Choose the project’s packaging path
Section titled “Choose the project’s packaging path”- Build
Compile and test the app, including its production frontend.
- Publish
Store one versioned image in the registry.
- Deploy
Select that published image for the cloud application.
Follow the project’s configured build. Two common paths are a container image built from a Dockerfile and an OCI package published by the Fluxzero build plugin. Use one intentional path for each application; do not add a second packaging mechanism just because an example workflow uses another one.
| Tool | Responsibility |
|---|---|
| Maven/Gradle build | Compile, test and produce the application’s artifacts |
| Fluxzero build plugin | Project-file support, development entry point and configured package publication |
| Container build | Build an OCI image from the project’s Dockerfile when that is its packaging path |
| Registry | Store the versioned image that deployment will request |
| Deploy Action / System API | Select an already published image for a cloud application |
Fluxzero build plugins
Section titled “Fluxzero build plugins”The Maven plugin includes sync-project-files, dev and publish-package. A publishing module declares its package name, image destination and entry point. Multi-module publishing opts modules in through their configuration; a reactor module is not automatically a deployable app.
The Gradle plugin provides the corresponding project/build integration. Use its documented tasks and properties for your pinned plugin version. Configure the Fluxzero Packages repositories for plugin and dependency resolution.
In GitHub Actions, the Maven publisher can use its configured github-oidc registry authentication. This publication credential is separate from the deployment credential used by the Deploy Action. Keep credentials out of the POM and source repository.
Identify exactly what will run
Section titled “Identify exactly what will run”Publish an immutable version, such as a release tag or commit SHA, and record the full registry reference. When the pipeline applies more than one tag to the same build, preserve the same underlying image instead of rebuilding between publication steps.
Check that the package includes the production frontend or that the frontend has its own explicit delivery path. Verify required live settings and identity configuration before deployment. Local demo seed actions should not become production initialization accidentally.
The GitHub Actions guide gives a complete Dockerfile-based Maven example. Projects using the Fluxzero publisher should retain their publisher configuration and use the same authentication/deployment boundaries. Publishing your app covers the builder’s release checks.
One recorded image reference, the required frontend assets and entry point, and the intended live configuration.
© 2026 Fluxzero