Grouping of Pipelines

Features Requests
1

Once the number of pipelines increase and the fact there is no ordering, it would be really useful to be able to group pipelines per project or some custom parameter such as a folder (even 1 level deep) - it would help organise the pipelines and make it clearer which are related to one another

2

Hey @mbam :waving_hand:

Thanks for raising this. I can see how a long, flat list gets harder to scan as the number of pipelines grows, and how that makes it tricky to tell which ones belong together.

Before I pass this to our Product team, it’d help to understand what you have in mind:

  • How would you picture the grouping working? What would it let you do that’s awkward today?
  • Where does the current flat list actually slow you or your team down?

Anything you can share in your own words is useful here. The clearer the picture, the better we can represent your case.

For now, the closest option is pipeline tags. You can tag pipelines (say, by project) and filter them from the search bar. It’s flatter than what you’re describing, but it might help in the meantime.

3

I would be happy with a very simple approach here personally…

Creating folders on the https://buildkite.com/{slug} page and being able to drop any pipeline into a folder would be enough grouping for us to organise them. Sorting of the pipelines instead of alphabetical order would also help.

The issue is we use Buildkite for multiple projects and have lots to add. But a single project can have multiple pipelines. Once they are spread out randomly it makes it easier for an engineer who’s just ‘using’ the pipeline to click the wrong one for example. It creates visual noise right now having everything showing in an alphabetical list.

Also I believe the default page when clicking a pipeline should be the /builds page as this is way more useful than seeing builds grouped by branch. There is no link from the /{pipeline} page to the /builds​ page, so you have to go back a page, and click the little hover icon to get there. Just kind of annoying - and have to do this many times a day.

Hope the feedback helps

Matt

4

Thanks for the additional context @mbam! We’ve raised it with our Product folks to take into account while planning future work in the Pipelines UI.