publish fat jar in maven update action - #935
Merged
xiaoyongzhu merged 1 commit intoJan 3, 2023
Merged
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
xiaoyongzhu
approved these changes
Jan 3, 2023
blrchen
reviewed
Jan 3, 2023
Comment thread
.github/workflows/publish-to-maven.yml
blrchen
approved these changes
Jan 3, 2023
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
Reviewers
3 participants
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.
Description
Resolves #934
How was this PR tested?
Currently, the Github Action will write fat jar to the storage defined by "SPARK_JAR_BLOB_CONNECTION_STRING". To separate it from CI artifacts, we may need to create a new secret to store released jar blob connection string in the future.
This PR only provide a trackable released Fat jar for reference.
Does this PR introduce any user-facing changes?