Fix #11873 ci: remove non-existent public profile from core-test workflow (#11873) #11897
+7
−8
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.
Fix #11873
Describe changes proposed in this pull request:
-Corrected three specific Maven commands (Build without tests, Build with tests, and Run tests separately) to prevent "profile not found" warnings in the CI pipeline.
Checks
The commit log is comprehensible. It follows 7 rules of great commit messages.
Has tests or has a separate issue that describes the types of test that should be created. (Note: This is a CI infrastructure fix; I have verified the fix by successfully running the modified workflow in my personal fork).
Is this PR adding logic based on one or more clinical attributes? No.
Make sure your PR has one of the labels defined in release-drafter.yml. (Please add the test or CI label).
Any screenshots or GIFs?
Before: The logs showed: Warning: The requested profile "public" could not be activated because it does not exist.
After: The Maven command executes successfully without the warning: Run mvn --settings settings.xml -q -U -DskipTests clean install
Notify reviewers
I am notifying @onursumer and @dippindots regarding this fix