You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After more or less 2 years of usage, I came to the conclusion that using generic docker images for CI as the ones provided by robotology/docker_images is applicable only in particular cases. Often it is easier vendoring the CI docker image within the same project repository. The trade-off is that project maintainers have to edit individually all the images in case of an update that requires manual modification.
In the vendoring case, I found that a good solution to build images while minimizing manual effort is exploiting cron-based CI jobs. You can find an example here.
With the current structure, this means adding gazebo10 support in https://github.com/robotology-playground/docker_images/blob/master/robotology-tdd/Dockerfile, or change the system to use some vanilla docker image, and install gazebo & yarp autonomously, as done for example in https://github.com/robotology/gazebo-fmi/blob/master/.ci/install_debian_and_script.sh .
The text was updated successfully, but these errors were encountered: