forked from jenkinsci/artifactory-plugin
-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix accessing credentials when authorize project is enabled #922
Open
kneirinck
wants to merge
4
commits into
jfrog:master
Choose a base branch
from
kneirinck:feature/access_credentials_when_authorize_project_is_enabled
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fix accessing credentials when authorize project is enabled #922
kneirinck
wants to merge
4
commits into
jfrog:master
from
kneirinck:feature/access_credentials_when_authorize_project_is_enabled
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
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
yahavi
added
the
safe to test
Approve running integration tests on a pull request
label
Feb 14, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Feb 14, 2024
kneirinck
force-pushed
the
feature/access_credentials_when_authorize_project_is_enabled
branch
from
February 14, 2024 14:31
62f18a3
to
5a9aedc
Compare
@yahavi could you re-add the safe to test label? Seems it got removed because of my (force) push |
yahavi
added
the
safe to test
Approve running integration tests on a pull request
label
Feb 19, 2024
github-actions
bot
removed
the
safe to test
Approve running integration tests on a pull request
label
Feb 19, 2024
…orize_project_is_enabled
…orize_project_is_enabled
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.
When using the authorize-project plugin and restricting a job to run as a specific user,
rtUpload
fails to retrieve the stored credentials.This happens for both a globally defined server as well as a locally defined server with
rtServer
.After quite a bit of digging I found out that it's related to not using the
Run
context to access/find credentials.This PR changes the credential retrieval in as many places as possible to use a
Run
context if available and applicable.It's inspired by jenkinsci/docker-commons-plugin#68 (review)
This fixes #247
passed.