Fix dockerhub push on release #174

New Issue

i-norden · 2021-12-20T20:04:02Z

i-norden commented

2021-12-20 20:04:02 +00:00

https://github.com/vulcanize/ipld-eth-db/issues/35 but for this repo

Pubishing to the docker registry on release only works if the git commit being tagged and published was already previously published to the github registry by the on-master action. But, we would like to be able to publish releases without merging them into one of main branches (e.g. for hot fixes, testing, maintaining the two different db schema working versions).

The way it currently works, the on-publish action must first pull from the github registry an image that was previously published by the on-master action. It tags and re-publishes it to the docker registry. It should build the image itself so it doesn't depend on a previous action that may or may not have occurred.

https://github.com/vulcanize/ipld-eth-db/issues/35 but for this repo Pubishing to the docker registry on release only works if the git commit being tagged and published was already previously published to the github registry by the `on-master` action. But, we would like to be able to publish releases without merging them into one of main branches (e.g. for hot fixes, testing, maintaining the two different db schema working versions). The way it currently works, the `on-publish` action must first pull from the github registry an image that was previously published by the `on-master` action. It tags and re-publishes it to the docker registry. It should build the image itself so it doesn't depend on a previous action that may or may not have occurred.

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/go-ethereum#174