This message was deleted.

context: I have a test resources service which starts a server responsible for spawning test containers

As far as I know a build service is by design always build-scoped. And the

-t

triggers a new build if inputs were changed.

However, the build service gets shutdown between builds, so it destroys test containers and restarts them for every change. This is precisely what we try to avoid.

Probably a topic for a feature request if they consider this a valid use-case

I don't know if it's "by design" or an overlook. It sounds reasonable to me to provide a build session scoped version.

Quite possible, just not implemented as far as I'm aware

if you can think of any workaround, because this is quite a blocker 😕

Nothing halfway clean that comes to mind. You probably would need to store some static state if you really want to do that, but using static state is quite cumbersome, especially if you then build different branches and so on.

every time you use static state a puppy dies

And drags a kitten with it