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

project.VersioningStrategy.DonorPackage is null exception on Project settings page #5491

hnrkndrssn opened this issue Apr 18, 2019 · 2 comments


Copy link

commented Apr 18, 2019


  • 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

An exception if shown on the project settings page if the project has auto release creation enabled

What I expected to happen

The Project settings page is displayed without errors

Steps to reproduce

  1. Go to a project with a Deploy package step in the deployment process
  2. Go to the Triggers tab and enable Auto release creation
  3. Go to the Settings tab
  4. See error

Screen capture


Log exerpt

Affected versions

Octopus Server: 2019.4.3


Disable auto release creation


@hnrkndrssn hnrkndrssn self-assigned this Apr 18, 2019
@hnrkndrssn hnrkndrssn closed this Apr 18, 2019
@octoreleasebot octoreleasebot added this to the 2019.4.4 milestone Apr 18, 2019

This comment has been minimized.

Copy link

commented Apr 18, 2019

Release Note: Fixed exception on Project settings page if auto release creation is enabled and a package step is configured to use a versioning template instead of package step


This comment has been minimized.

Copy link

commented Jul 17, 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 Jul 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.