Skip to content
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

pre-release testing workflow for ros2 #118

Merged
merged 4 commits into from Jun 16, 2021
Merged

pre-release testing workflow for ros2 #118

merged 4 commits into from Jun 16, 2021

Conversation

tylerjw
Copy link
Contributor

@tylerjw tylerjw commented Jun 15, 2021

I pushed this into the repo so we can run it on this branch to test if it works before merging.

It looks like industrial_ci supports pre-release testing for ros2: https://github.com/ros-industrial/industrial_ci/blob/master/industrial_ci/src/tests/ros_prerelease.sh#L25

@tylerjw tylerjw force-pushed the ros2-prerelease branch 3 times, most recently from 4f89c58 to 18eacae Compare June 15, 2021 17:49
@tylerjw
Copy link
Contributor Author

tylerjw commented Jun 15, 2021

There is not pre-release testing for galactic yet, but foxy and rolling seem to work. https://github.com/ros-planning/moveit_msgs/runs/2831886962?check_suite_focus=true

@tylerjw tylerjw force-pushed the ros2-prerelease branch 2 times, most recently from 0d385b3 to ec4c608 Compare June 15, 2021 17:54
@vatanaksoytezer
Copy link
Member

There is not pre-release testing for galactic yet,

Is there anything blocking that? I mean we can add this functionality to industrial_ci I think

@tylerjw
Copy link
Contributor Author

tylerjw commented Jun 15, 2021

I reenabled the workflow dispatch test. Merge the other commit and then that feature will work and you can merge this one and use the pre-release test on either main or ros2 branches.


on:
workflow_dispatch:
push:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just for understanding... Couldn't we remove push here and get rid of the job guard?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so. In a related note, is there any reason not wanting prerelease tests to run with every push or nightly?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the reason is there is no concept of workflows that are allowed to fail with GitHub Actions. We will want to be able to merge changes between releases that will cause the pre-release test to fail.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pushed a change removing the push from this. I'm not sure what the original intent of having it here. I mostly copied this file from the moveit repo.

@tylerjw
Copy link
Contributor Author

tylerjw commented Jun 16, 2021

Now that there is a prerelease test in the default branch (master) I was able to manually trigger running the one in this branch: https://github.com/ros-planning/moveit_msgs/runs/2840796649?check_suite_focus=true

@tylerjw tylerjw merged commit 5bc4ed1 into ros2 Jun 16, 2021
@delete-merged-branch delete-merged-branch bot deleted the ros2-prerelease branch June 16, 2021 16:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants