search

super-owesome / bobble_controllers

ROS controllers for self balancing robot, Bobble-Bot.
BSD 3-Clause "New" or "Revised" License
62 stars 15 forks source link

Setup GitHub Continuous Integration #11

Open mike-moore opened 3 years ago

mike-moore commented 3 years ago

Would like to get CI going in our GitHub repository. This should be a good reference https://github.com/ros-industrial/industrial_ci

dwes7 commented 3 years ago

I started looking into this today. I assumed you'd want to use Github actions since they're free and the industrial_ci has some scripts to help set it up. So I forked the bobble_controllers repo and tried putting in the script from the industrial_ci quickstart guide for github actions and pushing it to my forked repo. The action steps seemed to work correctly, but I got the following result from the action. See the log file attached or see build result here. logs_2.zip

It looks everything was good until the tests were ran. I haven't tried running the tests locally to see if they pass, or if its has something to do with the way the environment is setup in the github action.

dwes7 commented 3 years ago

I also noticed that there's a .gitlab-ci.yml, already in place. Is there already some CI for gitlab? Should I be building off of this script instead of focusing on github Actions? Or do we want to migrate over to github Actions instead? I guess Github actions didn't get released until Nov 2019, you pushed the .gitlab-ci.yml in April 2019 aedf995642ae6a439283002b002dd129dddd6a4b, so maybe sticking with the github ecosystem seems to make more sense?

mike-moore commented 3 years ago

@dwes7 yeah the idea would be to build off what's called out in .gitlab-ci. We would want to replicate that behavior using what GitHub provides.