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

Handle combinatorial inputs better #485

Open
rickynils opened this issue Jun 13, 2017 · 0 comments
Open

Handle combinatorial inputs better #485

rickynils opened this issue Jun 13, 2017 · 0 comments

Comments

@rickynils
Copy link
Member

I commonly set up jobsets with the same inputs, tracking different branches. For example a project might depend on nixpkgs and the project's source repository. I'm interested in building for both the master and release-xx.yy branches of nixpkgs, and I probably have at least two branches of the project source. I might have more inputs that I also want to track.

This creates a combinatorial explosion of jobsets for a single project, with names like nixpkgs-master_proj-master, nixpkgs-master_proj-release, nixpkgs-release_proj-release etc.

With declarative Hydra projects, it is pretty convenient to generate these kinds of jobsets, but the UI experience is not nice. It would be lovely to have some kind of matrix view for the jobsets, maybe with support for dynamically selecting which combination of "input branches" you want to display.

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

No branches or pull requests

1 participant