docker: publish branch-aligned repeater images and trigger rebuilds from core#258
Draft
yellowcooln wants to merge 3 commits into
Draft
docker: publish branch-aligned repeater images and trigger rebuilds from core#258yellowcooln wants to merge 3 commits into
yellowcooln wants to merge 3 commits into
Conversation
f64be2b to
9cc893c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR makes the repeater Docker image build deterministic and branch-aligned with
pyMC_core.devrepeater images build againstpyMC_core@dev.mainrepeater images build againstpyMC_core@main.pyMC_corecommit SHA and passes it into the image build.pymc_core[hardware]from that exact SHA, then installs repeater without letting pip re-resolvepymc_coreback to a cached branch tip.devis preserved, includinglibrrd-dev,pkg-config, and therrdtoolPython dependency.Workflow Behavior
mainanddev, but only onpyMC-dev/pyMC_Repeaterandyellowcooln/pyMC_Repeater.workflow_dispatchstill works and lets a user provide a custom Docker image repository.repository_dispatchsupport was added sopyMC_corecan trigger a repeater image rebuild with a knownchannel,core_ref, andcore_sha.pyMC-dev/pyMC_Repeater.Docker Compose / User Docs
pymcdev/pymc-repeater:devinstead of building locally.pull_policy: alwaysis set so compose pulls the latest published image before recreate../configto/etc/pymc_repeaterand./datato/var/lib/pymc_repeater../configand./data, run the radio config script against./config, and document the default container UID/GID15888ownership requirement.Notes
This PR adds the repeater-side dispatch receiver. The companion
pyMC_coreworkflow andREPEATER_REPO_DISPATCH_TOKENneed to live in thepyMC_corerepo separately.Testing
pyMC-dev/dev.PYMC_CORE_SHAprovided, confirming the Dockerfile resolvespyMC_core@devto an exact SHA.rrdtool,pymc_core, andrepeaterimport successfully.