-
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 the concept of build-metadata #138
Labels
Comments
13 tasks
Basic support implemented. Still todo:
|
flosell
added a commit
that referenced
this issue
Jan 15, 2017
flosell
added a commit
that referenced
this issue
Jan 15, 2017
flosell
added a commit
that referenced
this issue
Feb 5, 2017
flosell
added a commit
that referenced
this issue
Feb 5, 2017
…t once we also add step-metadata #138
Basic support implemented and ready for release. Moved additional features into separate issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
At the moment, all information about a build pipeline needs to be extracted from individual build steps:
Some of this could be better handled on a metadata-level for a build:
to identify which build was retriggered
Context
Related issues
The text was updated successfully, but these errors were encountered: