-
Notifications
You must be signed in to change notification settings - Fork 557
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
Human intervention #67
Comments
Only human intervention is to remove triggers from a job, so that only a human or API call can trigger a job, afaik. |
As part of this human interaction, you can also use the email resource to send a message before going into the job that has triggers turned off. The actual approval workflow seems to be custom work since it is usually industry dependent on what needs to be done for the approval cycle. |
More generally, if a manual trigger is not sufficient for your purposes, you can create a custom resource to request and receive approval from whatever change control tool your org uses. I'm closing this out as we've hopefully answered your question. A better place for general questions about Concourse (as opposed to this tutorial about it) is the Concourse team on Slack or GitHub issues for the Concourse project itself. Good luck! |
Is there any way to include human intervention in alle pipeline, e.g. for approvals before deploying etc?
The text was updated successfully, but these errors were encountered: