Skip to content

Comments

Allow customizing MoveIt2 docker image tag#223

Merged
ivanperez-keera merged 2 commits intomainfrom
dev-moveit2-tag
Apr 30, 2025
Merged

Allow customizing MoveIt2 docker image tag#223
ivanperez-keera merged 2 commits intomainfrom
dev-moveit2-tag

Conversation

@ivanperez-keera
Copy link
Contributor

@ivanperez-keera ivanperez-keera commented Apr 10, 2025

Currently, the build script for the MoveIt2 image picks latest as the tag, which prevents us from easily customizing the tag during the build.

This PR adjusts the build script for the MoveIt2 image to pick a tag passed in a variable as MOVEIT2_TAG. If the variable is not set, latest is used instead, defaulting to the current behavior.

The new feature is documented in the associated README.

@ivanperez-keera ivanperez-keera changed the title Allow customizing moveit2 docker image tag Allow customizing MoveIt2 docker image tag Apr 10, 2025
@ivanperez-keera ivanperez-keera requested a review from Bckempa April 10, 2025 01:43
@ivanperez-keera ivanperez-keera force-pushed the dev-moveit2-tag branch 2 times, most recently from e63a682 to d92effa Compare April 10, 2025 01:46
Bckempa
Bckempa previously approved these changes Apr 10, 2025
Copy link
Contributor

@Bckempa Bckempa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is a valid argument that the build.sh scripts represent project defaults and if you want to override them you should know enough about Docker to run the build command yourself, but I can see the value in this for advanced CI workflows.

@Bckempa Bckempa linked an issue Apr 10, 2025 that may be closed by this pull request
@Bckempa Bckempa added this to the jazzy-2025.04.0 milestone Apr 10, 2025
@ivanperez-keera ivanperez-keera requested a review from Bckempa April 10, 2025 05:15
@ivanperez-keera
Copy link
Contributor Author

@Bckempa I've requested the re-review to meet the requirements to merge without bypassing. I applied your suggestion and responded to the other comment.

@ivanperez-keera
Copy link
Contributor Author

@Bckempa the build is in a strange state, with several CI jobs crashing atm. Do we want to bypass those or wait until those are fixed (if the fix is simple/quick)?

@Bckempa
Copy link
Contributor

Bckempa commented Apr 12, 2025

@Bckempa the build is in a strange state, with several CI jobs crashing atm. Do we want to bypass those or wait until those are fixed (if the fix is simple/quick)?

For the sake of the record, we discussed that since this wasn't blocking anything we'd prioritize getting CI back to green first.

Currently, the build script for the moveit2 image picks latest as the tag,
which prevents us from easily customizing the tag during the build.

This commit adjusts the build script for the moveit2 image to pick a tag passed
in a variable as MOVEIT2_TAG. If the variable is not set, the latest is used
instead, defaulting to the current behavior.
A prior commit adjusted the build script for the moveit2 docker image to allow
setting the image tag using a variable MOVEIT2_TAG.

This commit adjusts the README to document the new functionality.
@ivanperez-keera ivanperez-keera merged commit d4f0b93 into main Apr 30, 2025
4 checks passed
@github-project-automation github-project-automation bot moved this from In Review to Done in Space ROS Project Development Apr 30, 2025
@ivanperez-keera ivanperez-keera deleted the dev-moveit2-tag branch April 30, 2025 05:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Allow customizing moveit2 tag

2 participants