Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »



This solution is needed when some changes were previously abandoned in a release but now need to be allowed to proceed forward as part of a new release. 

Considerations

As you plan to unabandon changes, take the following into consideration:

  1. Are the previously abandoned changeset ready to be promoted without any modifications?
  2. If previously abandoned changeset require modifications then bring a "fix" script.
    1. Can the fix be applied together with the previously abandoned changesets such that original changesets and the fix changeset be applied together all the way to PROD?
    2. Or does the fix script need to be applied to remove previously deploy changes? In this case, you would only need to apply the fix script only into those environments where previously abandoned changes were already deployed. This can be controlled using "contexts". Follow the steps described in How To: Abandon changes in order to fully abandon your changes. This would effectively clean your environments from abandoned changesets. You would then bring a modified version of the abandoned script to package and deploy into the pipeline.

Step-by-step guide

Following steps guide you towards unabandoning your changesets assuming that those changesets do not require any modification. 

 



  • No labels