Ian Denhardt

Hm, it seems like for your use case it might just be better to provide a way to skip building the .spk entirely, and just output the contents to a...

I'm thinking a `--directory` flag to `docker-spk build`.

Glad you worked your way through it. Yeah, it probably isn't actually helpful in your case then. Hopefully I'll eventually get around to supporting searchPath, so it isn't necessary to...

Yeah, I think we could do something where we just included the full packagePath for each entry in searchPath, in addition to what gets built in to the docker container.

Definitely interested in exploring this. The big question I have is, what does package signing look like in this environment? It's probably best to start by sketching what we want...

If you're just looking to test that the package builds ok, it's pretty common to use docker as part of Travis. In that case you could just do `docker-spk build...

For that workflow, pipeline 3 would probably just use docker itself, just doing `docker build`/`docker run`. docker-spk just invokes these commands itself, so besides shoving it in the spk there...

One possible improvement I can think of is that if we can tweak things so you can sign the package with the correct key *after* testing, the build pipeline could...

We could also add a variant of `spk publish` that re-signs and publishes in one step, so you can effectively just test & upload, which seems like more of a...

Sounds good, I'll wait to hear.