feat(JFrogCliV2): add option to register JFrog CLI on agent PATH - #650
Open
SierraNL wants to merge 1 commit into
Open
feat(JFrogCliV2): add option to register JFrog CLI on agent PATH#650SierraNL wants to merge 1 commit into
SierraNL wants to merge 1 commit into
Conversation
Adds an opt-in 'registerInPath' input. When enabled, the JFrog CLI executable's directory is prepended to the agent's PATH, so later steps in the same pipeline job can call 'jf' directly without a separate install/config step. Split out of jfrog#637 per reviewer feedback to keep each change focused and independently reviewable. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Aug 25, 2026
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
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.
Summary
Split out of #637 per reviewer feedback (multiple independent changes bundled into one PR). This is one of 3 independent PRs split out of #637 - #651 (persist/reuse config) and #652 (Package Alias) are the other two. All three are independent and can be reviewed/merged in any order.
Adds an opt-in
registerInPathinput toJFrogCliV2. When enabled, the JFrog CLI executable's directory is prepended to the agent's PATH, so later steps in the same pipeline job can calljfdirectly without a separate install/config step.This is off by default, so existing pipelines using
JFrogCliV2are unaffected.Test plan
node --check tasks/JFrogCliV2/jfrogCliRun.jstasks/JFrogCliV2/task.jsonparses as valid JSONtests/resources/jfrogCliV2RegisterInPath/registerInPath.js+ a newdescribeblock intests/tests.ts) asserting the task emits a##vso[task.prependpath]logging command whenregisterInPathis enabled, following the existingtests/resources/<taskDir>/<scenario>.js+mockTask/runSyncTestpattern used by sibling tasks.Note on CI
The
Testsworkflow is apull_request_targetworkflow gated behind asafe to testlabel, and for fork PRs GitHub always runs the base branch's copy of that workflow file (a built-in security control against fork PRs granting themselves elevated permissions) - so a maintainer needs to add the label for the integration test above to actually execute in CI. This can't be changed from the PR branch itself.🤖 Generated with Claude Code