Share
ReportI run CIJ across 3 environments. DEV, UAT and PROD. Fairly standard practice as far as I am aware.
We are having issues now where our environments are updating themselves automatically without warning and are asynchronous with one another.
2 weeks ago our Prod environment Updated itself to the latest version while the DEV and UAT versions remained behind at the previous version. We had to scramble to update our DEV and UAT environments and test them with our new developments to make sure we wouldn't break PROD before our next release.
This week UAT has updated itself to the latest version and DEV and PROD are behind...
This is a problem..
We have no version control over our product and changes get implemented into PROD without us testing and releasing them.. and they break things..
We have an Issue now in dev where the CSS injected by Microsoft into our forms is different from the CSS being injected into our UAT and PROD forms and is breaking our forms in DEV. So now we have this ticking timebomb waiting to be automatically implemented in UAT and PROD that is going to mess up our forms... And DEV's version is behind UAT... but it's still using a newer CSS template.
None of it makes any sense to me. How can we have standard release cycle when Microsoft is updating things in the background without our knowledge or consent?
I've spoken with support about this and their response is we cannot opt out of the updates and they should closely match across our environments when it comes to timing but in our experience we have seen some pretty large gaps between the updates getting pushed across all 3.
How do you handle release cycles when your environment's version of CIJ and it's underlying framework are randomly becoming out of sync?
I have the same question (0)
All responses (
Answers (
131
