octo.exe error

[smadiganBpe]

Hello,

After numerous successful Octo.exe operations, we've started getting 400s from the server:

[14:43:50]Handshaking with Octopus server: http://10.12.10.175:8066/api [14:43:50]Handshake successful. Octopus version: 0.9.620.4 [14:43:50]Finding environments... [14:43:50]Finding steps for project... [14:43:50]Getting package versions for each step... [14:43:50]1. ConstellationWeb - latest: 0.105 [14:43:50]A --version parameter was not specified, so a version number was automatically selected based on the highest package version: 0.105 [14:43:50]Creating release: 0.105 [14:43:51]The remote server returned an error: (400) Bad Request. Bad Request [14:43:51]System.Exception: The remote server returned an error: (400) Bad Request. Bad Request

(Above is a log from teamcity)

Are there logs on the server that can be examined? Any advice on a fix or workaround?

thanks! Steve

[PaulStovell]

Hi Steve,

Are any other details included in the output? The 400 Bad Request should contain error details.

My guess is that a release already exists for that version - can you check if release 0.105 already exists?

Paul

[smadiganBpe]

Hi Paul,

There are no other details in the output, just what I sent you. I do believe you are correct, that a release already exists for the version. Is there a log anywhere or some other way to analyze these kind of failures?

FYI I saw someone ask about automatically deploying from teamcity and how it distributes the previous release instead of the new one. We hit this problem as well -- the reason it doesn't work as expected is because until the team city build is fully complete, the new version does not yet exist in teamcity. It's not a problem with Octo.exe

The way to do this in team city is to set up a configuration or a project that contains only the octo.exe invocation, and have this configuration/project triggered by the completion of a build in the core project you're concerned about. I can provide more details upon request.

By the way we call one of these octo.exe invocations an "Octopush" ;-)

Thanks for the timely response. We're pretty excited about replacing msdeploy with the power and simplicity of Octopus!

Best regards, Steve

On 4/12/12 6:13 PM, "Paul Stovell" <reply+i-4060875-f2849dcc514cbca96c628728dfb3cdabf41773fc-1632234@reply.git hub.com> wrote:

Hi Steve,

Are any other details included in the output? The 400 Bad Request should contain error details.

My guess is that a release already exists for that version - can you check if release 0.105 already exists?

Paul

---

Reply to this email directly or view it on GitHub: https://github.com/OctopusDeploy/Octopus-Tools/issues/10#issuecomment-5106 642

IMPORTANT NOTICE: This e-mail message is intended to be received only by persons entitled to receive the confidential information it may contain. E-mail messages sent from this company may contain information that is confidential and may be legally privileged. Please do not read, copy, forward or store this message unless you are an intended recipient of it. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.

[smadiganBpe]

Paul,

I'm having trouble with running powershell scripts (postdeploy.ps1) that require an Import-Module - the import fails when running in the Octopus host, but works fine when running from the powershell command line. The module in question is failoverclusters. Any advice you can offer? (Octopus tentacle agent is running under local system account if that matters.)

(I tried to post this in the discussions but the post failed)

thanks in advance Steve

IMPORTANT NOTICE: This e-mail message is intended to be received only by persons entitled to receive the confidential information it may contain. E-mail messages sent from this company may contain information that is confidential and may be legally privileged. Please do not read, copy, forward or store this message unless you are an intended recipient of it. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.

[PaulStovell]

Hi Steve,

The discussion post seemed to come through OK, I just replied to it here:

http://help.octopusdeploy.com/discussions/problems/367-powershell-scripts-and-import-module

Paul

-----Original Message----- From: Steve Madigan [mailto:reply@reply.github.com] Sent: 14 June 2012 19:24 To: Paul Stovell Subject: Re: [Octopus-Tools] octo.exe error (#10)

Paul,

I'm having trouble with running powershell scripts (postdeploy.ps1) that require an Import-Module - the import fails when running in the Octopus host, but works fine when running from the powershell command line. The module in question is failoverclusters. Any advice you can offer? (Octopus tentacle agent is running under local system account if that matters.)

(I tried to post this in the discussions but the post failed)

thanks in advance Steve

IMPORTANT NOTICE: This e-mail message is intended to be received only by persons entitled to receive the confidential information it may contain. E-mail messages sent from this company may contain information that is confidential and may be legally privileged. Please do not read, copy, forward or store this message unless you are an intended recipient of it. If you received this transmission in error, please notify the sender by reply e-mail and delete the message and any attachments.

---

Reply to this email directly or view it on GitHub: https://github.com/OctopusDeploy/Octopus-Tools/issues/10#issuecomment-6336604