Build System & Compilation
Hubfly space's managed build system compiles source code from connected Git repositories or Dockerfiles into optimized container images inside isolated build runners.
Build Caching & Acceleration
node_modules, .m2, Go build cache) to minimize compilation times across redeployments.The Build Pipeline Lifecycle
1Source Fetching
The engine clones your Git repository or pulls the tarball commit payload, checking out the exact target branch or commit SHA.
2Stack Detection & Build Plan
If no explicit Dockerfile is provided, Hubfly space automatically detects your application runtime framework (Next.js, Express, FastAPI, Go, Rust) and generates an optimal multi-stage build plan.
3Compilation & Image Packaging
Build instructions execute inside secure sandbox containers. Build arguments and secrets are injected into the build stage safely without persisting in final image layers.
4Push to Internal Registry & Rollout
The finished container image is tagged and pushed to Hubfly space's high-speed private container registry, then deployed to your project environment.
Inspecting Build Execution
Every build session is assigned a unique buildId viewable at /projects/:projectId/build/:buildId. The build detail view provides:
- Pipeline Stepper Visualizer: Live progress tracking across Fetch, Inspect, Compile, Tag, and Push steps.
- Streamed Terminal Logs: Real-time stdout/stderr output from
docker buildor Paketo buildpacks with color-highlighted warnings and errors. - Build Variables: Full listing of compilation environment variables and build arguments used during execution.
- Lifecycle Timestamps: Detailed performance metrics (Created At, Started At, Finished At, Total Duration).
Build Arguments vs Runtime Variables
| Type | Scope | Persistence | Example |
|---|---|---|---|
| Build Argument (ARG) | Compilation stage only | Not stored in running container | NPM_TOKEN, NEXT_PUBLIC_API_URL |
| Runtime Variable (ENV) | Container execution environment | Available to container process | DATABASE_URL, PORT |
| Both | Available during build AND runtime | Persisted in runtime environment | NODE_ENV, APP_VERSION |