Add github actions and solve build error

[Jaeyoung-Lim]

Problem Description This PR adds the a build fix which seems to be caused by a regression coming from a aslam_cv2 update. The fix has been mentioned in https://github.com/ethz-asl/aerial_mapper/issues/43 and is included in this PR

To prevent this from happening a gain, a github actions CI has been added which verifies the build in the following Ubuntu distributions. The Jenkins build pipeline uisng Jenkins seems to be not running anymore.

• Ubuntu 16.04 Xenial ROS Kinetic
• Ubuntu 18.04 Bionic ROS Melodic

Additional Context

• The build takes extremely long, probably we need to start packaging and distributing some of the build dependencies (e.g. pcl_catkin)
• This package fails to resolve dependencies on ROS Noetic and seems like it is coming from other dependencies too: https://github.com/Jaeyoung-Lim/aerial_mapper/pull/1/checks?check_run_id=1553005334
• Fixes https://github.com/ethz-asl/aerial_mapper/issues/43
• Fixes https://github.com/ethz-asl/aerial_mapper/issues/42 with the added rosinstall dependencies

[ethzasl-jenkins]

Can one of the admins verify this patch?

[Jaeyoung-Lim]

@hitimo Any chance you can review this? Thanks in advance

[hitimo]

add to whitelist

[hitimo]

@Jaeyoung-Lim So, I have already Jenkins set up for this repo. Please correct me if I am wrong, but adding github actions would just be redundant, or what is the benefit?

For Jenkins, one would just need to fix the following:

See failures here: https://jenkins.asl.ethz.ch/job/aerial_mapper/3368/lagopus-trusty=ubuntu-xenial-heavy/parsed_console/ grid_map: CMake 3.5.1 or higher is required. You are running version 2.8.12.2

https://jenkins.asl.ethz.ch/job/aerial_mapper/3368/lagopus-trusty=ubuntu-trusty-heavy/parsed_console/ Could not find a package configuration file provided by "protobuf_catkin"

[Jaeyoung-Lim]

@hitimo Thanks for the review. There are two parts of this PR, which is separated by two commits

• A fix for the build error that is preventing the package from building
• A github actions pipeline that verifies the above

If you think that adding a github actions doesn't fit in this repo, I am also fine with removing it from this PR. However, I still think the build issue is a real failure and needs to be fixed.

@Jaeyoung-Lim So, I have already Jenkins set up for this repo. Please correct me if I am wrong, but adding github actions would just be redundant, or what is the benefit?

I do see benefits on using github actions(less maintanance, more transparent and instant feedback), but the decision is yours as you are the main maintainer of the repo. Since Jenkins is also quite powerful I am fine with removing the pipeline from this PR, as long as the Jenkins CI is well maintained.

[hitimo]

Ok, let's try out github actions and see how well it works, we can always go back to Jenkins. I've removed the Jenkins webhook. Thanks @Jaeyoung-Lim

[Jaeyoung-Lim]

@hitimo Thanks!