build: add support for ssh key for publishing artifacts - #85
Draft
mahesh-wor wants to merge 2 commits into
Draft
Conversation
Collaborator
Author
|
Upstream Issue: geosolutions-it/MapStore2#11751 |
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
4 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
Adds support for ssh keys authentication in github actions to push to maven.geo-solutions.it repository.
Needs new secrets:
GS_MAVEN_HTTPPROXY_USERNAMEGS_MAVEN_HTTPPROXY_KEYRollback
Rollback would include reverting the PR, that should enable existing
user/password basedworkflow. As a precaution existing secrets are left intact and to be deleted only when ssh-key based workflow is working.Existing secrets INTACT.