SilverSardine Example erro in deploy

alessandro_binhara · 14 June 2013 14:41

Hello …

I try reproduce a example SilverSardine.web…
I cant deploy in tentacle… i got the erro above…

What s wrong ???

2013-06-14 14:24:45 INFO [Deploy Script] App pool exists.
2013-06-14 14:24:45 INFO [Deploy Script] Set .NET framework version: v4.0
2013-06-14 14:24:46 INFO [Deploy Script] Set identity…
2013-06-14 14:24:47 INFO [Deploy Script] Checking site…
2013-06-14 14:24:47 INFO [Deploy Script] Site does not exist, creating…
2013-06-14 14:24:47 INFO [Deploy Script] ERROR: New-Item : Filename:
2013-06-14 14:24:47 INFO [Deploy Script] ERROR: Error: Element is missing required attributes bindingInformation
2013-06-14 14:24:47 INFO [Deploy Script] ERROR: At C:\Octopus\Applications\TesteSardine\SilverSardine.Web\1.1.0.0_7\Deploy.ps1:
2013-06-14 14:24:47 INFO [Deploy Script] ERROR: 36 char:13
2013-06-14 14:24:47 INFO [Deploy Script] ERROR: + new-item <<<< $sitePath -bindings @{protocol=“http”;bindingInformation=$
2013-06-14 14:24:47 INFO [Deploy Script] ERROR: siteBindings} -id $id -physicalPath $webRoot
2013-06-14 14:24:47 INFO [Deploy Script] ERROR: + CategoryInfo : NotSpecified: ( [New-Item], FileNotFoundExcept2013-06-14 14:24:47 INFO [Deploy Script] ERROR: ion
2013-06-14 14:24:47 INFO [Deploy Script] ERROR: + FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.PowerS
2013-06-14 14:24:47 INFO [Deploy Script] ERROR: hell.Commands.NewItemCommand
2013-06-14 14:24:47 INFO [Deploy Script] ERROR:
2013-06-14 14:24:47 WARN [Deploy Script] The script returned an exit code of 0, but output was written to the error output stream. Please investigate any errors in the script output above.
2013-06-14 14:24:47 INFO [IIS] Updating IIS website named 'SilverSardine.Web’
2013-06-14 14:24:47 INFO [IIS] The IIS website named ‘SilverSardine.Web’ has had its path updated to: 'C:\Octopus\Applications\TesteSardine\SilverSardine.Web\1.1.0.0_7’
2013-06-14 14:24:47 DEBUG Storing a record of the deployment.

Trevor_Crosse · 17 June 2013 17:37

The variable $siteBindings in Deploy.ps1 is unset.

This variable is meant to hold the port or ports to bind to your new web site. In my examples below I’ve assumed that you want to bind it to port 8080 on all IP addresses. Modify to suit your situation.

You can either set this variable inside the Deploy.ps1 file in the SilverSardine.Web project or within the Octopus project.

In Deploy.ps1 you can add this to line 7:
$siteBindings = "*:8080"

Within Octopus open the Project > Variables. Create a new variable by clicking the ‘Edit Variables’ button on the upper right and then the ‘Add new’ button below the grid. Add the following row, making sure to click the ‘Save’ button above the grid when done.

Name	Value
siteBindings	*:8080

The advantage of doing it within Octopus is that you could support more complicated scenarios like this:

Name	Value	Environment	Machine
siteBindings	*:8080	Development
siteBindings	*:80	Production
siteBindings	*:85	Production	StrangeBeast
siteBindings	10.20.0.10:80	Production	MultipleIPs

HUGE CAVEAT: I haven’t actually run this example and I’m ‘just another user’, not an Octopus Certified Guy. However I verified the powershell commands from the console. With $siteBindings set correctly the site was created exactly as I expected.

But hopefully this will get you up and running.