> Even if the source changes frequently its better to automate. Its not when it keeps changing daily or more then that.
Now I think we can get somewhere! Is this an admission that automation is not worth it when the processes or inputs change too often?
If so, then this frequency (which you have given as daily) depend entirely on the business needs in question.
Often, there's no business case to run an automated process daily.
Weekly or even monthly are very common intervals for processes in business. For a process that needs to run monthly, you only get twelve executions in a year. If the inputs change every six months, do you still think spending 60+ commits (as in your settings example) is worth it every six months, when there are cheaper ways to do it with limited human intervention?
> Often, there's no business case to run an automated process daily.
Almost 100% of the cases I have run daily, hourly and even less (5,10,20,30 minutes schedule are common). I even had one recently that executed millions of requests to some REST API daily, running every few seconds. I call those "app supporting scripts", and I offload specific features of the main app to those.
Must be architectural thing I guess, I work as principal architect and I design most of my services so that they rely heavily on automation support.
> Is this an admission that automation is not worth it when the processes or inputs change too often?
I don't work in a vacuum. For me there are no rules about anything, context is most important (patterns, best practices etc. are for newbies). That case does lean to the manual side on first thought, but it all depends on other factors.
Now I think we can get somewhere! Is this an admission that automation is not worth it when the processes or inputs change too often?
If so, then this frequency (which you have given as daily) depend entirely on the business needs in question.
Often, there's no business case to run an automated process daily.
Weekly or even monthly are very common intervals for processes in business. For a process that needs to run monthly, you only get twelve executions in a year. If the inputs change every six months, do you still think spending 60+ commits (as in your settings example) is worth it every six months, when there are cheaper ways to do it with limited human intervention?