OTM Cloud - Developments access segregation, versioning and CI/CD
In the scope of OTM Cloud, regarding the technical developments and configurations, we are motivated to implement in all our systems a strategy aligned with the trending and best practices on solutions development, quality assurance, security and change management procedures.
It's been some time since we have OTM and we've been developing lots of features and configurations in our systems (Development and Production).
Right now, it’s crucial that we align OTM with our IT strategy, so here are some key questions to continue our path:
- In our IT team, how can we segregate the accesses allowing just the developer to develop in each system (Development and Production)?