Skip to content
This repository has been archived by the owner on Jun 15, 2024. It is now read-only.

first-updated-at timestamp not updated for container when retriggering child #56

Closed
flosell opened this issue Sep 20, 2015 · 0 comments
Closed
Labels

Comments

@flosell
Copy link
Owner

flosell commented Sep 20, 2015

Consider this pipeline:

(in-parallel
  some-step
  some-flaky-step)

If we retrigger some-flaky-step, in-parallel is retriggered as well, and it's state changes if some-flaky-steps state changes. But it also contains a retrigger-marker and it keeps the original first-updated-at timestamp as if it didn't run at all. This is inconsistent and leads to bugs in code processing those timestamps, e.g. flosell/lambdacd-cctray#3

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

No branches or pull requests

1 participant