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

Group jobs by project/pipeline #31

Open
cburgmer opened this issue Nov 24, 2016 · 0 comments
Open

Group jobs by project/pipeline #31

cburgmer opened this issue Nov 24, 2016 · 0 comments

Comments

@cburgmer
Copy link
Owner

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:

  1. Provide namespaces when posting job/build information /builds/:ns/:job/:build
  2. Trick D3 into providing similar colors for jobs of the same namespace

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.

cburgmer added a commit that referenced this issue Nov 24, 2016
…Only really worked well for Go setup. Wait for proper implementation via #31
cburgmer added a commit that referenced this issue Nov 24, 2016
This was meant to be used to solve the issue of stable job colors across graphs. Will have to wait for #31 possibly to be properly supported

This reverts commit ae105b0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant