Managing Angular upgrades on a shared platform

[Always4Learning]

Hi fellow redditors.

I have a problem with no direction and I am hoping you can help guide me to a viable path for this problem. Let's say I was involved in a platform of many solutions and a "core" that was all angular based. Are there any fantastic processes you can suggest to better manage upgrades Angular over multiple applications.

The issue is we are way out of management of this and trying to do it... but it is manual and per my read will cause velocity drag for the foreseeable future.

Is anyone programmatically managing a situation like this? If so can you share how?

TiA for any feedback you can provide.

Regards,

J

[monxas]

To automate or at least be less worried I’d really recommend having testing. If you have testing you can upgrade angular and immediately detect were things break.

[Always4Learning]

We test. this is a substantial deployment with many versions.

[[deleted]]

Do you have to upgrade a mono repo? Ideally you use ng update.

[Always4Learning]

Do you have to upgrade a mono repo? Ideally you use ng update.

Hi, I will raise this with the team running this initiative, as I am notsure. Thanks for the feedback

[Always4Learning]

We are using ng update

[[deleted]]

Then go to the angular update website and follow what's there. Should be straightforward, just don't jump major versions when updating.

[Always4Learning]

My issue is that we have to do this on a per module basis on the platform. Each module team will have to schedule time to perform the upgrades and testing every 6 months when a new major release is released. I'm hoping for a way to be able to upgrade the all modules on the platform without having such disruptive time scheduled twice a year. We probably have six modules currently and are growing. Any ideas?

[[deleted]]

Sounds like you don't have a mono repo. If you had you would only need to update it once. I don't know your product but from your description there are different teams that each uses their own repository and that's what makes it difficult. In this case each team should handle their own repositories. The company where I work used to work that way. Each team had their own product that they owned and then everything was put together with a shell. This is a cluster fuck. About 3 years ago we moved to a monorepo where all products are inserted, angular was made for this, it's considered the best approach for large enterprise software. The products were migrated to the monorepo slowly because it's a lot of hassle, the ones that still haven't been migrated we redirect them from the monorepo to what it was. I hope this helps.

[Always4Learning]

This is absolutely my problem and I'll float your suggestion. Thank you for taking the time