Missing variable causes tentacle to exit with no error in the dashboard

It would be nice if the error below can be seen from the dashboard. Loving the new features BTW, just setup the no-server deploy feature today.

From the octopus dashboard, this is the last few lines of the (raw) deploy log:
2013-03-07 05:58:27 DEBUG - Current directory: C:\Windows\system32
2013-03-07 05:58:27 DEBUG - OS version: Microsoft Windows NT 6.1.7601 Service Pack 1
2013-03-07 05:58:27 DEBUG - Tentacle version: 1.4.0.1592

Then nothing. The same for the .Tentacle/Log/.log file.

The following was found in the Windows Event viewer:
2013-03-07 15:58:27,737 [5] ERROR Octopus [(null)] - Error while executing job: The variable ‘DmattConnectionString’ contains a reference to another variable named ‘SqlUser’, which is not defined. Set the special variable OctopusPrintVariables to have Tentacle print the value of all variables to help diagnose this problem.
System.Exception: The variable ‘DmattConnectionString’ contains a reference to another variable named ‘SqlUser’, which is not defined. Set the special variable OctopusPrintVariables to have Tentacle print the value of all variables to help diagnose this problem.
at Octopus.Shared.Contracts.VariableEvaluator.ParseDependencies(List`1 nodes, Configuration config) in c:\w\e6923628be6eaf72\source\Octopus.Shared\Contracts\VariableEvaluator.cs:line 62
at Octopus.Shared.Contracts.VariableEvaluator.Evaluate(VariableDictionary variables) in c:\w\e6923628be6eaf72\source\Octopus.Shared\Contracts\VariableEvaluator.cs:line 20
at Octopus.Tentacle.Deployment.DeploymentController.Execute(StoredPackage package, VariableDictionary variables, IActivityLog log) in c:\w\e6923628be6eaf72\source\Octopus.Tentacle\Deployment\DeploymentController.cs:line 52
at Octopus.Tentacle.Services.Jobs.JobQueue.RunDeploymentsOnBackgroundThread(Object ignored) in c:\w\e6923628be6eaf72\source\Octopus.Tentacle\Services\Jobs\JobQueue.cs:line 80

Hi Robert,

Thanks for the bug report and sorry for this, I’m sure it took far too long to track down for what should be a simple error. It will be fixed in the next release.

Paul

Cool :). I’ll admit it didn’t take too long, just interesting.

Keep up the good work.