Project is deployed to both old custom directory and new one for a single release

I have a build from TeamCity that I deploy to a custom directory on a tentacle. Initially, it was going to what I assume was a default directory, but I changed it to a custom directory. After a few false tries, it started deploying to the custom directory, but it still deploys to the old directory as well. I have the option to purge the custom directory before the deploy. I have also deleted the .Tentacle\Packages directory and the deleted all the deployed directories, but it’s still doing 2 NuGet unpacks each time I deploy a release. In case it was caching my old information, I let it sit overnight and tried another deploy, but it still had the same effect.

Can you please help me correct this?

Thanks,

John Spinosa

Hi John - thanks for getting in touch. Can you please let me know which version of Octopus you’re using, and if possible, send the relevant sections from the task log output?

Many thanks,
Nick

I’m using the free version.

Here’s the raw log output:

Task ID: ServerTasks-2264
Task status: Success
Task queued: Friday, January 10, 2014 11:36 AM
Task started: Friday, January 10, 2014 11:36 AM
Task duration: 2 minutes

                | Success: Deploy BUILD DEPLOY release 2.0.30 to

DEVBUILDSERVER2
11:37:49 Verbose | Packages acquired
11:38:08 Verbose | Deploy the build completed
11:38:08 Verbose | All steps completed
|
| Success: Acquire packages
11:36:28 Info | Downloading packages
11:36:28 Info | Making a list of packages to download
11:36:28 Verbose | The following packages will be downloaded by the
Octopus Server:
11:36:28 Verbose | - Limeade.UI.Web 1.0.0.0 (feed:
TeamCityOctodeploy)
11:36:28 Verbose | The following packages will be downloaded
directly by Tentacles:
11:37:49 Info | All packages have been downloaded
|
| Success: Download package Limeade.UI.Web 1.0.0.0
from NuGet feed: TeamCityOctodeploy
11:36:28 Verbose | Checking package cache for package
Limeade.UI.Web 1.0.0.0
11:36:29 Verbose | Package was found in cache. No need to
download. Using file:
C:\Octopus\PackageCache\feeds-1\Limeade.UI.Web.1.0.0.0_51688FE5FDD39343B8B950ACBD7F51C4.nupkg
11:36:29 Verbose | SHA1 hash of package is:
c489d61107d14e26814d76c0b6b4751342fc06a3
11:36:29 Verbose | Determining machines that need the package
|
| Success: Upload package to
https://devbuildserver2:10933/
11:36:29 Verbose | Starting Upload package to
https://devbuildserver2:10933/
11:36:29 Info | Uploading Limeade.UI.Web.1.0.0.0 (118.60 MB)
to SQ-DEVBUILDSERVER2-EC03DF5C
11:36:29 Verbose | Checking to see if the package is present on
the tentacle
11:36:29 Verbose | Uploading package Limeade.UI.Web 1.0.0.0 to
tentacle SQ-DEVBUILDSERVER2-EC03DF5C
11:36:30 Verbose | Requesting upload…
11:37:42 Verbose | File
C:\Octopus\PackageCache\feeds-1\Limeade.UI.Web.1.0.0.0_51688FE5FDD39343B8B950ACBD7F51C4.nupkg
with hash c489d61107d14e26814d76c0b6b4751342fc06a3 successfully uploaded to
SQ-DEVBUILDSERVER2-EC03DF5C
11:37:42 Verbose | Storing the uploaded file in the package cache
11:37:42 Verbose | Storing
C:\Octopus\Files\Limeade.UI.Web.1.0.0.0_51688FE5FDD39343B8B950ACBD7F51C4.nupkg-e8226594-aa6a-4b2a-a204-2fb23fefde3d
as package Octopus.Platform.Deployment.Packages.PackageMetadata
11:37:49 Info | Package Limeade.UI.Web 1.0.0.0 successfully
uploaded to tentacle SQ-DEVBUILDSERVER2-EC03DF5C
|
| Success: Step 1: Deploy the build
11:37:49 Info | Executing step: Deploy the build
|
| Success: DEVBUILDSERVER2
11:37:49 Verbose | Starting Running step “Deploy the build” on
"DEVBUILDSERVER2"
11:37:50 Info | Running “Deploy the build” on “DEVBUILDSERVER2”
|
| Success: Deploy Limeade.UI.Web on
DEVBUILDSERVER2
11:37:51 Info | Beginning deployment…
11:37:51 Verbose | Begin deployment of package:
Limeade.UI.Web.1.0.0.0Package file path:
D:\Limeade\Published\NightlyDev\Limeade.UI.Web.Tentacle\Packages\Limeade.UI.Web.1.0.0.0_21C40D3058FEF646B1935CC2C30B8B5D.nupkgPackage
file hash: c489d61107d14e26814d76c0b6b4751342fc06a3Tentacle Agent
information: - Machine name: DEVBUILDSERVER2 - Is 64-bit:
True - Service user name: SYSTEM - CLR version: 4.0.30319.17379 -
Current directory: C:\Windows\system32 - OS version: Microsoft
Windows NT 6.1.7601 Service Pack 1 - Tentacle version: 2.0.8.977
11:37:51 Verbose | Package will be extracted to:
D:\Limeade\Published\NightlyDev\Limeade.UI.Web\DEVBUILDSERVER2
11:37:57 Verbose | Looking for any configuration transformation
files
11:38:07 Verbose | Storing a record of the deployment.
11:38:07 Info | Deployment complete.
|
| Success: Copy files to
D:\Limeade\Published\OctopusDeploy\Limeade.UI.Web
11:37:57 Info | Purging the directory
’D:\Limeade\Published\OctopusDeploy\Limeade.UI.Web’
11:37:57 Info | Extracting package contents to
’D:\Limeade\Published\OctopusDeploy\Limeade.UI.Web’
|

Thanks,

John Spinosa

Thanks John.

Here’s my understanding, let me know if this matches yours:

The path D:\Limeade\Published\NightlyDev\Limeade.UI.Web\DEVBUILDSERVER2 is used for package extraction. The app won’t run from here.

The path D:\Limeade\Published\OctopusDeploy\Limeade.UI.Web is the custom installation directory you’ve configured; the package is actually being copied here, not extracted (the log message, now fixed, is a bit misleading). This is where the app will run from.

If you’re concerned about space, the best way to clean up the first copy is to set a retention policy. Go to Configuration > Retention, create a new policy, and choose a low number of builds to keep on the Tentacle. Keeping at least a couple of builds around is strongly advised, as these will make it much faster to roll back to a previous version in case a deployment goes awry.

Let me know if this helps,

Nick

Thanks! That makes sense. Can I configure the directory where the
packages are extracted? It seems to be just extracting to a default
directory that I have no control over.

John

Hi John,

Sure can! :slight_smile: On the Tentacle machine run:

Tentacle.exe service --stop
Tentacle.exe configure --appdir="C:\...(your apps dir)...."
Tentacle.exe service --start

Tentacle will still create sub-directories for various environments, package versions etc.

Let me know if you have any trouble with it.

Cheers,
Nick

That seems pretty clear, but I’d be interested to know how it initially
decides where to unpack. I don’t remember it asking me where it would
unpack when I installed the tentacle service, so I don’t know why it would
choose to unpack to that particular directory.

Thanks,

John

Hi John,

During the Tentacle setup process there’s a setting you can modify, I’ve attached a snip that shows it.

Cheers,
Nick

Hi again Nicholas,

I’ve made a huge mistake. I thought I knew my octopus login and password,
but it appears I don’t. Also, when I try to reset my password it says that
email is not configured for this account.

Can you help me recover my account? The odds are that I used johnspinosa,
johnspinosa@limeade.com, johnspinosa@gmail.com, jspinosa as my login.

Thanks,

John Spinosa

Hi John,

Hopefully no problem :slight_smile: - here’s the process: http://docs.octopusdeploy.com/display/OD/Resetting+passwords

You’ll need to use the admin option, be sure to choose the right command depending on whether you’re using AD authentication or not.

(If you can’t remember the username precisely don’t worry, the command will create a new user if necessary, with which you can log in and reset the password on the other account.)

Best regards,
Nick

Thanks, Nick. I remembered that I had enabled Active Directory, so I
already knew my password. :slight_smile: