-
Notifications
You must be signed in to change notification settings - Fork 61
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
Introduce a concept of step-metadata #86
Labels
Projects
Comments
+1 |
13 tasks
flosell
changed the title
Introduce a concept of step-metadata?
Introduce a concept of step-metadata
Feb 5, 2017
This was referenced Mar 28, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment, all information about a build pipeline needs to be extracted from individual build steps:
If we had a separate concept of metadata, this could be used by build steps as well as LambdaCD itself to store such information and access it in a convenient way. It could also simplify the life of everyone trying to aggregate and visualize information about their builds in a custom way (see for example #84).
Some ideas on how it could look like:
Pipeline State:
Sending metadata:
As part of a step-result:
Through the event-bus
In the API and UI
The text was updated successfully, but these errors were encountered: