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

Add support for multiple errands (automatic and manual ones) #14

Closed
JCL38-ORANGE opened this issue Sep 13, 2017 · 1 comment · Fixed by #286
Closed

Add support for multiple errands (automatic and manual ones) #14

JCL38-ORANGE opened this issue Sep 13, 2017 · 1 comment · Fixed by #286
Assignees

Comments

@JCL38-ORANGE
Copy link

Today errand jobs (if there are some for a deployment) are grouped all together in a unique Concourse box.
The request is to have one box by errand job in order to trigger each one separately.
Moreover, we would like to categorize errands job :
*A manual category means "errand triggered by human (click)"
*An automatic category means "errand triggered by concourse"

@o-orand
Copy link
Member

o-orand commented Feb 15, 2019

Todo: design errand lifecycle (see PCF as inspiration)

o-orand added a commit that referenced this issue Oct 25, 2019
We also use metadata-resource to replace secrets and paas-template resources,
so we are able to trigger errands even on git reset.

close #14, close #285, related to #197
o-orand added a commit that referenced this issue Oct 25, 2019
We also use metadata-resource to replace secrets and paas-template resources,
so we are able to trigger errands even on git reset.

close #14, close #285, related to #197
o-orand added a commit that referenced this issue Nov 4, 2019
We also use metadata-resource to replace secrets and paas-template resources,
so we are able to trigger errands even on git reset.

close #14, close #285, related to #197
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
2 participants