π― Targets
This page describes the main build targets available in the Forge system for Docker and Node.js projects.
π οΈ Forge (Changelog Generation) Targetsβ
- ποΈ Build: Completes the build process after changelog generation (depends on GenerateChangeLog).
- π GenerateChangeLog: Generates formatted changelog from Git commit history and saves to CHANGELOG.md.
- βοΈ Setup: Initializes parameters and environment configuration.
Changelog Features:
- Supports multiple sources: since last tag, complete history, or specific tag
- Uses customizable date formatting (default:
yyyy.MM.dd
) - Automatically prepends new content to existing changelog files
- Groups commits by date in descending order (latest first)
πΊοΈ Forge Target Execution Orderβ
This diagram shows the order in which the Forge (Changelog Generation) targets are executed:
π³ Docker Targetsβ
- ποΈ Build: Builds the Docker image, orchestrating all Docker-related steps.
- π PublishToGitHub: Creates a GitHub release for the built Docker image (if enabled and configured).
- π€ PushToRegistry: Pushes the built Docker image(s) to the configured container registry.
- πΌοΈ BuildDockerImage: Runs the actual Docker build command to produce the image.
πΊοΈ Docker Target Execution Orderβ
This diagram shows the order in which the Docker build targets are executed:
π© Node Targetsβ
- ποΈ Build: Runs the full Node.js build pipeline, including environment generation, application build, and artifact copying.
- π¦ CopyToArtifacts: Copies the built Node.js application and related files to the artifacts directory.
- π οΈ BuildApplication: Executes the Node.js build process (e.g.,
npm run build
). - π± GenerateEnvironment: Generates the environment file from your mapping configuration, ensuring all required variables are set.
- π§Ή Clean: Cleans the artifacts directory and prepares the workspace for a fresh build.
πΊοΈ Target Execution Orderβ
This diagram shows the order in which the Node.js build targets are executed:
π©π³ NodeInDocker Targetsβ
The NodeInDocker build combines Node.js application building with Docker image creation:
- ποΈ Build: Executes the complete pipeline from Node.js build to Docker image push and GitHub release.
- π PublishToGitHub: Creates a GitHub release for the built Docker image (if enabled and configured).
- π€ PushToRegistry: Pushes the built Docker image(s) to the configured container registry.
- πΌοΈ BuildDockerImage: Builds the Docker image from the Node.js artifacts.
- π¦ CopyToArtifacts: Copies the built Node.js application to the artifacts directory.
- π οΈ BuildApplication: Executes the Node.js build process.
- π± GenerateEnvironment: Generates the environment file from your mapping configuration.
- π§Ή Clean: Cleans the artifacts directory and prepares the workspace for a fresh build.
πΊοΈ NodeInDocker Target Execution Orderβ
This diagram shows the order in which the NodeInDocker build targets are executed: