You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are 2 situations where NSIS does not exists on the build system:
it's not a Windows machine
it was not installed
If NSIS is not available we should handle it gracefully in ccnet-packaging.inc.build, targets:
packageCCTray
packageCCTools
packageCCNET
I'm thinking if not on Windows it should display something like "CruiseControl.NET windows installers can only be created on Windows". But if the script runs on Windows but nsis.executable is empty / does not exist then it should fail the build.
There are 2 situations where NSIS does not exists on the build system:
If NSIS is not available we should handle it gracefully in ccnet-packaging.inc.build, targets:
I'm thinking if not on Windows it should display something like "CruiseControl.NET windows installers can only be created on Windows". But if the script runs on Windows but nsis.executable is empty / does not exist then it should fail the build.
Original discussion on PR #301
The text was updated successfully, but these errors were encountered: