New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes #142 - Deploy the automatic build on Appveyor #144
Conversation
@reviewbybees just in case |
@@ -2,7 +2,7 @@ | |||
export "PATH=$PATH:/cygdrive/c/Program Files/Windows Kits/8.1/bin/x86" | |||
for f in Release Debug; | |||
do | |||
signtool sign /f winsw_cert.pfx /t http://timestamp.verisign.com/scripts/timestamp.dll bin/$f/winsw.exe | |||
signtool sign /f winsw-key.snk /t http://timestamp.verisign.com/scripts/timestamp.dll bin/$f/winsw.exe |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sign script is not going to work well with the new project structure anyway. But it should not be required at all
Well, now I just need to fix the test failures. Which is good... |
This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation. |
@reviewbybees done. |
Finally I decided to try Appveyor before using VS Team Services.
The draft project is available here: https://ci.appveyor.com/project/oleg-nenashev/winsw
TODOs:
Edited by @NextTurn: Fixes #142