Nightly Workflow not running

Build Environment Running Tests
1

Having an issue with our scheduled job(nightly) workflow. The yaml seems to be correct and matches the example almost completely, but the job never runs. Any suggestions?

version: 2.1

orbs:
  browser-tools: circleci/browser-tools@1.4.6

jobs:
  node_test_job:
    docker:
      - image: cimg/node:20.4.0
    steps:
      - checkout
      - run: echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > ~/.npmrc
      - run: yarn install
      - run: yarn test

  cypress_test_job:
    docker:
      - image: cimg/node:20.4.0-browsers
    steps:
      - browser-tools/install-browser-tools:
          chrome-version: 116.0.5845.96
      - run: echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > ~/.npmrc
      - checkout
      - run: yarn install
      - run: yarn cypress:stage:chrome

workflows:
  commit:
    jobs:
      - node_test_job
  nightly:
    triggers:
      - schedule:
          cron: '0 0 * * *'
          filters:
            branches:
              only:
                - master
    jobs:
      - cypress_test_job
2

First question, does the CircleCI web console show a “No workflow” entry when you modify the config.yml?

This will at least indicate that the integration between CircleCI and the repo is working correctly.

3

If you are correctly getting “CREATED No workflow” messages within the GUI can you try using this far more basic config.yml

version: 2.1

jobs:
  test_job:
    docker:
      - image: cimg/node:20.4.0
    steps:
      - checkout
      - run: echo "hello" 

workflows:
      
  nightly:
    jobs:
      - test_job
    triggers:
      - schedule:
          cron: '* * * * *'
          filters:
            branches:
              only:
                - master

This should cause a cron job to be run every minute so it is easier to see if it is running as the GUI does not provide much info about jobs queued via the cron sub-system. I believe the reason for this is that there has been a long-running project to replace the cron option, but this is currently on hold for refactoring.

4

It successfully shows as “No workflow” after I copy/pasted your suggestion with my current branch (instead of master). However, I do not see any pipelines having ran after 30 minutes. Tried this with a couple branches for what it’s worth.

5

I thought this may have something to do with the number of seats, so I removed a person from the org and retried. No dice.

6

What repo are you using as your backend?

7

This issue is on web, but the backend is called Demeter

8

You miss understand, which repo vendor - github, bitbucket etc.

CircleCI has dedicated code for each platform and so an issue may exist for one, but not another. As my testing was done against bitbucket I can not say what the status of other backends is at the moment.

9

Oh. Github

10

I heard back from support. Since scheduled pipelines are not available for Github, we can’t do scheduled workflows either. Seems like a necessary feature for most folks, so hopefully they add it soon. Thank you for your help, @rit1010!

11

Thanks for posting that as it was not something I was aware of and it may help others in the future. A lot of posted examples are generic and so such a limitation gets missed.

12

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.