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

Creating a calendar event triggers jobs #6

Open
henrytk opened this issue Nov 13, 2016 · 0 comments
Open

Creating a calendar event triggers jobs #6

henrytk opened this issue Nov 13, 2016 · 0 comments

Comments

@henrytk
Copy link
Owner

henrytk commented Nov 13, 2016

If you have a pipeline which triggers jobs from calendar events and adds calendar events, then the job triggered by an event will trigger every time a calendar event is created, regardless of whether that calendar event is currently happening or not.

Steps to reproduce

  • Create a pipeline based on the README. You will need to edit the times of the events.
  • Create a job in the calendar which is currently happening. You will see that the job triggers as expected.
  • Run the job that creates an event. Make sure it doesn't create an event which is currently happening (set it in the future some time).
  • You will observe the other job, which is designed to trigger at a specific time for a specific calendar event, will trigger.

Cause

This seems to be the way Concourse handles a 'version' of an event. By creating an event you create a new 'version' of that resource, but there is no logic to say whether the created resource version is actually valid for input to a pipeline.

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

1 participant