refactor(webauto-ci): migrate autoware-setup to install_dev_env#7061
Merged
refactor(webauto-ci): migrate autoware-setup to install_dev_env#7061
Conversation
Phase 2 step for #7052. Switches the web.auto setup hook to the tag-driven install_dev_env.yaml so universe.yaml can be removed on 2026-05-24. - Calls autoware.dev_env.install_dev_env (collection-style) instead of the ansible/playbooks/universe.yaml file path. - Drops prompt_install_nvidia / prompt_download_artifacts extra-vars; the new playbook has no vars_prompt, and NVIDIA + artifacts roles run by default (no --skip-tags for them). - Adds dev_tools to --skip-tags to preserve the install_devel=false behaviour; universe.yaml gated dev_tools on a top-level when clause while install_dev_env.yaml expresses the same via role tags. data_dir, ros2_installation_type, install_devel, rosdistro, and WORKSPACE_ROOT are kept as-is since the receiving roles still consume them unchanged. Signed-off-by: Mete Fatih Cırıt <mfc@autoware.org>
No role or task in the ansible collection defines a `vcs` tag (never has, per git history), so the flag was a no-op in the old universe.yaml call and stayed a no-op after the install_dev_env migration. Drop it so the remaining `--skip-tags dev_tools` reflects intent. Signed-off-by: Mete Fatih Cırıt <mfc@autoware.org>
|
Thank you for contributing to the Autoware project! 🚧 If your pull request is in progress, switch it to draft mode. Please ensure:
|
Contributor
Author
|
Initiated with clean build on. 
|
Contributor
Author
|
All green 🟢 
|
mitsudome-r
approved these changes
Apr 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
.webauto-ci/main/autoware-setup/run.shfrom the soon-to-be-removedansible/playbooks/universe.yamlto the tag-drivenautoware.dev_env.install_dev_env.install_devel=falsesemantics by replacing the old top-levelwhen: install_devel == 'y'gate with--skip-tags dev_tools(the new playbook expresses optional roles via tags, notvars_prompt).--skip-tags vcs— no role or task in the ansible collection ever defined avcstag, so the flag was a no-op in the old invocation too.prompt_install_nvidia=yandprompt_download_artifacts=yextra-vars: the new playbook has novars_prompt, and both the NVIDIA and artifacts role sets run by default (no--skip-tagsfor them here).Why
Step 6 of the Phase 1 migration tracked in #7052.
universe.yamlis scheduled for removal on 2026-05-24; this moves the last caller in theautowarerepo so the deletion in Phase 2 is uncontested.Behavioral equivalence
For the exact extra-vars this script passes (
install_devel=false,rosdistro=humble, NVIDIA + artifacts enabled,dev_toolsskipped), role-by-role tracing confirms the two playbooks install the same 13 roles in the same mode.Roles installed
universe.yaml)install_dev_env.yaml+--skip-tags dev_tools)ros2ros2_dev_toolsrmw_implementationrosdistro=humble)rosdistro=humble)gdownbuild_toolsagnocastwhen: rosdistro == 'humble')acadosgeographiclibcudainstall_devel='false'inside role)tensorrtspconvwhen: prompt_install_nvidia == 'y')prompt_install_nvidia=ndev_toolswhen: install_devel == 'y')--skip-tags dev_tools)artifactswhen: prompt_download_artifacts == 'y',data_dir=$HOME/autoware_data)data_dir)qt5ct_setupWhy each old gate maps to the same result under the new mechanism
when: prompt_install_nvidia == 'y'→ CUDA/TensorRT/spconv--skip-tags nvidiaprompt_install_nvidia=yanyway, so both install themwhen: prompt_download_artifacts == 'y'→ artifacts--skip-tags artifactsprompt_download_artifacts=yanywaywhen: install_devel == 'y'→ dev_tools top-level--skip-tags dev_toolsinstall_devel=false, so dev_tools was already skippedwhen: rosdistro == 'humble'→ agnocastrosdistro=humbleanywayVars still consumed unchanged
rosdistro=humblermw_implementation, agnocast (indirectly)install_devel=falsecuda/tensorrttasks (when: install_devel == 'y') → devel packages skippedros2_installation_type=ros-baseros2roledata_dir=$HOME/autoware_dataartifactsroleWORKSPACE_ROOT=$(pwd)universe.yaml)Test plan