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
{{ message }}
This repository was archived by the owner on Jun 15, 2024. It is now read-only.
Currently, LambdaCD only keeps a history of builds, not of the structure of the pipeline at this build.
If the structure of the pipeline was changed after a build happened, old build will be treated like a build with the new structure, resulting in undefined behavior: Viewing it might show wrong or missing status and output, retriggering might be broken and so on.
Therefore, LambdaCD should keep not only the output of a build but also the structure of the pipeline at that time.
Also, after a change to the pipeline retriggering of old builds should be prevented until we find a way to do so safely.
Currently, LambdaCD only keeps a history of builds, not of the structure of the pipeline at this build.
If the structure of the pipeline was changed after a build happened, old build will be treated like a build with the new structure, resulting in undefined behavior: Viewing it might show wrong or missing status and output, retriggering might be broken and so on.
Therefore, LambdaCD should keep not only the output of a build but also the structure of the pipeline at that time.
Also, after a change to the pipeline retriggering of old builds should be prevented until we find a way to do so safely.
Tasks:
The text was updated successfully, but these errors were encountered: