Hi there
My previous role only involved sequential deployments. Each version went from Dev, all the way through to Production.
My current role involves multiple development streams.
There is often more than one deployment pipeline
One part of the team might be working on new features for a given rulebase, while others are working on fixes to the Production-level code of the same rulebase. Both teams are currently working out of the same Repository, so while our deployment versioning is solid - I'm not sure if we're tracking the individual changes between versions well enough.
e.g.
- If the Production-fix team needed to add a new attribute "the payment amount", that fix would also need to be retrofitted/merged back into the NewFeatures development stream.
- And if the NewFeatures team added an attribute "the other payment amount", that update should NOT be included in any Production fix releases.
A given update can encompass a lot of different changes (rules/attributes/entities etc). The changes can be seen when uploading to the repository - but it doesn't record exactly what's changed - only WHERE it happened.
So if a staff member needed to merge a given update into a different environment - how would they know what updates to make? (if they weren't the one to make those original updates)
Does anyone have any tips for how to best handle tracking of changes across multiple development streams in OPA 12?