ci: add container build workflow for fork #24
Conversation
|
Oh, sick, my big goal here is to re-add a container build so we can consume it in CI deployments. I'll edit this to just add the container workflow, and wait for #23 to land to rebase this! |
conorsch
force-pushed
the
container-image
branch
from
4c1553a to
e3c6f0a
Compare
|
This PR now only affects the container-build logic. Will wait until other PRs land, so this can be rebased, and we keep CI green. I can't test the new container workflow until it lands on main, so there might be a follow-up, but will handle that when the time comes. |
conorsch
changed the title
conorsch
force-pushed
the
container-image
branch
2 times, most recently
from
ad07153 to
f0bb9e8
Compare
We cannot depend on the upstream `informalsystems/hermes` repo for CI deployments, because we need the forked Hermes code for compatiblity with Penumbra chains. Added a new workflow that will publish as `ghcr.io/penumbra-zone/hermes`, and removed the informalsystems one.
conorsch
force-pushed
the
container-image
branch
from
f0bb9e8 to
634dccc
Compare
This single job was failing due to timeout. Bumping its timeout. We could also switch to a faster runner, but a separate job takes ~1h, which is really where we should focus attention.
|
Ready for review. I tacked on one more commit to bump the timeout on one of the CI jobs that was failing due to overrunning the 20m limit. If we end up maintaining this fork for a long time, maybe someday it'll be worthwhile to focus on speeding up CI—but at the low rate of change here, not worthwhile right now. |
We cannot depend on the upstream
informalsystems/hermesrepo for CI deployments, because we need the forked Hermes code for compatiblity with Penumbra chains. Added a new workflow that will publish asghcr.io/penumbra-zone/hermes, and removed the informalsystems one.