Skip to content

fix-exclusions-ignored-with-build-flag-for-dl-cmd - #3335

Closed
reshmifrog wants to merge 2 commits into
jfrog:masterfrom
reshmifrog:fix/exclusions-ignored-with-build-flag
Closed

reshmifrog wants to merge 2 commits into
jfrog:masterfrom
reshmifrog:fix/exclusions-ignored-with-build-flag

Conversation

@reshmifrog

Copy link
Copy Markdown
Contributor
  • All tests have passed. If this feature is not already covered by the tests, new tests have been added.
  • The pull request is targeting the master branch.
  • The code has been validated to compile successfully by running go vet ./....
  • The code has been formatted properly using go fmt ./....

problem: When using the jf rt download command with the --build flag to download artifacts associated with a specific build, the --exclusions flag is ignored. Files matching the exclusion pattern are still downloaded.
soltuion: When using the --build flag, the dl cmd was calling createAqlBodyForBuildArtifacts() which only included build name/number filters in the AQL query, completely ignoring --exclusions param. The fix adds new functions that properly include exclusion patterns into the AQL query using buildExcludeQueryPart(), ensuring files matching exclusion patterns are filtered out.

@reshmifrog reshmifrog added bug Something isn't working safe to test Approve running integration tests on a pull request labels Feb 1, 2026
@reshmifrog
reshmifrog enabled auto-merge (squash) February 1, 2026 21:26
@reshmifrog reshmifrog added safe to test Approve running integration tests on a pull request and removed safe to test Approve running integration tests on a pull request labels Feb 1, 2026
@github-actions

github-actions Bot commented Feb 1, 2026

Copy link
Copy Markdown
Contributor

👍 Frogbot scanned this pull request and did not find any new security issues.


@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

This pull-request has been marked as stale due to 6 months of inactivity. As part of our effort to address every issue properly, please feel free to remove the stale label or keep this issue active by leaving a comment. Otherwise, it will be closed in 7 days

@github-actions github-actions Bot added the stale An outdated issue lacking engagement label Aug 1, 2026
@github-actions

github-actions Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

This pull-request was closed due to 7 days of inactivity after being marked as stale. Feel free to reopen it if it remains relevant.

@github-actions github-actions Bot closed this Aug 9, 2026
auto-merge was automatically disabled August 9, 2026 00:26

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working safe to test Approve running integration tests on a pull request stale An outdated issue lacking engagement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant