-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Adding docker image support with docker publish Github_action #58
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you build the image an push it to the registry registry.goharbor.io
Image name using thirs domain and library
repository name registry.goharbor.io/library/harbor-cli:1.2.3
The creads are in those variables.
- REGISTRY_GOHARBOR_ROBOT_USER_NAME
- REGISTRY_GOHARBOR_ROBOT_USER_SECRET
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bishal7679 fix DCO.
Signed-off-by: bishal7679 <[email protected]>
Signed-off-by: bishal7679 <[email protected]>
Signed-off-by: bishal7679 <[email protected]>
Signed-off-by: bishal7679 <[email protected]>
Signed-off-by: bishal7679 <[email protected]>
Signed-off-by: bishal7679 <[email protected]>
Signed-off-by: bishal7679 <[email protected]>
Signed-off-by: bishal7679 <[email protected]>
Signed-off-by: bishal7679 <[email protected]>
Fixes ⇾ part of #7
Previous State
Current Behavior
Needs to be set
secrets
in the repository scope using below naming conventionharbor-cli
and Docker hub account namegoharbor
(can be changed if already existing any account)goharbor/harbor-cli
To trigger the github action, just need to push any changes in main branch or any pull request
//cc @Vad1mo @amands98