DNNCommunity
Deployment from command line returns failure, but did install
I have deployments that use the command line tool through Octopus Deploy. Octopus Deploy is saying the deployment step with Polydeploy failed because polydeploy returns a failure. However when I go to my DNN site all the module versions updated, the database updated, and I all the views update. It appears that the deployment was really successful. How can I best trouble shoot this issue and see if it is something on my end or if there is a possible bug in the command line tool? When I look through the PolyDeploy logs I dont see any failures, but maybe I am looking in the wrong place.
Are you recording the output from the command line tool? Is it showing something like this:
10/10 module archives processed, 9/10 succeeded.
When I get that, I have to look through the Host Alerts logged in the Event Log to find which errored and why.
Looking at the Host Alerts for the install today and they both say Successful. However, looking at the logged console output of the poly deploy client I see this error:
Exception caught at: 3/13/2019 2:17:39 PM.
March 13th 2019 14:18:03Info
System.ArgumentNullException | Value cannot be null.
March 13th 2019 14:18:03Info
Parameter name: input
March 13th 2019 14:18:03Info
at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize(JavaScriptSerializer serializer, String input, Type type, Int32 depthLimit)
March 13th 2019 14:18:03Info
at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize[T](String input)
March 13th 2019 14:18:03Info
at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
March 13th 2019 14:18:03Info
at DeployClient.Program.<Main>d__2.MoveNext() in C:\DNNDev\CantarusCore\PolyDeploy\DeployClient\Program.cs:line 183
So it looks like it was successful, but it was unable to continue. Could it be a timeout issue where the modules get installed, but the site is taking a while to come back online and a call is failing and returning null?