Adaption of Deployment frequency of CI jobs
While setting up a CI job, I recognized there are only automatization options up to every 24 hours, which is once a day. Currently there is no possibility to deploy e.g. every second day or even more important to us, every week/ every second week. Please add this possibility when adding CI jobs, to have a slower Deployment cycle to e.g. demo sandboxes, that don't need daily deployment.
Melanie Schock
shared this idea
-
Melanie Schock
commented
Thanks for taking this up (unfortunately I didn't get an email on your comment so I just came across now).
It is relevant for the people that work e.g. on POCs, to make sure to not overwrite their changes, we agree on updating the orgs on a less regular basis like e.g. weekly or even better monthly. Also on demo-sandboxes that are used to demo ideas to customers.
Would be a quite common case for us and in each project we would have 3-4 CI jobs that need this possibility of longer deployment cycles. -
To help us understand the situation, what is the disadvantage of running the CI job more often (daily) than required (weekly)?
