Use dependabot to trigger rebuilds for osrf/ros2:testing #546
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using dependabot, we can automate the rebuilding of local docker images to be in lock step with that of respective parent images. We can do this by pinning the tag of the parent image to include the version identifier provided by the parent repo, and then configuring dependabot to watch the local manifest (or Dockerfile) for available version updates. This will subsequently open auto generate PRs to ratchet up the parent image tag when a newer version is pushed to the public docker registry upstream.
Upon merging changes to local Dockerfiles, existing github actions (#542) will trigger docker rebuilds of local image tags. The added build hook will also timestamp newly built image tags, allowing downstream projects building from our local images to use dependabot to similarly watch for updates to parent image tags.
Example dependabot PR:
While the earlier beta version of dependabot provided a feature for auto merging dependabot PRs, this has been subsequently removed from the native integration offered by GitHub. While this feature can be replicated via third-party actions, it seems that much of this is still in flux due to migration and roadmap changes.
References: