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

Not prompted to promote from Dev to Stage or Stage to Prod (input missing) #37

Closed
murphye opened this issue Aug 22, 2018 · 5 comments
Closed
Assignees

Comments

@murphye
Copy link

murphye commented Aug 22, 2018

There doesn't seem to be any "input" commands in the Jenkinsfile. I tried the Spring Boot basic.

@syvanen
Copy link
Contributor

syvanen commented Aug 24, 2018

Why would it need that? I personally don't like "input" as CI/CD ideally would run for any commit and shouldn't ideally require any human input from git commit to production deployment.

@pabrahamsson
Copy link
Contributor

I agree with @syvanen here, with proper testing built into your pipeline you probably rather have the promotion and deployments happen without waiting for input.
Feel free to re-open this issue if you like to continue the conversation.

@pcarney8
Copy link
Contributor

@pabrahamsson @syvanen @etsauer In practice removing that input block requires the question, are your tests good enough? and are you disrupting someone else (QA typically) by automatically deploying to Stage?

In this repo, we aren't going to have good, robust tests, nor should we IMO. This repo is for container pipeline examples. I believe omitting a good example of something like an input block is a mistake. We could move it up so it goes from stage to prod. It's easier to delete/comment out the input block than it is to have to search for an example to put it back in. It might be good to add a blue-green with that input block when things go into production (in addition to smoke tests, scaling down and roll back). thoughts?

@etsauer
Copy link
Contributor

etsauer commented Sep 11, 2018

@pcarney8 @murphye if you guys believe that there is more value in having an input than not having it, I'm fine having it in. We used to have inputs in our pipelines and ended up removing them because it made testing changes to the repo so much easier. Would it be a good compromise to include input blocks, but leave them commented out, with instructions in the README to enable them if desired?

cc: @syvanen @pabrahamsson

@pabrahamsson pabrahamsson reopened this Sep 21, 2018
@pabrahamsson
Copy link
Contributor

That's a valid point @pcarney8 so let's add input gates after stage deployment for:

The other pipelines already have input gates and I think the selenium example is one that can do without.

pabrahamsson added a commit to pabrahamsson/container-pipelines that referenced this issue Oct 5, 2018
@pabrahamsson pabrahamsson self-assigned this Oct 5, 2018
etsauer added a commit that referenced this issue Oct 19, 2018
Add promt for promotion to prod, fixes #37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants