Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release is created if a package is pushed using external feeds #5564

Closed
5 tasks done
mudra-octopus opened this issue May 13, 2019 · 2 comments
Closed
5 tasks done

Release is created if a package is pushed using external feeds #5564

mudra-octopus opened this issue May 13, 2019 · 2 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving
Milestone

Comments

@mudra-octopus
Copy link

mudra-octopus commented May 13, 2019

Prerequisites

  • I have verified the problem exists in the latest version
  • I have searched open and closed issues to make sure it isn't already reported
  • I have written a descriptive issue title
  • I have linked the original source of this report
  • I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

When a project has a step that uses a package from an external nuget feed and
automatic release creation is configured for that step, on pushing a package to the built-in nuget feed matching the package id of the package that step is used, then release should not be created - it's the correct package but incorrect feed

Steps to reproduce

  1. Create a deployment step with External feed.
  2. Set ARC true.
  3. Push the feed with the same package selected in the both above.
  4. Release should not be created. But it is created.

How to test:

The test step ReleaseIsNotCreatedIfPackagePushedIsNotUsedFromBuiltInFeed in the test NuGetPackagePushTestScript should pass.

Current behaviour:

Expected collection to be empty, but found {

Octopus.Client.Model.ReleaseResource
{
@mudra-octopus mudra-octopus added the kind/bug This issue represents a verified problem we are committed to solving label May 13, 2019
@octoreleasebot octoreleasebot added this to the 2019.5.4 milestone May 17, 2019
@octoreleasebot
Copy link

Release Note: Automatic release creation can no longer be configured to use a package sourced from an external feed

@lock
Copy link

lock bot commented Aug 15, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants