MSI 3010 is concidered an build failure
I have a build configuration that deploys a bootstrapper exe to a vm for testing.
This is done through an SSH Exec build step.
The installer requires a restart at the end of the install process.
This produces a 3010 error which is ERROR_SUCCESS_REBOOT_REQUIRED however Team city will call this a failure.
Is there a way to configure 3010 error to be a success?
Please sign in to leave a comment.
Hi! SSH Exec will fail if the command that it executes returns the control with a non-zero exit code. To make it successful, you will need to handle the 3010 exit code in your script.
I'm aware that this won't make any difference, but it is quite frustrating as the process finishes and reboots as intended with an msi 3010 return. Despite 3100 being a success in msiexec; team city only accepts 0 as a success which is quite frustrating and would be useful to be a configurable option.
Could you please share a bit more details about why you find that frustrating? In my understanding, achieving the desired behavior is a matter of adding one line to your install script. Something along the lines of