# How to make the build farm use --packages-select/--packages-up-to?

**URL:** <https://discourse.openrobotics.org/t/how-to-make-the-build-farm-use-packages-select-packages-up-to/49453>\
**Category:** Buildfarm\
**Created:** [August 6, 2025, 9:47pm UTC](https://discourse.openrobotics.org/t/how-to-make-the-build-farm-use-packages-select-packages-up-to/49453 "2025-08-06T21:47:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jtbandes](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/jtbandes/32/3930_2.png) [@jtbandes](https://discourse.openrobotics.org/u/jtbandes)\
**Post date:** [August 6, 2025, 9:47pm UTC](https://discourse.openrobotics.org/t/how-to-make-the-build-farm-use-packages-select-packages-up-to/49453/1 "2025-08-06T21:47:59Z")

</div>

The `foxglove_msgs` build is [currently failing](https://build.ros2.org/job/Kdev __foxglove_msgs__ ubuntu_noble_amd64/124/console) due to a build failure in a different package in the workspace. This is because we are in the process of moving `foxglove_bridge` into the same repository, but that is not yet completed, so the build failure is expected.

The surprising part is that having the `foxglove_bridge` code in the repository causes the build farm to fail for `foxglove_msgs`, which doesn’t depend on `foxglove_bridge`. Is there a way we can make the build farm use `--packages-select/--packages-up-to` so it only builds the package that is to be released?

---

<div class="post-metadata">

**Author:** ![christophebedard](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/christophebedard/32/1514_2.png) [@christophebedard](https://discourse.openrobotics.org/u/christophebedard)\
**Post date:** [August 6, 2025, 9:58pm UTC](https://discourse.openrobotics.org/t/how-to-make-the-build-farm-use-packages-select-packages-up-to/49453/2 "2025-08-06T21:58:10Z")

</div>

The Kdev job is for the whole repo, i.e., all of its packages. In this case, the repo is also [named `foxglove_msgs` as far as the buildfarm is concerned](https://github.com/ros/rosdistro/blob/67667522bbe5aa98ba29d4541547f8c3fa6c5c53/kilted/distribution.yaml#L2138). It’s failing because of the `foxglove_bridge` package, not the `foxglove_msgs` package.

I would just ignore the Kdev job until you’ve finished moving `foxglove_bridge`. The Kbin job for `foxglove_msgs` is still 🟩 [Kbin\_uN64\_\_foxglove\_msgs\_\_ubuntu\_noble\_amd64\_\_binary [Jenkins]](https://build.ros2.org/view/Kbin_uN64/job/Kbin_uN64 __foxglove_msgs__ ubuntu_noble_amd64__binary/)

---

<div class="post-metadata">

**Author:** ![jtbandes](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/jtbandes/32/3930_2.png) [@jtbandes](https://discourse.openrobotics.org/u/jtbandes)\
**Post date:** [August 6, 2025, 10:52pm UTC](https://discourse.openrobotics.org/t/how-to-make-the-build-farm-use-packages-select-packages-up-to/49453/3 "2025-08-06T22:52:25Z")

</div>

Thanks. Presumably when we finish the migration, then we should also update distribution.yaml so it combines the two repos into one entry. At that point, will it matter which name we put there? Should we make that change manually or via bloom?

---

<div class="post-metadata">

**Author:** ![christophebedard](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/christophebedard/32/1514_2.png) [@christophebedard](https://discourse.openrobotics.org/u/christophebedard)\
**Post date:** [August 6, 2025, 11:31pm UTC](https://discourse.openrobotics.org/t/how-to-make-the-build-farm-use-packages-select-packages-up-to/49453/4 "2025-08-06T23:31:43Z")

</div>

The name is only really [used with `bloom-release`](https://docs.ros.org/en/rolling/How-To-Guides/Releasing/Subsequent-Releases.html#bloom-release) so that it can find the right repo in the `distribution.yaml` file AFAIK; it doesn’t really matter.

However, to minimize confusion, the name ideally should:

1. Reflect the packages inside the repository
2. Match the name of the release repo (currently: ros\_foxglove\_msgs-release)
3. Match the name of the source repo, but I think that is less important than the above. You could rename it to `foxglove_schemas` to better match the source repo, then request the release repo to be renamed, and then update the `release.url` in `kilted/distribution.yaml`

I don’t think the repository name is included in the release repo’s `tracks.yaml` file, so you can just edit it manually and submit a PR against ros/rosdistro. Then you would have to use the new repo name with `bloom-release`.

If you want to keep it simple, just keep the repo name as-is and eventually delete the `foxglove_bridge` entry in the relevant `distribution.yaml` files through a manual PR.