π― Targets
This page describes the main build targets available in the Forge system for Docker and Node.js projects.
π οΈ Forge (Generic) Targetsβ
- ποΈ Build: Runs the main build process for the selected project type (Docker, Node, etc.), depending on your command-line arguments.
- π ChangeLog: Generates or updates the project changelog based on recent commits.
πΊοΈ Target Execution Orderβ
This diagram shows the order in which the Forge (Generic) targets are executed:
π³ Docker Targetsβ
- ποΈ Build: Builds the Docker image, orchestrating all Docker-related steps.
- π CreateRelease: Creates a GitHub release for the built Docker image (if enabled and configured).
- π€ Push: Pushes the built Docker image(s) to the configured container registry.
- π·οΈ Tag: Tags the Docker image with the appropriate version and latest tags.
- πΌοΈ Image: Runs the actual Docker build command to produce the image.
πΊοΈ 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: