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

Reployments should include package metadata from last successful deployment #5614

slewis74 opened this issue Jun 7, 2019 · 2 comments


Copy link

commented Jun 7, 2019


  • I have searched open and closed issues to make sure it isn't already requested
  • I have written a descriptive issue title
  • I have linked the original source of this feature request
  • I have tagged the issue appropriately (area/*, kind/enhancement)

The enhancement

In the design of the package metadata features the deployments quite deliberately builds the list of changes from each release between the one that was last deployed to a scope (env/tenant) and the current deployment. So it's building the "delta" of what is changing between when the deployment started and when it completed.

This all holds and makes sense when you are deploying a new version to an environment. However, when you redeploy things aren't what you may think/expect. The current implementation determines that there is no delta, because the version is the same, and therefore no package metadata/work items etc are included.

This enhancement is to include the package metadata from the release(s) from the previously successful deployment. It will be important to take the details from the release, rather than the previous deployment itself, otherwise when we implement #5605 the result of the redeploy would be the old details and not the current details.





This comment has been minimized.

Copy link

commented Jun 11, 2019

Release Note: Redeployments now include package metadata for the releases used the first time the deployment's release was deployed to the given environment/tenant


This comment has been minimized.

Copy link

commented Sep 9, 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 Sep 9, 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.