-
Notifications
You must be signed in to change notification settings - Fork 17
Minor Dockerfile optimizations #288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
2904649
fe50526
6aa54c3
c787703
67ec373
78f2c03
63e254d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -19,8 +19,8 @@ jobs: | |
fail-fast: false | ||
matrix: | ||
env: | ||
- IMAGE: rolling-ci | ||
ROS_DISTRO: rolling | ||
- IMAGE: humble-ci | ||
ROS_DISTRO: humble | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As noted, industrial CI tries to install mavros via CI does work if we force it to use Humble, for which there's a binary image. Note this is just the ros_industrial CI stage, not building the Docker images (where Mavros is built from source for rolling/jazzy. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for looking into that. Because we know it's an issue with MAVROS, It's not a big deal if the CI fails in this PR. We can just update the CI stage in #241 to use the new |
||
steps: | ||
- name: Checkout repository | ||
uses: actions/checkout@v4 | ||
|
Uh oh!
There was an error while loading. Please reload this page.