Repository navigation
Conversation
…; deprecate transfer-plugin-install
This branch is waiting to be deployed
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
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.
masterbranch.go vet ./....go fmt ./....What
jf rt transfer-plugin-installis now hidden and only logs a deprecation warning; it no longer installs anything. Its flags are accepted but ignored.test.installDataTransferPluginstays defined as a deprecated no-op so existing pipelines don't fail on an unknown flag. It can be removed in a follow-up once no workflow passes it.Dependency
transfer-filesstops requiring the plugin only with ajfrog-cli-coreversion that includes the GET/PUT transfer cutover. This PR must not merge beforego.modis bumped to such a version. Until then the transfer integration tests will still fail at the plugin check.