CI jobs on ROS2 build farm are not triggered for Iron and Rolling

[JanStaschulat]

TODO:

• [x] merge all pending pull requests,
• [x] have a clean status on master, rolling and iron.
• [x] update changelog, create a new revision number (package.xml), and add a new tag
• [x] create a new bloom release and change the branch names to iron and rolling, respectivly.

---

@pablogs9 @Acuadros95 the ci pipeline on OSRF build farm is not triggered for Rolling and Iron for all of the pending pull requests. Do you have any idea what else to check?

pending pull requests:

• https://github.com/ros2/rclc/pull/363
• https://github.com/ros2/rclc/pull/362
• https://github.com/ros2/rclc/pull/359
• https://github.com/ros2/rclc/pull/358
• https://github.com/ros2/rclc/pull/357

I have also seen that you have updated the line in one of the micro-ros/setup repos: https://github.com/ros2/rclc/blob/master/.github/workflows/ci.yml#L26

• uses: actions/checkout@v2 to
• uses: actions/checkout@v3

Might this be the reason? Where is this documented? Could you provide a link to the documentation for the changes of v2 and v3?

[Acuadros95]

Might this be the reason? Where is this documented? Could you provide a link to the documentation for the changes of v2 and v3?

v3 updates to Node16, which will be the version used on github actions. Sources:

• GitHub Actions: All Actions will run on Node16 instead of Node12
• Why and how to adopt actions/checkout@v3 in your GitHub Action workflow

I really hope this is not the reason for the not triggered CIs

[Acuadros95]

I would say its related to the branch used, maybe something needs to be configured on the build farm side?

[JanStaschulat]

I updated the action/checkout version for some PR. This did not resolve the issue.

[JanStaschulat]

I would say its related to the branch used, maybe something needs to be configured on the build farm side?

That's a good point.

[JanStaschulat]

Indeed, the Iron- and Rolling- build jobs on the ROS build farm are using the master branch on rosdistro:

• iron distribution configuration file
• rolling distribution configuration file

I need make a new bloom release for the iron and rolling distribution with changed branch names.

[JanStaschulat]

status:

• the Github Action CI-jobs on master, rolling and iron were triggered by all pending pull requests (only one has not run yet) and were successful.
• the ROS build-farm CI-job on Iron was triggered by the corresponding pull requests on the master branch and was successful.
• the ROS build-farm CI-job on Rolling was triggered by the corresponding pull requests on the master branch and was successful.

I would do the following:

• I would now merge all pending pull requests,
• then I have a clean status on master, rolling and iron.
• then I update changelog, create a new revision number (package.xml), and add a new tag
• then create a new bloom release and change the branch names to iron and rolling, respectivly.

@Acuadros95 , @pablogs9 Do you agree?

[JanStaschulat]

Created a bloom release for Iron, however the iron branch was not updated with the bloom-release tool. I need to create another pull reqest again that changes the branch name.

PR for iron: https://github.com/ros/rosdistro/pull/37664

PR for rolling: https://github.com/ros/rosdistro/pull/37675

[JanStaschulat]

Created two pull requests to change the source branch name for ...:

• Rolling: https://github.com/ros/rosdistro/pull/37677
• Iron: https://github.com/ros/rosdistro/pull/37676

[JanStaschulat]

@pablogs9 @Acuadros95 The bloom release is finished for Rolling and Iron including updated branch names. Closing this issue.