We have our GitHub branches configured to trigger Circle CI 2.0 workflows, but I noticed that my workflow did not get triggered. We use these workflows not only for CI, but for CD as well, and I have a release scheduled for tonight.
Pls halp
We have our GitHub branches configured to trigger Circle CI 2.0 workflows, but I noticed that my workflow did not get triggered. We use these workflows not only for CI, but for CD as well, and I have a release scheduled for tonight.
Pls halp
Might be worth adding your config.yml
to your post, in a formatted block, in case there’s any issues. Has this worked before?
My scheduled triggers have been fine. Here is my config.yml
:
version: 2
jobs:
build:
working_directory: /app
docker:
- image: docker:17.05.0-ce-git
steps:
- checkout
...
# Scheduled builds
# (Format: Minute hour DOM month DOW)
workflows:
version: 2
commit-workflow:
jobs:
- build
daily-workflow-1:
triggers:
- schedule:
cron: "0 14 * * *"
filters:
branches:
only:
- master
jobs:
- build
daily-workflow-2:
triggers:
- schedule:
cron: "0 22 * * *"
filters:
branches:
only:
- master
jobs:
- build
I’ve just pushed another repo, with a different config (and no schedule triggers), and the push trigger worked in that.
So, apparently, it wasn’t a config issue. Or at least, not one with the circle.yml.
I believe that our SSH key for Circle CI has expired and we just need to re-up.
Going to close this since I was just crying wolf in a panic last night.
wait - how do I close an issue? Or does that have to be an admin who closes the issue?
No real way to close an issue, but you can mark it solved, like I did.