Could not find package in feed

Integration
1

Could not find package in feed

We are using teamcity to build package. Create deploy release step succeeds but in octopus ‘Tasks’ it shows error as "Could not find package in feed "

2

Hi @pranitas, thanks for reaching out.

From what you have described it sounds like an Octopus project is referencing packages that have not bee uploaded yet.

The deploy release step does not upload any packages to Octopus, it only starts the deployment of the release. To push a package to Octopus you need to use the OctopusDeploy: Push Packages step before the release is created.

image
image.png1348×684 24.4 KB

So the usual process for creating a deployment in Octopus from TC is:

  1. Build the artifacts with TC
  2. Push the artifacts to Octopus
  3. Create an Octopus release
  4. Deploy an Octopus release

The blog post at https://octopus.com/blog/octopus-build-server-integration-101 has more information on the typical build process between a CI server and Octopus.

Regards
Matt C

3

Thank you for your reply.

When i check ‘Artifacts’ in teamcity for project, it says, 'No user-defined artifacts ’

I guess, will need to get step 1 working now.

We are using Bitbucket as source repository. It works fine with svn as repository.

5

@Matthew_Casperson

To resolve artifact issue i found this page ‘https://help.octopusdeploy.com/discussions/questions/2304-teamcity-804-not-creating-nuget-packages’

I have ‘Run Octopack’ enabled in build step.

Its mentioned here, From TeamCity, it’s common to use %build.number% so that the package version number matches the TeamCity build number.

I am not sure if we can use same build number when source repo is bitbucket, as buildnumber is alphanumeric something like ‘1f8c0526a56’

6

Hi @pranitas

The %build.buildnumber% variable is generated by Team City itself rather than the source repository. You can find more information on these variables with the TC documentation at https://confluence.jetbrains.com/display/TCD10/Predefined+Build+Parameters. This means you are able to use %build.buildnumber% with BitBucket.

Regards
Matt C

7

Hi Matthew
Thanks for your reply. I have managed to get this working. Solution was setup incorrectly which caused this issue. Deleting and re-creating it on bitbucket has worked now.
Thanks

9

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