Fixes include folder installation.

[francocipollone]

Part of maliput/maliput_infrastructure#275

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

[tfoote]

LGTM. This won't pass CI until maliput/maliput_drake#23 or maliput/maliput#508 (review) are merged, released, and rebuilt.

[francocipollone]

LGTM. This won't pass CI until maliput/maliput_drake#23 or maliput/maliput#508 (review) are merged, released, and rebuilt.

• maliput: 1.0.4-1 in 'foxy/distribution.yaml' [bloom] ros/rosdistro#33562
• maliput_drake: 0.1.1-1 in 'foxy/distribution.yaml' [bloom] ros/rosdistro#33563

[francocipollone]

maliput and maliput_drake have been built already, It should be ok now to be re-triggered.
I tried to retrigger it but I am not sure if I am a bit rusty with jenkins or if I don't have the bits to retrigger it. :D @tfoote

[tfoote]

You can request a retry from Jenkins by commenting here like this.

@ros-pull-request-builder retest this please

[tfoote]

The build passed, but has linter errors which are why it shows error now.

[francocipollone]

The build passed, but has linter errors which are why it shows error now.

• The GCC and Clang-Tidy warnings are because there are some deprecated attributes in maliput (related to old rules api) and therefore when using those and compiling maliput_malidrive, some warnings are raised.

Is it a requirement to fix all the warnings? What's the best approach when using marked-as-deprecated api?

CC: @agalbachicar

[francocipollone]

Issues were solved via 221 and 222.
Build farm should be happy now.

When merging we should: Rebase and Merge

[francocipollone]

@tfoote Issues are resolved! https://build.ros2.org/job/Fpr__maliput_malidrive__ubuntu_focal_amd64/8/

[tfoote]

I'm glad it wasn't too much to clear the warnings.