feat(docker,ci): push autoware image on "push to main branch" and "push tag" events

[youtalk]

Description

Under the current GitHub Actions' workflow configuration, the autoware images are only pushed at the following times:

1. On the openadkit-v*.*.* tag pushed
2. On the 1st and 15th of each month
3. On a workflow_dispatch with registory option dispatched

Since 1 and 3 have nerver been executed so far, images have actually only been pushed regularly on the 1st and 15th of each month. However, there is no particular significance to the 1st and 15th of each month.
In order to advance the version control and proceed with container development and operation, it is necessary to always be able to pull the latest container images.

Therefore, this PR revises the image push timings as follows:

1. On the main branch pushed (i.e., on a PR merged)
2. On a tag pushed
3. On a workflow_dispatch dispatched

I would like to propose a revision of the naming conventions for the Docker images and tags in a discussions and a separate PR later.

Tests performed

Not applicable.

Effects on system behavior

Not applicable.

Interface changes

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

[youtalk]

I would like to propose a revision of the naming conventions for the Docker images and tags in a discussions and a separate PR later.

I've submitted a Discussions post about the tag naming convention. https://github.com/orgs/autowarefoundation/discussions/4995

approved wrong pr sorry

[xmfcx]

When do we need new images?

• When ansible script changes
• When the dockerfile changes
• When rosdep dependencies of Autoware change
• When dependent (ROS or not) apt packages are updated
• When the content of autoware.repos or tools.repos? (I dont know if this is part of the docker image) changes

On the 1st and 15th of each month.

This was to loosely handle these updates, with a twice a month schedule.
Unless we detect the changes from autoware packages, or the dockerfile/ansible updates, it might be better to do this on a schedule. Maybe more often, even daily.

ROS 2 has nightly images: https://hub.docker.com/layers/osrf/ros2/nightly/images/sha256-1f29100323ee91dbc90ed248862c408d67ceb9580757bc9c94005de0c2144fef?context=explore

• https://github.com/osrf/docker_images/blob/master/ros2/nightly/nightly/Dockerfile
• https://github.com/osrf/docker_images/blob/master/ros2/source/devel/Dockerfile
• https://github.com/osrf/docker_images/blob/master/ros2/testing/testing/Dockerfile

It seems they generate these dockerfilesi with this create_dockerfiles.py script explained here.

On the main branch pushed (i.e., on a PR merged)

If we don't check for changes made in:

• ansible setup procedure
• dockerfiles
• x.repos
• x.env files,
  this is not good. Any random documentation update or ci push will trigger a new image build, completely detached from any meaningful trigger.

On a tag pushed

I'm ok with keeping this.

workflow_dispatch

This is for testing, why remove it?

[xmfcx]

Directly related issue and PR regarding to the following being removed:

 on:
  push:
    branches:
      - main

• docker-build-and-push should not push an image for every commit to main #4878
  • ci(docker-build-and-push-main): don't push to registry on commit to main #4888

[xmfcx]

https://github.com/marketplace/actions/changed-files

This can be used to detect changes to certain files within this repository.

[youtalk]

@xmfcx

workflow_dispatch

This is for testing, why remove it?

I'm sorry but I just forgot the listing and have fixed the PR description #4993 (comment).

I'm trying to modify the workflow based on your suggestion. Please wait a while.

[youtalk]

I have modified this PR so that the build is only executed when there are changes to the corresponding files using changed-files action.

I've checked that the Build 'Autoware' was skipped in my forked workflow when there was no change https://github.com/youtalk/autoware/actions/runs/9969947469/job/27547864413.

@xmfcx Please review again.

[xmfcx]

@youtalk -san, what do you think about nightly builds?

Rest of the changes look good 👍 Thank you.

[oguzkaganozt]

I think we need to re-enable the artifact saving option as tar files as soon as possible on the workflow_dispatch otherwise LGTM. Thanks !

[youtalk]

@xmfcx nightly is seems to be better than latest but we need to discuss first on https://github.com/orgs/autowarefoundation/discussions/4995.