CI - Prefer repo from settings over project #90
Merged
Conversation
This file contains 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
yahavi
added
improvement
github-actions
bot
removed
the
safe to test
yahavi
changed the title
yahavi
force-pushed
the
ci-prefer-settings
branch
from
987ed7b
to
7cb5ba5
Compare
github-actions
bot
removed
the
safe to test
eyalbe4
approved these changes
Dec 11, 2023
yahavi
added
bug
4 tasks
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
tests.
In CI mode, when a resolution server is specified, the plugin should prioritize repository settings configured by the user in the JFrog CLI / Jenkins Artifactory plugin over those in the
build.gradlefile. For example, configuring the Gradle project withjf gradlec --server-id-resolve maven-remoteand executingjf gradle clean aPshould result in the use of the maven-remote repository instead of any repositories mentioned in thebuild.gradlefile.