Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

If two time resources are specified, job will not trigger until both resources are satisfied. #20

Closed
DonBower opened this issue Jul 31, 2017 · 1 comment

Comments

@DonBower
Copy link

DonBower commented Jul 31, 2017

I have a pipeline, to backup Ops Manager, which I want to run twice a day.
But when I first start the pipeline, and it's just after noon in Chicago, the job does not start.
It seems there has to be both resources are triggered.

- name: trigger-daily-after-12am
  type: time
  source:
    start: 00:00
    stop: 03:00
    location: America/Chicago

- name: trigger-daily-after-12pm
  type: time
  source:
    start: 12:00
    stop: 15:00
    location: America/Chicago

And the jobs section has:

  - get: trigger-daily-after-12am
    trigger: true

  - get: trigger-daily-after-12pm
    trigger: true
@jtarchie
Copy link
Contributor

If there are no versions of resource available, concourse will not trigger a build. This is workflow in concourse that resources are an AND operation not a OR operation. You have to have all resources available for a job to build.

I think your issues would be resolved by having the time resource providing an initial zero-time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants