Add CI workflow#11
Open
baggepinnen wants to merge 5 commits into
Open
Conversation
Mirrors the MultibodyComponents CI: self-hosted runner, private JuliaHub registries, and the test suite run under a virtual display. Includes a temporary step that takes MultibodyComponents from its main branch, since the models require the BodyShape center-of-mass fix (JuliaComputing/MultibodyComponents.jl#150) which is not yet in any registered release; remove the step and bump the compat bound once a fixed release is registered. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
JuliaComputing/set-up-private-juliahub-registries lives in a private repository, and private actions cannot be resolved from workflows in this public repository (the run failed at job setup with "Unable to resolve action"). Use the public actions it delegates to directly: webfactory/ssh-agent for the Git SSH identity and PumasAI/add-private-registry for the JuliaHubRegistry, JuliaSimRegistry and DyadRegistry registries, with the same two secrets. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
MultibodyComponents v0.2.1 containing the BodyShape center-of-mass fix (JuliaComputing/MultibodyComponents.jl#150) is now registered, so the temporary CI step installing it from the main branch is removed and the compat bound is raised to require the fixed release. The SSH-agent step now only runs when the secret is configured, since all dependencies are registered and only JULIAHUB_TOKEN_ENCODED is strictly needed. Full test suite passes locally against the registered v0.2.1. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The secrets context is not available in step-level if conditions, which made the workflow file invalid (runs failed instantly with no jobs). Test a job-level env flag instead, which is allowed to reference secrets. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Adds
.github/workflows/CI.ymlmirroring the MultibodyComponents CI: push/PR triggers,JULIA_PKG_SERVER: internal.juliahub.com, self-hosted runner with Julia 1.12, theset-up-private-juliahub-registriesaction (sameJULIAHUB_TOKEN_ENCODED/JULIASIM_REGISTRY_SSH_KEYsecrets),julia-buildpkg, andPkg.test()underxvfb-run.One deviation from the MultibodyComponents workflow, clearly marked TEMPORARY in the file: a step that installs MultibodyComponents from its
mainbranch before building, because the 3D models require theBodyShapecenter-of-mass fix (JuliaComputing/MultibodyComponents.jl#150) which is not yet in any registered release — a plain registry resolve gets v0.2.0 (pre-fix) and the planar/3D equivalence tests fail. Remove that step and bump theMultibodyComponentscompat bound once a fixed release is registered.Caveat on that step: it uses the SSH URL
git@github.com:JuliaComputing/MultibodyComponents.jl.gitwithJULIA_PKG_USE_CLI_GIT, assuming the SSH identity configured on the runner by the registries action can read the (private) MultibodyComponents repo. If that key is a deploy key scoped to the registry only, the step needs a different credential — or, better, just cut a MultibodyComponents release and drop the step.The workflow cannot be exercised before it lands on a branch in this repo, so this PR's first CI run is itself the test.
🤖 Generated with Claude Code