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

Warn if retriggering a pipeline that has changed #139

Open
flosell opened this issue Oct 16, 2016 · 0 comments
Open

Warn if retriggering a pipeline that has changed #139

flosell opened this issue Oct 16, 2016 · 0 comments

Comments

@flosell
Copy link
Owner

flosell commented Oct 16, 2016

Problem

After the pipeline code is changed, retriggering a build that ran with the old code might have unpredictable consequences.

Examples:

  • Slightly changing the behavior of a step but leaving the overall structure and semantics the same: Probably works fine and as intended
  • Completely changing the structure of the pipeline: probably visible in UI and retriggering will probably fail immediately (therefore not causing any damage)
  • Changing the behavior substantially but leave the overall structure the same (e.g. adding a parameter that's passed to a deployment script): Might fail in very subtle ways (e.g. in the given example, the deployment script will still be called but the parameter was missing, possibly deploying a broken version)

Potential Solution

tbd

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

No branches or pull requests

1 participant