How do you manage publish-to-prod releases?
Hi ya'll! Looking for some words of wisdom / advice about how to manage publish-to-prod on the Lithium platform. I find it challenging that some configuration-y things (e.g. badge images) are in sta...
Forum Discussion
StanGromer - RIGHT! I remember hearing that a third instance, "dev", was an option way back when, but I had forgotten. This would be very useful for us; I'll look into the cost with my account manager!
StanGromer - That's a nice one. 🙂 Do your developers work with the SDK? If so, how do you handle the different settings you need to make between multiple instances?
CarolineS - For one of our customers we're using Git and a granular branching model to keep track of different development states. We established a few rules how releases and features will be developed and merged into each other.
We're also using an "integration branch" where we merge all release states, so the staging environment is always set up with the current development states of multiple releases.
With these we ensure that all our release branches only contain changes for the particular release. Before a production release we prepare stage with the current production source code and all releases to be published.
Finally we freeze stage until Push2Prod is done.
Best regards,
Christian
