Andrei Boar

@Equanox @rdnt I think we need to prio "Maybe find a way to lock nixpkgs version. " in the context of launching the remote store. Builds should use the same...

> @zuzuleinen if nix-pkgs is not explicitly specified, the latest stable commit hash should be used, and embedded into the artifacts that are built, as if it was declared in...

> @zuzuleinen if nixpkgs version is added as input to artifacts, then it is okay if future builds will use a more recent nixpkgs. Old artifacts will become stale and...

> A restart must be able to be cancable (by listening to the context as we do it with build).. E.g. A restart is immediately followed by a ctrl+c (send...

**Testing wait for init to finish before restarting** 1. In example/server-db add init to the server run task: ```yaml run: server: type: binary path: ./build/server dependson: - build - database...

Anyone found a solution?

> **Push** After playing around with the push workflow i think it would be better to only push on request. Especially when testing/experimenting locally a push of big artifacts (e.g....

> @Equanox @zuzuleinen `bob build --push` sounds good to me, and I agree, pull should be enabled by default (maybe also consider a flag `--no-pull` if the user doesn't want...

After discussing with @Equanox we decided to go with @rdnt version: bob build --push sounds good to me, and I agree, pull should be enabled by default (maybe also consider...

I think it's a good idea. We can even make pinning nixpkgs per-package level. We should also check [rules_nixpkgs](https://github.com/tweag/rules_nixpkgs) for inspiration: ```bazel nixpkgs_git_repository( name = "nixpkgs", revision = "17.09", #...