Psuh Packages to Octopus keeps failing on me

Legacy Execution
1

The issue I keep getting is this… any are intentional replacements.

2017-06-12T10:33:41.5755844Z ##[command]“D:<WorkingFolder>_tasks\OctopusPush_\2.0.75\Octo.exe” push --server=http:///OctopusDeploy/nuget/packages/ --apiKey=******** --proxy=http://:8080 --package=“D:<WorkingFolder>\22\a\DevApp.20170612.6.nupkg” --replace-existing
2017-06-12T10:33:41.6537083Z Octopus Deploy Command Line Tool, version 4.13.11
2017-06-12T10:33:41.6537083Z
2017-06-12T10:33:42.2474580Z The resource you requested was not found.
2017-06-12T10:33:42.2474580Z Error from Octopus server (HTTP 404 NotFound)
2017-06-12T10:33:42.2474580Z Exit code: -7
2017-06-12T10:33:42.4193369Z ##[error]Process ‘Octo.exe’ exited with code ‘-7’.
2017-06-12T10:33:42.4351436Z ##[section]Finishing: Push Packages to Octopus

These are the steps in the build definition. The first two steps work great and can see the generated nuget file on the build server.

  1. Package Application - Pass
  2. Public Build Artifact - Pass
  3. Push Packages to Octopus - Fail

The endpoint has been created with the correct url api key and api key.

Does any one have ideas as to what I’m doing wrong?

2

I have attached the log files with intentional replacements

logs_1054_2.zip (5 KB)

3

Hi Simon,

Thank you for getting in touch. The --server parameter takes the root path of the Octopus server (unlike when you push with nuget). Try --server=http:///OctopusDeploy.

Hope that helps

Robert W

1 Like
4

Thanks Robert, that worked first time.