-
Story
-
Resolution: Done
-
Normal
-
None
-
None
This ticket implements two major workflow enhancements for our CI/CD pipeline:
1. Node.js 22 Integration
- Add support for building and testing with Node.js 22
- Ensure project compatibility with the latest Node.js version
- Enable access to new performance features and improvements
2. Docker Image Build Automation (with [skip-build] feature)
- Implement automated Docker image builds using pull_request_target event
- Add a [skip-build] tag feature (suggested by Nick) to optimize CI workflow
- Allow developers to skip image builds when unnecessary by adding [skip-build] to commit messages
- Maintain all other checks and tests while skipping only the image build step
The [skip-build] feature provides several benefits:
- Reduces CI pipeline execution time when image rebuilds aren't needed
- Makes the skip intention explicit in git history
- Provides flexibility to skip builds on any branch
- Prevents unnecessary comments on PRs when build is skipped
Example usage:
git commit -m "feat: update e2e tests [skip-build]"
These enhancements will improve our development workflow by:
- Ensuring compatibility with the latest Node.js features
- Streamlining the deployment process
- Reducing unnecessary CI pipeline executions
- Making the build process more efficient and developer-friendly
Credits:
The idea of checking commit messages for the [skip-build] tag was suggested by nickboldt , who proposed this approach as a more flexible and explicit way to control the build process. This implementation follows his suggestion to make the skip intention clear in the git history and provide a simple way to bypass image builds when needed.
- is cloned by
-
RHIDP-7752 [rhdh-operator] Add support for [skip-build] tag in commit messages to skip the CI jobs and save some time
-
- Refinement
-
- links to