You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently store build information (commits and changesets) for every package. If a build produces many packages we duplicate the same build information for every package in that build. When creating releases that use those packages a large amount of duplication occurs, exploding the size of the data. This is exacerbated when there are many releases between deployments and/or there are many Tenants.
Instead we should store the build information against the build and link the packages to that.
This is a significant change and will require reworking our integrations and documentation.
The text was updated successfully, but these errors were encountered:
ReleaseNote: Fixed Build Information duplication in a deployment caused by multiple releases containing the same package but not the other duplication scenarios.
We currently store build information (commits and changesets) for every package. If a build produces many packages we duplicate the same build information for every package in that build. When creating releases that use those packages a large amount of duplication occurs, exploding the size of the data. This is exacerbated when there are many releases between deployments and/or there are many Tenants.
Instead we should store the build information against the build and link the packages to that.
This is a significant change and will require reworking our integrations and documentation.
The text was updated successfully, but these errors were encountered: