Topic/adapt to gitlab ci

[gergondet]

• Provide a gitlab-ci.yml example file
• Implement an option to disable sudo even on travis builds (CI_REQUIRE_SUDO not tested on travis)
• Do not rely on the scripts being in .travis

[bchretien]

👍

With GitLab CI, apt packages are supposed to be installed in those scripts as well? Now that Travis offers a docker-based build, apt packages can be provided in .travis.yml, removing the need for sudo in most parts of the script.

[gergondet]

For now, apt-dependencies are given in .gitlab-ci.yml in the same way (i.e. by defining the environment variable APT_DEPENDENCIES) and with the same effect, i.e. trigger apt-get install calls in before_script.

However, since (in our use-case) the gitlab-ci builder is root in its docker container, we do not require the use of sudo. I am unsure about the situation with travis and container-based builds but it may be worth a try although this does not seem to be the proper way to add apt-dependencies in that case.

[bchretien]

For travis, we can use this rather than the current APT_DEPENDENCIES + sudo: http://docs.travis-ci.com/user/apt/

However, sources need to be approved (see their whitelist). This may be a problem for ROS (cf. travis-ci/apt-source-safelist#171).

For sudo requirements, if that only concerns APT packages + ccache, we can probably avoid it. We'd need to clean the scripts though, and have different CI-agnostic functions e.g. install_dependencies(), process_coverage(), process_doc().

[bchretien]

Any particular reason for moving this out of verbose_errors.sh?

[gergondet]

No particular reason (except for a bug earlier in the patch cycle). I've restored this part to the previous version.