templates issueshttps://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues2024-02-15T11:47:56+01:00https://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/63Merge some content from 'health_software/software_good_practices'?2024-02-15T11:47:56+01:00Prada Sarasola, MiguelMerge some content from 'health_software/software_good_practices'?I recently updated a [document](https://health_software.pages.code.tecnalia.com/software_good_practices/ci-cd/readme/) we have in the health group about setting up CI/CD pipelines for our projects, mostly describing how to use the templa...I recently updated a [document](https://health_software.pages.code.tecnalia.com/software_good_practices/ci-cd/readme/) we have in the health group about setting up CI/CD pipelines for our projects, mostly describing how to use the templates here. While writing, I realized quite a lot of the content there could actually go in the README here as well (e.g. configuration of stricter checks, description of the _deploy key_ shenaningans, how to replicate some of the checks locally).
That said, before spending time trying to mix bits from there into the current content of this repository's README, I'd like to collect impressions. Do you think such content will fit README here well? Thoughts/comments are welcome.
All of this was brought back to my mind by [this comment](https://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/merge_requests/93#note_159253), BTW.https://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/58Add yolo pip package support2024-01-19T10:34:23+01:00Rivero Pavlenko, DanilAdd yolo pip package supporthttps://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/55Collision between test jobs due to DDS autodiscovery (ROS2)2023-11-14T16:18:06+01:00Jon AzpiazuCollision between test jobs due to DDS autodiscovery (ROS2)(detected by @danil.rivero )
When two independent ROS2 jobs with tests are running simultaneously in the runner, the DDS autodiscovery mechanism makes the topics/services/params in one docker visible in the other one, producing unexpect...(detected by @danil.rivero )
When two independent ROS2 jobs with tests are running simultaneously in the runner, the DDS autodiscovery mechanism makes the topics/services/params in one docker visible in the other one, producing unexpected failures.
I expected docker network isolation to be enough, but I have validated with a dummy test that starting two docker containers in my PC, topics published by one of the containers are visible to the other one.Jon AzpiazuJon Azpiazuhttps://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/47Echo the command to run industrial_ci locally2021-12-13T14:51:27+01:00Iñigo Moreno i CairetaEcho the command to run industrial_ci locallyA nice feature to have for the industrial_ci template would be to echo the variables it uses so that it is easier to run industrial_ci locally with the same variables used by GitLab.A nice feature to have for the industrial_ci template would be to echo the variables it uses so that it is easier to run industrial_ci locally with the same variables used by GitLab.https://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/46Default docker image name too long2022-10-26T08:47:31+02:00Jon AzpiazuDefault docker image name too longIn the current ddeploy job, the default image name is something like: `tecnalia-robotics-docker.artifact.tecnalia.com/tecnalia_robotics/subgroup_name/project_name` .
Looks too long, at least the first level `tecnalia_robotics` shall be ...In the current ddeploy job, the default image name is something like: `tecnalia-robotics-docker.artifact.tecnalia.com/tecnalia_robotics/subgroup_name/project_name` .
Looks too long, at least the first level `tecnalia_robotics` shall be omitted.https://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/45Double pipeline triggered if merge request has melodic-* branch name.2021-11-23T11:32:07+01:00Iñigo Moreno i CairetaDouble pipeline triggered if merge request has melodic-* branch name.This is because the second rule is triggered for the merge request pipeline.
```yaml
workflow:
rules:
- if: "$CI_COMMIT_REF_NAME =~ /^kinetic-.*/"
variables:
DEFAULT_DISTRO: kinetic
- if: "$CI_COMMIT_REF_NAME =~ /^melodic...This is because the second rule is triggered for the merge request pipeline.
```yaml
workflow:
rules:
- if: "$CI_COMMIT_REF_NAME =~ /^kinetic-.*/"
variables:
DEFAULT_DISTRO: kinetic
- if: "$CI_COMMIT_REF_NAME =~ /^melodic-.*/"
variables:
DEFAULT_DISTRO: melodic
- if: "$CI_COMMIT_REF_NAME =~ /^noetic-.*/"
variables:
DEFAULT_DISTRO: noetic
- if: "$CI_COMMIT_TAG"
- if: "$CI_COMMIT_BRANCH"
```https://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/20Add whole-workspace devcontainer configuration2021-07-06T12:04:28+02:00Jon AzpiazuAdd whole-workspace devcontainer configurationhttps://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/16Add yaml linting to the CI jobs2019-11-25T10:12:46+01:00Jon AzpiazuAdd yaml linting to the CI jobsE.g. using https://github.com/adrienverge/yamllintE.g. using https://github.com/adrienverge/yamllinthttps://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/14Add catkin lint to the CI tests2019-11-19T16:46:46+01:00Jon AzpiazuAdd catkin lint to the CI testshttps://git.code.tecnalia.com/tecnalia_robotics-public/gitlab_templates/-/issues/12Add warning message to ci_run_entry_points.sh2019-11-15T10:51:30+01:00Jon AzpiazuAdd warning message to ci_run_entry_points.shThis script should be used **iff** strictly needed. Add a warning output to the execution.This script should be used **iff** strictly needed. Add a warning output to the execution.