I am having trouble setting up a cron job that will run against a given branch. I am not sure if this is a yaml issue or a circle-ci issue, but in the example below development is run but release/2.0 and release/3.1 are not.
Through trial and error I’ve figured out that the issue is the forward slash in the branch name.
I’ve tried a number of different combinations of regex and string literal, but have had no luck. How can I properly specific the given release/x.y branch for this cron job?
@rohara - Removing the tag filtering has no effect for me. I’ve tried with this updated workflow and the job is still not being picked up (again, branch name is feature/kburns_fix_cypress_cron2)
I see it is working for you and I decided to take a closer look at your config.yml. I noticed that mine is referencing version: 2.1 while yours has version: 2. I thought this this be a bug related to 2.1.
Hi @drazisil This is marked as solved but I believe it may be a legit bug. I have used @rohara’s exact config.yml and am unable to trigger those cron jobs.
Can you open a ticket then https://support.circleci.com/hc/en-us/requests/new and share the number so we can take a look? Without that I can’t think of a reason why those jobs would not be triggering.
@drazisil Ticket has been created but the response has been essentially the same as in this ticket. I have copy and pasted the exact same config.yml used by support and an seeing the same results (no . cron jobs queued)