honest patio
I once encountered a problem where I had 2 projects on different versions of Dagger. As I switched building each, the latest invocation would kill the one that was currently running, because it wanted to replace the dagger-engine container
Is this still an issue?
How should I handle builds from different branches / versions the run concurrently on the same Jenkins worker?
tulip epoch
I once encountered a problem where I had 2 projects on different versions of Dag...
if your worker is stateful - which I assume it is given that you have this issue - you can start the dagger engines you need and then set the _EXPERIMENTAL_DAGGER_RUNNER_HOST=docker-container://$container_name variable for each corresponding pipeline and that will prevent your pipelines to shutdown already existing engines
honest patio
I haven't deployed it out to workers yet, but I've seen this happen locally between different projects
Is there a doc out there for how/where to configure things like this, and the dagger-engine container?
tulip epoch
I haven't deployed it out to workers yet, but I've seen this happen locally between different projects
yes, that's how it works locally by default. There's an issue to improve that here: https://github.com/dagger/dagger/issues/3849
