OctopusDeploy: Push package Error: Please specify a package to push

Legacy Uncategorised
1

Hi,
I am having problems using the OctopusDeploy: Push package runner. The step always fails. Screen shots attached.Log looks like the following:

[18:37:16]Collecting changes in 1 VCS root
[18:37:16][Collecting changes in 1 VCS root] VCS Root details
[18:37:16][VCS Root details] “https://brianm-millmats@bitbucket.org/virtuosomm/virtuoso-webapi.git#refs/heads/master” {instance id=3, parent internal id=1, parent id=VirtuosoWebapi_HttpsBrianmMillmatsBitbucketOrgVirtuosommVirtuosoWebapiGitRefsHea, description: “https://brianm-millmats@bitbucket.org/virtuosomm/virtuoso-webapi.git#refs/heads/master”}
[18:37:21]The build is removed from the queue to be prepared for the start
[18:37:21]Starting the build on the agent Agent 007
[18:37:23]Clearing temporary directory: C:\BuildAgent\temp\buildTmp
[18:37:23]Publishing internal artifacts (1s)
[18:37:24][Publishing internal artifacts] Publishing 1 file using [ArtifactsCachePublisher]
[18:37:24][Publishing internal artifacts] Publishing 1 file using [WebPublisher]
[18:37:23]Will perform clean checkout. Reason: Checkout directory is empty or doesn’t exist
[18:37:23]Checkout directory: C:\BuildAgent\work\d1df6864f98d2599
[18:37:23]Updating sources: auto checkout (on agent)
[18:37:23][Updating sources] Will use agent side checkout
[18:37:23]Step 1/1: Push package to Octopus (OctopusDeploy: Push packages) (1s)
[18:37:23][Step 1/1] Octopus Deploy
[18:37:23][Octopus Deploy] Running command: octo.exe push --server http://cintasqa.millmats.com/deploy --apikey SECRET
[18:37:23][Octopus Deploy] Pushing packages to Octopus server
[18:37:23][Octopus Deploy] Octopus Deploy Command Line Tool, version 3.4.2+Branch.master.Sha.869d64eaf5d2657a5daadda886a2dd697e2a024c
[18:37:23][Octopus Deploy]
[18:37:24][Octopus Deploy] Handshaking with Octopus server: http://cintasqa.millmats.com/deploy
[18:37:24][Octopus Deploy] Handshake successful. Octopus version: 3.4.15; API version: 3.0.0
[18:37:24][Octopus Deploy] Authenticated as: “TeamCity Service” <""> “(a service account)”
[18:37:24][Octopus Deploy] Please specify a package to push
[18:37:24][Octopus Deploy] Exit code: -1
[18:37:24][Octopus Deploy] Octo.exe exit code: -1
[18:37:24][Step 1/1] Unable to create or deploy release. Please check the build log for details on the error.
[18:37:24][Step 1/1] Step Push package to Octopus (OctopusDeploy: Push packages) failed
[18:37:24]Publishing internal artifacts
[18:37:24][Publishing internal artifacts] Publishing 1 file using [ArtifactsCachePublisher]
[18:37:24][Publishing internal artifacts] Publishing 1 file using [WebPublisher]
[18:37:24]Build finished

Screen1.jpg
Screen1.jpg1624×835 207 KB

Virtuoso_Webapi_Deploy_to_Octopus_Repository_1611.log (3 KB)

2

Log file of Snapshot dependency that creates package

Virtuoso_Webapi_API_Build_1.0.16.log (202 KB)

3

Hi Brian,

Thanks for getting in touch!

From looking at the build log of the snapshot dependency build and the configuration screenshot you sent through, it looks like you may have gotten the filepath incorrect? I’ve search through the logs for VirtuosoWebapi but can’t find any filepaths that include Webapi, I can only find Virtuoso.

Although, our Push packages build step is actually more like a Generate package from build output and push it to Octopus build step, so when you use it as part of a dependency build it might not work as the build output is possibly not available. So you could either move the Push packages build step into your main build defenition or make the dependency an artifact dependency and in the build that is currently failing push the package using NuGet: Publish

Hope that helps!

Thank you and best regards,
Henrik