4 months ago
I've taken a pretty crude approach of spinning up an entirely separate service pointing to my main repo for each of our 15 dozen cronjobs (many of which should just be async celery tasks anyway). but if I insisted on this approach is there a better way than this?
I currently have the cronjobs not connected to each commit for deployment. But if it were connected it triggers 15 builds which really slows things down.
Pinned Solution
4 months ago
Have you tried using watch paths in each of your jobs to only redeploy if that one cron service has changed?
Attachments
3 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
4 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 4 months ago
4 months ago
Have you tried using watch paths in each of your jobs to only redeploy if that one cron service has changed?
Attachments
samgordon
Have you tried using watch paths in each of your jobs to only redeploy if that one cron service has changed?
4 months ago
thanks this seems very useful.
Status changed to Solved samgordon • 4 months ago