-
Notifications
You must be signed in to change notification settings - Fork 267
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
Comments
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. |
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. |
@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 |
@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? |
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. |
Add promt for promotion to prod, fixes #37
There doesn't seem to be any "input" commands in the Jenkinsfile. I tried the Spring Boot basic.
The text was updated successfully, but these errors were encountered: