# More group merging questions

**URL:** <https://forum.buildkite.community/t/more-group-merging-questions/1988>\
**Category:** General\
**Created:** [April 19, 2022, 1:15am UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988 "2022-04-19T01:15:35Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![john.soo](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@john.soo](https://forum.buildkite.community/u/john.soo)\
**Post date:** [April 19, 2022, 1:15am UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/1 "2022-04-19T01:15:35Z")

</div>

We have a pipeline that is entirely dynamically uploaded. So in our `pipeline.yaml` we have this:

```yaml
---
steps:
  - command: "init.sh"

```

`init.sh` uploads the jobs. It uploads enough that we would love to group them together. It uploads more yaml like:

```yaml
---
steps:
  - group: "category 1"
    depends_on: []
    steps:
      - command: "a.sh"
  - group: "category 2"
    depends_on: []
    steps:
      - command: "b.sh"

```

Which are nicely grouped into `category 1` and `category 2` on `/{org}/{pipeline}/builds/{build-number}` but show up ungrouped on `/{org}/{pipeline}/builds`.

Note that there is no way to know in advance which groups will show up, so we cannot “just” put the groups in `pipeline.yaml`.

How do I get my nice groups on `/{org}/{pipeline}/builds`?

---

<div class="post-metadata">

**Author:** ![paula](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/paula/32/954_2.png) [@paula](https://forum.buildkite.community/u/paula)\
**Post date:** [April 19, 2022, 1:21am UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/2 "2022-04-19T01:21:16Z")

</div>

Hi @john.soo thanks for the question!

This functionality is intentional as the builds index page is intended as an overview of the build and for more details you can click a build to view the full set of steps.  
It’s also a little complex to calculate the grouping on the index page since we have to load so many builds and many steps, we limit the number of steps per build for performance reasons. This means we cannot accurately calculate the groups in order to display them on this page as they steps are truncated.

Cheers,  
Jarryd

---

<div class="post-metadata">

**Author:** ![john.soo](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@john.soo](https://forum.buildkite.community/u/john.soo)\
**Post date:** [April 19, 2022, 1:22am UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/3 "2022-04-19T01:22:55Z")

</div>

Interesting. It feels like the grouped version of the UI is a nicer overview than all the ungrouped jobs of a build, though. (It is almost the only reason I want groups at all, honestly).

---

<div class="post-metadata">

**Author:** ![john.soo](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@john.soo](https://forum.buildkite.community/u/john.soo)\
**Post date:** [April 19, 2022, 1:34am UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/4 "2022-04-19T01:34:02Z")

</div>

Is this the point mentioned in the [group step docs](https://buildkite.com/docs/pipelines/group-step)?

> Only the first 100 jobs within a build header can ever be displayed in the UI, so you might not see all of your groups at all times. However, the jobs are fine and will still show up on the build page.

---

<div class="post-metadata">

**Author:** ![paula](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/paula/32/954_2.png) [@paula](https://forum.buildkite.community/u/paula)\
**Post date:** [April 19, 2022, 3:08am UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/5 "2022-04-19T03:08:15Z")

</div>

Yeah thats it exactly! 👍

---

<div class="post-metadata">

**Author:** ![john.soo](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@john.soo](https://forum.buildkite.community/u/john.soo)\
**Post date:** [April 19, 2022, 4:20am UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/6 "2022-04-19T04:20:01Z")

</div>

@jarryd I see! Thank you! Do you think maybe that could be clarified a bit?

> Only the first 100 jobs within a build header can ever be displayed in the UI

Might be better as

> Only the first 100 jobs within a build header can ever be displayed on the builds index page

Second. I think I have a feature request to display the groups on the builds index page. Not all jobs would have to be displayed. Would it be possible to display the denominator as `unknown` or `??`, or similar? Like:

```auto
| category a | | category b |
|------v-----| |------v-----|
| 50/unknown | | 20/unknown |
```

---

<div class="post-metadata">

**Author:** ![john.soo](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@john.soo](https://forum.buildkite.community/u/john.soo)\
**Post date:** [April 19, 2022, 4:25am UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/7 "2022-04-19T04:25:32Z")

</div>

Oh, I also think there may be another bug or inaccuracy. My jobs became ungrouped on the build index page when there were only 66 total jobs in the build.

---

<div class="post-metadata">

**Author:** ![paula](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/paula/32/954_2.png) [@paula](https://forum.buildkite.community/u/paula)\
**Post date:** [April 19, 2022, 7:35am UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/8 "2022-04-19T07:35:40Z")

</div>

Ah yes, we are aware of that bug in the UI. Did this happen whilst a build was running? Ie after it had been updated. There is a bug we have yet to squash related to build updates coming in through the websocket and updating the index page and it manifests in what you have seen.

I don’t have a time estimate for when we will be looking at this bug though.

---

<div class="post-metadata">

**Author:** ![john.soo](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@john.soo](https://forum.buildkite.community/u/john.soo)\
**Post date:** [April 19, 2022, 3:30pm UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/9 "2022-04-19T15:30:51Z")

</div>

Hm, I am not sure, sorry. It is definitely permanently ungrouped on the build index page now, though.

---

<div class="post-metadata">

**Author:** ![paula](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.buildkite.community/paula/32/954_2.png) [@paula](https://forum.buildkite.community/u/paula)\
**Post date:** [April 20, 2022, 7:45pm UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/10 "2022-04-20T19:45:54Z")

</div>

Hey @john.soo!

We received some clarification from the team, and the job truncation limit is actually 50, not 100!  
We’ll update the docs with this info.

Best!

---

<div class="post-metadata">

**Author:** ![john.soo](https://avatars.discourse-cdn.com/v4/letter/j/7ba0ec/32.png) [@john.soo](https://forum.buildkite.community/u/john.soo)\
**Post date:** [April 20, 2022, 9:39pm UTC](https://forum.buildkite.community/t/more-group-merging-questions/1988/11 "2022-04-20T21:39:01Z")

</div>

Woo! Thank you!
