You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Provide namespaces when posting job/build information /builds/:ns/:job/:build
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.
The text was updated successfully, but these errors were encountered:
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.
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: