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

Infrastructure Project Buildfarm
1

The foxglove_msgs build is currently failing 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?

2

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. 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 :green_square: Kbin_uN64__foxglove_msgs__ubuntu_noble_amd64__binary [Jenkins]

1 Like
3

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?

4

The name is only really used with 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.

1 Like