octopus-deploy

I am using NUGET Pack in teamcity to build a package. But it is creating the following error. I am using nuget teamcity version 2.2.1. Step 2/2: Build Package (NuGet Pack) (14s) [12:10:40][Step 2/2] Cleaning Z:\hgbuilds\IT\Build\packages [12:10:40][Step 2/2] pack: Create NuGet package from UI\UI.Tour\UI.Tour.Web\UI.Tour.Web.csproj (14s) [12:10:40][pack] NuGet command: C:\BuildAgent\tools\NuGet.CommandLine.2.2.1.nupkg\tools\NuGet.exe pack Z:\hgbuilds\IT\UI\UI.Tour\UI.Tour.Web\Calrom.UI.InclusiveTour.Web.csproj -OutputDirectory Z:\hgbuilds\IT\Build\packages -BasePath Z:\hgbuilds\IT -Verbose

I use Octopus for our deployments. I have a problem with one of the Powershell scripts to control the deployment: # stops running processes $processes = @("Notepad", "Firefox") foreach ($process in $processes) { $prc = Get-Process -Name $process -ErrorAction SilentlyContinue if (-not($prc -eq $null)) { Write-Host "Stopping " $prc.ProcessName Stop-Process -InputObject $prc -ErrorAction SilentlyContinue } } The programs I try to stop are not the ones you see in the script above, but they represent what I am trying to do. Now the problem I have with it, is that it works well on one server, but

On a current project we are using Teamcity and Octopus for building and deploying our IIS app. We have 4 environments. The CI Environment (automated build on checkin, runs unit tests, and automated QA tests), and the QA, UAT, and Prod Environments (which we push to manually using Octopus). On local (dev) builds, the default build script pushes directly to a local Octopus instance for testing purposes. Would it be better practice to have the CI build (which runs quite frequently) to follow a similar model as the local build (and push directly to a Tentacle instance, instead of through the

I have set up a build step on TeamCity,as described here , to do automatic release deployments to our test server. But it is not using the latest nuget packages that was build in TeamCity. Use Case : Teamcity will create nuget package with version 1.0.0.9, all the dlls that is in the package is the correct version, and the Release in Octopus, that was deployed has got the same version number , but the packages that octopus uses is of an earlier package eg 1.0.0.5. I have specified the --force parameter on the build step so it should use the latest packages but it is not. If I manually create a

So I'm actually trying to package up a web site project (not web application so no csproj file) into a NuGet package ready for Octopus to consume but am running into one brick wall after another.. I looked into using OctoPack but it doesn't support web site projects only web application projects. I am now trying to find a way of adding a folder (in my case a web site) into a Nuget package but Nuget doesn't allow this via the command line does it? It also requires a .csproj file! I've also tried trying to create the NuGet spec files and pass it in a folder but not possible? For the moment I may