Feature/gitlab ci

[sgermanserrano]

Status

DEVELOPMENT

Description

autowarefoundation/autoware_ai#327 Added gitlab-ci yaml file to run the same tasks as in travis. The jobs are successfully run https://gitlab.com/ServandoGS/Autoware/pipelines

[kfunaoka]

@sgermanserrano Thank you for the great contribution! Everything seems fine under the Gitlab-CI infrastructure. Would you tell me the following questions (your experience)?

• Is it stable compared to Travis in your trials? Does network error or other error appear sometimes in your experience?
• How long does the current tests (build & run_tests) takes? It seems there are one and half hour (1:23:18) and more than two hours (02:15:58). Does the difference between one and half hour and more than two hours seem to come from GitLab server load (or difference of test contents)? I think deep investigation is not necessary :)

[kfunaoka]

The questions above is about your experience after your following modification:

• Within Gitlab CI I've seen that the jobs some time fail with a "Run out of virtual memory" error -> Reducing the amount of parallel jobs when running catkin_make seems to solve the issue
• The previous point results in longer time to build -> The timeout is set to 1h by default, but it is straightforward to change it, I set it to 3h to be on the safe side but 2h should suffice

[sgermanserrano]

@kfunaoka See answers below:

• Is it stable compared to Travis in your trials? Does network error or other error appear sometimes in your experience?

I have not yet experienced errors related to the network. The failed jobs were tied to bugs on the gitlab-ci files.

• How long does the current tests (build & run_tests) takes? It seems there are one and half hour (1:23:18) and more than two hours (02:15:58). Does the difference between one and half hour and more than two hours seem to come from GitLab server load (or difference of test contents)? I think deep investigation is not necessary :)

I'm not sure how the time shown in the pipelines is calculated. If you go inside the pipelines 02:15:58 & 1:23:18, each job has taken less than 1h30min. It might be adding the time till the jobs started.

[esteve]

@kfunaoka

Within Gitlab CI I've seen that the jobs some time fail with a "Run out of virtual memory" error -> Reducing the amount of parallel jobs when running catkin_make seems to solve the issue

This can be solved by running the Gitlab runners on our own infrastructure. Gitlab's hosted runners are rather slow and with not too much memory.

[esteve]

Thanks!

[esteve]

I've withdrawn #1517 (which used Azure DevOps) in favor of this one. It'd be great to have this PR deployed as soon as possible, either on Gitlab's infrastructure or our own.

[maximosipov]

Is Travis CI going to be abandoned in favour of Gitlab CI? Since the current implementation of Travis CI using industrial_ci doesn't seem to support colcon / ament / ROS2 releases and cross builds?

[sgermanserrano]

@maximosipov Gitlab CI is currently being used