Add CI pipeline workflow for testing and coverage #495
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This workflow defines a CI pipeline that runs on pushes and pull requests to specific branches. It includes steps for checking out code, setting up JDK, caching Maven packages, detecting changed microservices, running tests, and checking coverage thresholds.
Refactor GitHub Actions workflow to detect changed microservices and run tests accordingly. Add coverage check and build steps for changed services.
Updated the Maven CI workflow to use Temurin JDK and added steps for testing and coverage reporting.
Commented out the previous parent section in the POM file.
Updated the relative path in the parent POM configuration.
Add debug step to list coverage files and directories
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This workflow defines a CI pipeline that runs on pushes and pull requests to specific branches. It includes steps for checking out code, setting up JDK, caching Maven packages, detecting changed microservices, running tests, and checking coverage thresholds.