Add per-package build farm status table #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nbbrooks
force-pushed
the
pr-add-build-farm-status-table
branch
from
782fe5b to
923f3fd
Compare
Member
Author
|
I have not looked into why the Rolling fault controller binary jobs are failing or why all the source CI jobs using upstream source checkouts are failing. @christophfroehlich could you review my explanation of the different CI jobs in https://github.com/PickNikRobotics/picknik_controllers/tree/pr-add-build-farm-status-table?tab=readme-ov-file#source-repository-status ? I believe the CI here was originally generated from some ros2_control boilerplate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding a per-package build farm status to provide some more granular info on debian release health for Ubuntu. I did not add RHEL to the table to keep it more manageable, and also because setting up the table the first time with all the magic URLs is annoying.
Screenshot of new README tables: