I feel like you are conflating things here a bit. In my experience a WMS is typically used for tasks outside the codebase. Normally you would leverage a CI/CD pipeline (Jenkins or similar) to handle the building, testing, and deployment of a project or repository.
You would then leverage a WMS to create sequential tasks to maybe: trigger an app deployment, send notifications to developers and stakeholders, update a database, send out SMS messages to customers, etc... although many ci/cd services offer these capabilities as well, WMSs are more comprehensive in what they can do.
But if you don't need all of those extra bells and whistles, you might actually add more complexity going to a WMS.
For help with a complex codebase, i like to adhere to a lot of principles in the 12 factor app https://12factor.net/
...Although thats easier said than done to "clean up" a codebase
Comments
I feel like you are conflating things here a bit. In my experience a WMS is typically used for tasks outside the codebase. Normally you would leverage a CI/CD pipeline (Jenkins or similar) to handle the building, testing, and deployment of a project or repository.
You would then leverage a WMS to create sequential tasks to maybe: trigger an app deployment, send notifications to developers and stakeholders, update a database, send out SMS messages to customers, etc... although many ci/cd services offer these capabilities as well, WMSs are more comprehensive in what they can do.
But if you don't need all of those extra bells and whistles, you might actually add more complexity going to a WMS.
For help with a complex codebase, i like to adhere to a lot of principles in the 12 factor app https://12factor.net/
...Although thats easier said than done to "clean up" a codebase