dash/contrib/containers/deploy
PastaPastaPasta bc20ef6bf5
ci: resolve gitian automation failures on dashevo repo (#5267)
## Issue being fixed or feature implemented
Automation in private dashevo GitHub was failing due to the branch
trying to be built not having the automation be the newer tagged based
system. as such, if you simply tag a commit from the dashpay repo and
try to build it using automation, the build would fail. This should
resolve the issue. Recommended to BP so that we don't have this issue
when building v19.x branch builds

## What was done?


## How Has This Been Tested?
Creating a docker image should now be as simple pushing a branch and tag
to dashevo/dash; start the automation on branch develop with tag
previously specified

## Breaking Changes


## Checklist:
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added or updated relevant unit/integration/functional/e2e
tests
- [ ] I have made corresponding changes to the documentation

**For repository code-owners and collaborators only**
- [x] I have assigned this pull request to a milestone
2023-03-23 09:51:05 -05:00
..
docker-entrypoint.sh chore: add missing copyrights via copyright_header.py insert 2023-01-13 00:49:04 +03:00
Dockerfile docker: fix gitian support, optimize container layer count and improve script consistency (#4983) 2022-08-22 22:42:36 +03:00
Dockerfile.GitHubActions.Dispatch docker: fix gitian support, optimize container layer count and improve script consistency (#4983) 2022-08-22 22:42:36 +03:00
Dockerfile.GitHubActions.Gitian ci: resolve gitian automation failures on dashevo repo (#5267) 2023-03-23 09:51:05 -05:00
Dockerfile.GitHubActions.Release docker: fix gitian support, optimize container layer count and improve script consistency (#4983) 2022-08-22 22:42:36 +03:00
README.md build: relocate *net deployment logic to their own directories 2021-12-21 12:41:00 +05:30

This docker image is built and pushed from travis. It does not contain any default configs or any special startup scripts. This is to keep it simple and to not copy too much logic from the official/supported Docker Images found at https://hub.docker.com/r/dashpay/dashd/

The image is mostly used for devops purposes, e.g. for testnet/devnet deployments. Regular users should use the official images instead of this one.

NOTE: Please update the image description at https://hub.docker.com/r/dashpay/dashd-develop/ when changing the above text