You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: