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
Group jobs by project/pipeline #31
Labels
Comments
cburgmer
added a commit
that referenced
this issue
Nov 24, 2016
…Only really worked well for Go setup. Wait for proper implementation via #31
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As teams will likely end up with multiple independent sets of jobs we should probably support some kind of separation of those sets. This could be a complex setup of multiple pipelines or many simple pipelines of microservices.
Color coding is one important visual aspect, as jobs of one group should by identifiable.
The "fail phases" graph follows a pipeline model, aggregating multiple pipelines in one overview will conflate what's happening below.
Ideas:
/builds/:ns/:job/:build
What we don't want:
buildviz does not want to hold information for multiple teams, rather it should be easy to deploy multiple instances of it.
The text was updated successfully, but these errors were encountered: