[GH-ISSUE #97] Configure cron job on Circle CI #82

New issue

Closed

opened 2026-05-05 11:26:21 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 11:26:21 -06:00

Owner

Originally created by @enocom on GitHub (Feb 4, 2019).
Original GitHub issue: https://github.com/enocom/gopher-reading-list/issues/97

One of the things we lost when transferring to Circle CI was running a build every 24 hours.

@mvxt If you have the time to do this, I would be grateful. Otherwise, I'm happy to handle it. You've done all the hard work.

Originally created by @enocom on GitHub (Feb 4, 2019). Original GitHub issue: https://github.com/enocom/gopher-reading-list/issues/97 One of the things we lost when transferring to Circle CI was running a build every 24 hours. @mvxt If you have the time to do this, I would be grateful. Otherwise, I'm happy to handle it. You've done all the hard work.

gitea-mirror closed this issue

2026-05-05 11:26:24 -06:00

gitea-mirror commented

2026-05-05 11:26:26 -06:00

Author

Owner

@mvxt commented on GitHub (Feb 4, 2019):

@enocom Here's one of the snippets I've used to configure nightly builds.

In short you'll want to specify workflows. So I'd add the following snippets to your config.yml file:

workflows:
  version: 2
  build-pipeline:
    jobs:
      - build

  nightly:
    jobs:
      - build
    triggers:
      - schedule:
          cron: "0 6 * * *"
          filters:
            branches:
              only:
                - master

workflows is a top-level item with version specification followed by various other parameters. In the above snippet we've defined two workflows: the first is the normal workflow which is always triggered on push to repo.

The second one is the one that is triggered to run once a day via CRON. I also added an additional filter so that we only run nightly builds on the master branch, and no other branches. You can omit that if you'd like.

Hope this makes sense and helps.

The "build-pipeline" and "nightly" workflow labels are just names you can arbitrarily change. What's important is that the "jobs" section underneath lists the exact job names for jobs you've defined above.

Actually, I think that since your main job is just called "build" you might not even need to specify the 1st workflow because by default CircleCI implicitly looks for a build job. If you decide to rename the "build" job to something else though then you'll need to specify a workflow for it so CircleCI knows what job it should look for.

@mvxt commented on GitHub (Feb 4, 2019): @enocom Here's one of the snippets I've used to configure nightly builds. In short you'll want to specify workflows. So I'd add the following snippets to your config.yml file: ``` workflows: version: 2 build-pipeline: jobs: - build nightly: jobs: - build triggers: - schedule: cron: "0 6 * * *" filters: branches: only: - master ``` `workflows` is a top-level item with version specification followed by various other parameters. In the above snippet we've defined two workflows: the first is the normal workflow which is always triggered on push to repo. The second one is the one that is triggered to run once a day via CRON. I also added an additional filter so that we only run nightly builds on the master branch, and no other branches. You can omit that if you'd like. Hope this makes sense and helps. The "build-pipeline" and "nightly" workflow labels are just names you can arbitrarily change. What's important is that the "jobs" section underneath lists the exact job names for jobs you've defined above. Actually, I think that since your main job is just called "build" you might not even need to specify the 1st workflow because by default CircleCI implicitly looks for a `build` job. If you decide to rename the "build" job to something else though then you'll need to specify a workflow for it so CircleCI knows what job it **should** look for.

gitea-mirror referenced this issue

2026-05-05 11:33:54 -06:00

[PR #82] [CLOSED] Added resources for Dependency Management #251

gitea-mirror referenced this issue

2026-05-05 11:34:02 -06:00

[PR #84] [MERGED] Added Resources for Go Modules #253