Basic scheduling support


Can basic scheduling support, e.g. build once a day at [time] be added to avoid setting up an external trigger?

Chron task support for running daily scheduled build
Scheduled Builds

I think, (based on my understanding of how builds get pushed) that this could be difficult, but I’m not sure.


If you could run a cron job which checks users scheduled settings, it could just kick off builds using your API.


This would be great I think, thanks for the suggestion!


+1 This would have the added benefit of keeping build configurations & triggers in a single place


Agreed. Being able to run a scheduled build or similar via the Circle UI would rock; else we’re stuck maintaining some other system as a very heavy crontab-runner


+1. This would be a great feature. A simple cron interface and ability to define extra environment variables would be perfect. I really dislike that I have to maintain separate infrastructure to add this functionality.


Be sure to click on the heart to show your “official” support for this request. We use the total likes when deciding what to work on next!


Any love on this? Or at least a URL secured with an API key we could hit to trigger a build so we could use a simple service like to trigger scheduled builds?


Continuing the discussion from How to run cron job on Circle CI?:

The request, as I understand it, is to add the ability to run regularly scheduled builds from CircleCI.

Such builds could be hourly, nightly, weekly, etc.

This could be in addition to, or in place of, builds normally triggered by pull requests.

If you have further details or thoughts, please comment, but be sure to also :heart: this post as that is how CircleCi gauges interest and prioritizes feature requests.


Yes, the scheduled periodical build (aka “nightly builds”) is super important for any non-open source project.

It’s this:


Just to be sure to make you aware, there’s something like this: which requires a cronjob to trigger these nightly builds. We use it effectively for our code coverage report.


I creatd an alternative approach that use aws lambda and the circleci REST API.

This way you do not need to have a server running cron.


For a slightly different use case, I have a project that doesn’t get regular updates, however I would still like to rebuild every once and a while to prevent bitrot and use newer versions of dependencies. I would like to schedule a monthy build so that the running version is never older then that.

For my use case the ideal option would be “Automatically build if last build is older then $n days” but strictly periodic is close enough and simler.


We are planning on add this functionality to our Workflows feature. Please reach out at if you would like to sign up for an early access.


I think this is a great idea. Our current workaround is to use AWS Cloudwatch rules triggering Lambda functions, which in turn trigger the builds via the CircleCI API. So yes, it would be simpler and less moving parts if this were CircleCI functionality.


We have launched a first-class way to run scheduled jobs on CircleCI 2.0.

Below, please find the links to get started: