-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add foxy and rolling to testing #1
base: staging
Are you sure you want to change the base?
Conversation
Signed-off-by: William Woodall <william@osrfoundation.org>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I copied all the files over even if some are not used right now (commented out in the index.yaml
).
# nightly-extra-rmw-release: foxy/ci-nightly-extra-rmw-release.yaml | ||
# nightly-fastrtps: foxy/ci-nightly-fastrtps.yaml | ||
# nightly-fastrtps-dynamic: foxy/ci-nightly-fastrtps-dynamic.yaml | ||
# nightly-performance: foxy/ci-nightly-performance.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kept as much commented out as possible, thinking to keep the load on the test server low, but honestly I don't really know what I'm doing so, if this isn't right let me know.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than enabling all of foxy and rolling, which would back up an unscaled farm pretty quickly, could we use package whitelisting to build only up to rclcpp or something?
Sure, that's fine with me. I don't know how to do that best though. What should we change? |
I think I need these newer versions in order to test the per package documentation jobs I'm working on.