vpk pack: emit signtool output immediately rather than capturing and printing it at the end #81
Comments
|
I would love this, but unfortunately, I don't think this will be possible at the moment. vpk actually is not capable of capturing signtool output at all, it runs signtool as a new process under cmd.exe and redirects the stdout to a file - which is then read back in after the process exits. The reason for doing this, is when we migrated vpk into a https://github.com/velopack/velopack/blob/develop/src/Velopack.Packaging.Windows/CodeSign.cs#L104 We'd need to find a different way of launching signtool.exe which does not rely on piping stdout to a file, and also preserves signtool HSM functionality. |
I'm asking for a better debugging experience when working with signtool in a non-interactive CI pipeline.
I'm invoking signtool with a dlib which makes network calls. As part of this, it needs login credentials. There are a handful of ways it can accept non-interactive credentials, but when I forget to specify them, the behavior of
vpk packmakes it difficult to see what's going on.The dlib is prompting me for interactive credentials, but because vpk captures stdout, this prompt is never emitted and the pack process hangs indefinitely with no visual indication of what's happening. I need an immediate way to see this.
The text was updated successfully, but these errors were encountered: