Bitbucket Pipelines Build Info

I’m following this article regarding to the integration of bitbucket pipelines with octopus. But in the part of producing the build information I’m not able to succeed.

The code related to the pipeline is the following one:


octo pack --basePath=./dist --id $BITBUCKET_REPO_SLUG-$BITBUCKET_BRANCH --version $VERSION --outFolder ./out --format zip

octo push --package ./out/$BITBUCKET_REPO_SLUG-$BITBUCKET_BRANCH.$ --server $OCTOPUS_SERVER --apiKey $OCTOPUS_APIKEY --debug


octo build-information --package-id $BITBUCKET_REPO_SLUG-$BITBUCKET_BRANCH --logLevel=verbose --version $VERSION --file=octopus.buildinfo --server $OCTOPUS_SERVER --apiKey $OCTOPUS_APIKEY

octo create-release --project Royaltyflush --server $OCTOPUS_SERVER

And the error is

+ octo build-information --package-id $BITBUCKET_REPO_SLUG-$BITBUCKET_BRANCH --logLevel=verbose --version $VERSION --file=octopus.buildinfo --server $OCTOPUS_SERVER --apiKey $OCTOPUS_APIKEY

Octopus Deploy Command Line Tool, version 6.17.3


Detected automation environment: "BitBucket"

DispatchRequest: GET

DispatchRequest: GET

DispatchRequest: GET

DispatchRequest: GET

Space name unspecified, process will run in the default space context

Handshaking with Octopus Server:

DispatchRequest: GET

Handshake successful. Octopus version: 2020.2.11; API version: 3.0.0

DispatchRequest: GET

DispatchRequest: GET

DispatchRequest: GET

DispatchRequest: GET

Authenticated as: admin <>

Pushing build information for package "royaltyflush.backend-dev" version "1.0.404"...

DispatchRequest: POST

Octopus Server returned an error: Object reference not set to an instance of an object.

Error from Octopus Server (HTTP 500 InternalServerError)

Exit code: -7

Does anybody have a clue how can I tackle this?

Hi @royaltyflush,

Thanks for reaching out. Sorry you’re having issues with your build information. The first thing that jumps out at me is your CLI tool is a bit old. Would you be able to update that and retry pushing the build information? Could you please check your Octopus Server logs to see if there is more detail about the error at the corresponding time? The default location for those is C:\Octopus\Logs .

There is also a newer blog from Mark where he explains the benefits of using octopus-cli-run, if you wanted to try that.

Please let me know how it goes once you’ve had a chance to update and check for additional logs.


Hi Jeremy, thanks for the reply.
When you say that my cli is old you’re talking about the syntax?
Currently on my pipe i’m using this:

name: Deploy to Octopus
image: octopusdeploy/octo:6.17.3-alpine
script: …

Regarding to logos, I don’t find anything related to the subject not even to deployment process. Only see updates and installation processes regarding to server, nothing regarding to operations.

Hi @royaltyflush,

When I say the cli is old, I mean the actual tool itself.

Here is a link to the latest, which is 7.3.7, and you are currently on 6.17.3. You would just need to update the CLI tool on your build server.

Please let me know if you have other questions regarding this.


This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.