Just to set the context right, we are using xml2iis (an vbscript utility) to
create the website as the WIX <iis:WebSite> doesn't support all the IIS
properties we intend to set. This xml2iis utility gets called in a custom
action of the MSI.
Question still holds good - how do we get the octopuscli to return the error
when the custom action fails.
Thanks,
Chandra
From: Pierson Lee (Volt)
Sent: Wednesday, November 14, 2007 5:23 AM
To: wix-users@lists.sourceforge.net
Cc: Michael Thurlkill; Chandra Mohan
Subject: RE: capturing errors from deployment using octopusCLI
<Forwarding to WiX list>
Does anyone know how to fail an MSI install with an error code if the website
fails to be installed/configured? I was think of Windows Service and thought
there was a way to do the <iis:WebSite> also but there doesn't seem to be.
Any help is appreciated.
Thanks
Pierson
From: Michael Thurlkill
Sent: Tuesday, November 13, 2007 3:46 PM
To: Pierson Lee (Volt); Chandra Mohan
Subject: RE: capturing errors from deployment using octopusCLI
We're using Wix. Chandra did most of the work, but I know just enough to be
dangerous.
From: Pierson Lee (Volt)
Sent: Tuesday, November 13, 2007 3:43 PM
To: Michael Thurlkill; Chandra Mohan
Subject: RE: capturing errors from deployment using octopusCLI
Are you creating your MSIs through WiX or using something else?
From: Michael Thurlkill
Sent: Tuesday, November 13, 2007 3:38 PM
To: Pierson Lee (Volt); Chandra Mohan
Subject: RE: capturing errors from deployment using octopusCLI
So, how do you do that?
Chandra, you probably know more about this than I do. Can you help work out
how to get the error code out of the msi and octopus?
From: Pierson Lee (Volt)
Sent: Friday, November 09, 2007 6:14 PM
To: Michael Thurlkill
Subject: RE: capturing errors from deployment using octopusCLI
I think you need to mark it critical in your MSI so the MSI install fails if it
can't install the site. That's what I did to get Octopus to error
From: Michael Thurlkill
Sent: Friday, November 09, 2007 6:13 PM
To: Pierson Lee (Volt)
Subject: RE: capturing errors from deployment using octopusCLI
Yes. I can see the errors from the msi in the octopus log. I just don't
appear to get an errorcode out of octopus.
From: Pierson Lee (Volt)
Sent: Friday, November 09, 2007 5:55 PM
To: Michael Thurlkill; Octopus Discussions
Subject: RE: capturing errors from deployment using octopusCLI
Are you deploying the website through an MSI?
From: Michael Thurlkill
Sent: Friday, November 09, 2007 12:25 PM
To: Michael Thurlkill; Octopus Discussions
Subject: RE: capturing errors from deployment using octopusCLI
Does anyone deploy websites using Octopus?
From: Michael Thurlkill
Sent: Thursday, November 08, 2007 4:39 PM
To: Octopus Discussions
Subject: capturing errors from deployment using octopusCLI
We are using octopuscli in an automated job to deploy a webapp to several web
servers.
If it is unable to deploy to one or more servers we would like to know and
return failure for the job.
I'm not seeing a way to do this other than parsing the logs to look for errors.
Is there a way to cause octopus to return an error code?
How are other teams dealing with this kind of scenario?
Thanks
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
