Uses ros-action-ci in build.yaml workflow.

[francocipollone]

Part of maliput/maliput_infrastructure#268 (comment)
Part of maliput/maliput_infrastructure#274

Rely on ros-action-ci for the build.yaml workflow

action-ros-ci-repos-override: https://gist.githubusercontent.com/francocipollone/18dfba70fefe81314bc8a68138732f53/raw/6ca6e0def9d90e93d84d7ce20ad99c437bdd0e7a/prs.repos

Signed-off-by: Franco Cipollone [email protected]

[francocipollone]

I've been trying this feature of the ros-action-ci but it doesn't seem to be working: https://github.com/ros-tooling/action-ros-ci#interdependent-pull-requests-or-merge-requests

[agalbachicar]

I've been trying this feature of the ros-action-ci but it doesn't seem to be working: https://github.com/ros-tooling/action-ros-ci#interdependent-pull-requests-or-merge-requests

I've seen it in a code block. Have you tried it?

[francocipollone]

I've been trying this feature of the ros-action-ci but it doesn't seem to be working: https://github.com/ros-tooling/action-ros-ci#interdependent-pull-requests-or-merge-requests

I've seen it in a code block. Have you tried it?

Let's see

[francocipollone]

@agalbachicar Nope, I will continue checking

[agalbachicar]

Please add me as reviewer when you've found a solution. Otherwise, I can allocate some time to investigate further.

[francocipollone]

It is working now! @agalbachicar

Some things to have mind with this tool

• When using action-ros-ci-repos-override, the entire repos file is being overridden, meaning that all the repos should be added to the repos file.
• It only works for Github Action triggered via pull_request.
• If PR's description has changed, then retriggering the workflow from Action tab doesn't seem to work (The PR's description is not updated for the action). You have to push again to the branch. (It could be an undesired behavior to report)

For the record:

I've found some PRs(See here) where this was being used (By the very feature's creator) and from there I got the confirmation on the expected PR's description syntaxis.

[agalbachicar]

I suggest we add a TODO in maliput_documentation and explain how to use it in the developer guidelines.

[agalbachicar]

LGTM

[francocipollone]

I suggest we add a TODO in maliput_documentation and explain how to use it in the developer guidelines.

Done! maliput/maliput_documentation#91

Going in