Hi all, we're looking for the best way to maintain a large deployment between environments.
We have the package created in our DEV environment but we don't want to keep deploying this into SIT every time we fix an issue, as it's a large package and some issues may be in progress and not ready for deployment.
I think ideally we want to create a package we can maintain in SIT as we deploy fixes to keep all the objects we've changed consolidated for when we deploy to UAT. Is there any way to create a package from a direct deployment or do I just need to manually create a new package in SIT and manually add all of the objects?
Thanks!
Discussion posts and replies are publicly visible
johng0005 said:Is there any way to create a package from a direct deployment or do I just need to manually create a new package in SIT and manually add all of the objects?
Does not automatically create a package from a direct deployment(You'll need to manually create/maintain the SIT package)I would recommend, Maintain a dedicated Release Package in DEV that you incrementally update with fixes. Deploy this package to SIT only when changes are validated, then promote the same package to UAT. For urgent fixes, create small delta packages and merge them into the main release package later.