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

Human intervention #67

Closed
ronaldvanderrest opened this issue Nov 16, 2016 · 3 comments
Closed

Human intervention #67

ronaldvanderrest opened this issue Nov 16, 2016 · 3 comments

Comments

@ronaldvanderrest
Copy link

Is there any way to include human intervention in alle pipeline, e.g. for approvals before deploying etc?

@drnic
Copy link
Contributor

drnic commented Nov 16, 2016

Only human intervention is to remove triggers from a job, so that only a human or API call can trigger a job, afaik.

@norman-abramovitz
Copy link
Contributor

norman-abramovitz commented Nov 16, 2016

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.
https://github.com/pivotal-cf/email-resource. The are other resources for other types of messaging systems such as SLACK https://github.com/cloudfoundry-community/slack-notification-resource.

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.

@mkb
Copy link
Contributor

mkb commented Dec 8, 2016

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!

@mkb mkb closed this as completed Dec 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants