dyn365-ce-vsts-tasks icon indicating copy to clipboard operation
dyn365-ce-vsts-tasks copied to clipboard

Published 20 hours ago • verified publisher icon WaelHamze

How to use solution patching and Apply Solution Upgrade in a CI scenario?

Open jellevervloessem opened this issue 5 years ago • 4 comments

I'm investigating the use of patches in our release guidelines and automation. Now our automated setup looks like this: Build

  • Set version number of Solution
  • Extract managed solution
  • Extract unmanaged backup.

Release

  • import managed solution

Question: triggering a build on DEV (manual), I think

  • I should export the Patch that is created on te previous build.
  • I should apply a solution upgrade
  • create a new patch 'v-next'

Triggering the Release should

  • install the patch on TEST, ACC, PROD,
  • Apply solution upgrade

This scenario is for an 'end-of-sprint-Release' that is why I will manually trigger this. Is there a way of setting up Continous Integration using the Patching? -> this was possible in my current scenario.

Am I on the right track?

jellevervloessem avatar Jun 18 '19 11:06 jellevervloessem

@jellevervloessem are you deploying all these patches to production? at what point do you deploy the next version?

WaelHamze avatar Jun 18 '19 18:06 WaelHamze

I haven't figured it all out, but i think that I only deploy entire managed solutions when they are rolled up to an upgraded solution. The patches stay on DEV unless there needs some emergency patching to be done. Not sure, but hiw do you recommend to us these steps?

jellevervloessem avatar Jun 18 '19 18:06 jellevervloessem

@jellevervloessem have you found a suitable solution for your needs? I'm exactly in the same boat right now and would need some input on how to proceed with the patches from DEV to TST

BugsOli avatar Aug 06 '20 16:08 BugsOli

@WaelHamze, @BugsOli

For ContinousIntegration I still use unmanaged solutions. I rather like to use managed solutions with patches. The way I understand it,

  • I should have a patch open during my DEV sprint.
  • At the end of the sprint I deploy the patch to TEST and rollup the patch up.
  • I would then immediately create a new patch v-next to work on during the upcoming sprint. So in this case I deploy patches to the test environment and apply the upgrade on the test environment. Leaving all the patches visible on the DEV.

-> is this the correct way to use the patches and is this possible in devops?

jellevervloessem avatar Aug 20 '20 09:08 jellevervloessem