-
Notifications
You must be signed in to change notification settings - Fork 9
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
Migrate sdformat to GitHub CI #168
Conversation
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.
It looks like the CI jobs are showing up on those example PR's, which is great!
I have two minor comments:
- Is it possible to show the ABI jobs in the build status as well? They didn't show up in bitbucket, but it would be nice to attach them here.
- I like the clickable links in the jenkins job descriptions that were started from bitbucket. I'll create an issue to add that so it doesn't slow down this PR.
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.
The builds seem to be correctly triggered when the PR is open, as well as when requested with @osrf-jenkins run tests
, and I can't spot anything weird in the code.
This was broken by #168 and caused gazebo_ros_pkgs jobs to create builds for every ROS distro.
This was broken by #168 and caused gazebo_ros_pkgs jobs to create builds for every ROS distro.
This PR enable the communication from GitHub to Jenkins for all sdformat scripts.
The approach to be able to merge this and keep the rest of our CI working has been to add new DSL files postfixed with GitHub and use them while porting the different pieces (instead of changing current files). This makes this PR difficult to review for the new DSL base classes (sorry).
For the code outside of DSL the changes to generic-abi-base are conditioned to have a new global GITHUB variable on (off by default, on added in new DSL code).
TODO: the old point of contact for CI (
sdformat-ci-pr_any
) is currently not working. My plan is to use for manual CI triggering and the job will spawn all platforms testing jobs without creating a PR.Testing: