#Gha engine behaviour
1 messages · Page 1 of 1 (latest)
Sorry for the late reply.
From the CI log https://github.com/wingyplus/dagster-pipes-elixir/actions/runs/12518710875/job/34921619022?pr=13
it seems that it can get the correct version but after installed the binary, it tries to start a dev engine from source and error because the dagger source does not exist on my repo. 😦
i expected that the dev engine should not be start unless we tells the module to use it somehow.
Contribute to wingyplus/dagster-pipes-elixir development by creating an account on GitHub.
Or maybe it is my misunderstanding. The gha module intended to start dev engine that is make senses in the dagger repo but it’s not for a regular repo that wanted only stable engine.
hm, so if version is set to a semver version, it should get that
only if it's not should it try and build the dev engine
see this logic: https://github.com/dagger/dagger/blob/ebbf38a752c5bd20bc25eb0131c4160ad5348340/modules/gha/steps.go#L37-L64
ohhh
i guess the "version" can be empty 🤔
See discussion in #1323311418325471315 message, raised by @wingyplus.
This fixes the issue where an dagger version will be treated as if w...