-
Notifications
You must be signed in to change notification settings - Fork 1
BUILD-11500 Use self-hosted Artifactory for Maven actions #280
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
base: master
Are you sure you want to change the base?
Changes from all commits
0314185
4407515
bdfd8a3
a032b28
1875321
230867c
8bac5c3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -62,7 +62,7 @@ | |
| <releases> | ||
| <enabled>true</enabled> | ||
| <!-- no need to always check if new versions are available when executing a Maven plugin without specifying the version --> | ||
| <updatePolicy>interval:60</updatePolicy> | ||
| <updatePolicy>always</updatePolicy> | ||
| <checksumPolicy>fail</checksumPolicy> | ||
|
Comment on lines
62
to
66
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
| </releases> | ||
| <snapshots> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Edge Case: artifactory vault step may emit empty output for non-deploy builds
The new
artifactorystep requests zero secrets wheninputs.deploy == 'false'(all three secret lines evaluate to ''), and it has noif:guard, so it always runs. Lines 190-192 then callfromJSON(steps.artifactory.outputs.vault).ARTIFACTORY_DEPLOY_USERNAMEetc.Previously these deploy credentials lived in the
secretsstep, whose output was always non-empty valid JSON because it also requestedSIGN_KEY/PGP_PASSPHRASE. Now, for non-deploy builds (e.g. PR builds with deploy=false), the dedicatedartifactorystep may produce an emptyvaultoutput. If the wrapper emits''rather than{}in that case,fromJSON('')would throw and fail the env evaluation of the build step for all non-deploy runs.Please confirm vault-action-wrapper outputs
{}(not empty string) when no secrets are requested; if not, add anif:guard on theartifactorystep (e.g. only when deploy != 'false') and gate the dependent env vars accordingly.Was this helpful? React with 👍 / 👎