-
Notifications
You must be signed in to change notification settings - Fork 43
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
Workflow to publish container to public registy #1266
Labels
ci/build
This is issue is about the build or CI system, and the administration of it.
Comments
orpheuslummis
added
the
ci/build
This is issue is about the build or CI system, and the administration of it.
label
Mar 30, 2023
This was referenced Apr 13, 2023
ideally: |
blocked by #1221 |
4 tasks
nasdf
added a commit
that referenced
this issue
Jul 25, 2023
## Relevant issue(s) Resolves #1674 Resolves #1266 ## Description This PR adds a GitHub Action workflow that builds and publishes DefraDB container images to DockerHub & GitHub container registries. Push Docker images to registries Job: https://github.com/sourcenetwork/defradb/actions/runs/5651002188 Pull Docker image Job: https://github.com/sourcenetwork/defradb/actions/runs/5651962572 Validate containerfile job: https://github.com/sourcenetwork/defradb/actions/runs/5652056549 GitHub Container Image: https://github.com/sourcenetwork/defradb/pkgs/container/defradb DockerHub Container Image: https://hub.docker.com/repository/docker/sourcenetwork/defradb/general ## Tasks - [x] I made sure the code is well commented, particularly hard-to-understand areas. - [x] I made sure the repository-held documentation is changed accordingly. - [x] I made sure the pull request title adheres to the conventional commit style (the subset used in the project can be found in [tools/configs/chglog/config.yml](tools/configs/chglog/config.yml)). - [x] I made sure to discuss its limitations such as threats to validity, vulnerability to mistake and misuse, robustness to invalidation of assumptions, resource requirements, ... ## How has this been tested? Manual Specify the platform(s) on which this was tested: - MacOS
shahzadlone
pushed a commit
to shahzadlone/defradb
that referenced
this issue
Feb 23, 2024
…twork#1676) ## Relevant issue(s) Resolves sourcenetwork#1674 Resolves sourcenetwork#1266 ## Description This PR adds a GitHub Action workflow that builds and publishes DefraDB container images to DockerHub & GitHub container registries. Push Docker images to registries Job: https://github.com/sourcenetwork/defradb/actions/runs/5651002188 Pull Docker image Job: https://github.com/sourcenetwork/defradb/actions/runs/5651962572 Validate containerfile job: https://github.com/sourcenetwork/defradb/actions/runs/5652056549 GitHub Container Image: https://github.com/sourcenetwork/defradb/pkgs/container/defradb DockerHub Container Image: https://hub.docker.com/repository/docker/sourcenetwork/defradb/general ## Tasks - [x] I made sure the code is well commented, particularly hard-to-understand areas. - [x] I made sure the repository-held documentation is changed accordingly. - [x] I made sure the pull request title adheres to the conventional commit style (the subset used in the project can be found in [tools/configs/chglog/config.yml](tools/configs/chglog/config.yml)). - [x] I made sure to discuss its limitations such as threats to validity, vulnerability to mistake and misuse, robustness to invalidation of assumptions, resource requirements, ... ## How has this been tested? Manual Specify the platform(s) on which this was tested: - MacOS
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Registry needs to publically resolvable - it can be Docker's, Github's, Web3 one, etc.
The text was updated successfully, but these errors were encountered: