Issue Creating and Deploying builds from the command line

Legacy Uncategorised
1

I just upgraded to 1.0.16.1276 (from .9.x)

The upgrade seems to have done smoothly.

I updated my octo.exe with the latest and added the -apiKey to the command line of the bulid script.

My script adds a release and then tries to deploy that release.
The problem is that the release appears to get created, but then isn’t available to deploy:

[exec] Octopus Command Line Tool, version 1.0.0.0
[exec] Finding project: Solana.WebApplications
[exec] Handshaking with Octopus server: http://wrangler/api
[exec] Handshake successful. Octopus version: 1.0.16.1276; API version: 1.0.0
[exec] Finding environments...
[exec] Finding steps for project...
[exec] Getting package versions for each step...
[exec] Solana.WebApplications - latest: 4.46.7918.3
[exec] Solana.WebApplications - latest: 4.46.7918.3
[exec] Solana.DataProcessing.Service - latest: 4.46.7918.3
[exec] Solana.DataProcessing.Service - latest: 4.46.7918.3
[exec] Creating release: 4.46.7918.3
[exec] POST http://wrangler/api/projects/projects-1/releases
[exec] Release created successfully!
[exec] Octopus Command Line Tool, version 1.0.0.0
[exec] Finding project: Solana.WebApplications
[exec] Handshaking with Octopus server: http://wrangler/api
[exec] Handshake successful. Octopus version: 1.0.16.1276; API version: 1.0.0
[exec] Finding environments...
[exec] Finding release: 4.46.7918.3
[exec] Argument error:
[exec] A release named '4.46.7918.3' could not be found.

I don’t see that release when I look at releases through the web (or the API…is there some command that is used to get a second page?)
If I try to add a new release with that name, it gives an error that that
"A release named version ‘4.46.7918.3’ already exists. Please enter a different version number."

What can I do to get this back up and running?

2

As an update to this. The releases that it creates now are appearing in the web site, so they appear to be being added correctly.

The automated release is still giving the same error:

A release named ‘4.47.7925.2’ could not be found.

3

Hi Lynn,

Thanks for letting me know, I suspect this might be a caching issue - I’ll investigate it.

https://trello.com/card/releases-can-t-be-found-after-creating-them-from-octo-exe/4e907de70880ba000079b75c/153

Paul

4

Hi Lynn,

I think I have fixed this in build 1.0.17.1287, but I can’t be sure since i couldn’t really reproduce the original bug (I think it was just a timing thing). Can you let me know if it works?

Paul

5

Unfortunately, this doesn’t seem to have fixed the issue for me.

Here’s the log of what happened.

[exec] Octopus Command Line Tool, version 1.0.0.0
[exec] Finding project: Solana.WebApplications
[exec] Handshaking with Octopus server: http://wrangler/api
[exec] Handshake successful. Octopus version: 1.0.17.1287; API version: 1.0.0
[exec] Finding environments...
[exec] Finding steps for project...
[exec] Getting package versions for each step...
[exec] Solana.WebApplications - latest: 4.47.7931.2
[exec] Solana.WebApplications - latest: 4.47.7931.2
[exec] Solana.DataProcessing.Service - latest: 4.47.7931.2
[exec] Solana.DataProcessing.Service - latest: 4.47.7931.2
[exec] Creating release: 4.47.7931.2
[exec] POST http://wrangler/api/projects/projects-1/releases
[exec] Release created successfully!
[exec] Octopus Command Line Tool, version 1.0.0.0
[exec] Finding project: Solana.WebApplications
[exec] Handshaking with Octopus server: http://wrangler/api
[exec] Handshake successful. Octopus version: 1.0.17.1287; API version: 1.0.0
[exec] Finding environments...
[exec] Finding release: 4.47.7931.2
[exec] Argument error:
[exec] A release named '4.47.7931.2' could not be found.

The release does show up in the UI and deployment works fine from that point on.

I tried waiting a few minutes and running the deploy-release again and I get the same error. (this was even after it had deployed via the web app)

6

Hi Lynn,

Ahh, I see the problem now. The releases aren’t sorted and Octo.exe is only listing the last 20 releases, it doesn’t navigate to the next page. I’ll fix it in today’s release.

Paul

7

Hi Lynn,

This should now be fixed:

Paul

8

Thanks Paul. The latest release fixes my issue.