toolbox/playbooks/setup-env-migration-path-for-coreos-toolbox.yaml

---
- hosts: all
  tasks:
    - include_tasks: dependencies.yaml

    - name: Set up build directory
      command: meson -Dmigration_path_for_coreos_toolbox=true --fatal-meson-warnings builddir
      args:
        chdir: '{{ zuul.project.src_dir }}'

    - include_tasks: build.yaml
.zuul, playbooks: Run unit tests on -Dmigration_path_for_coreos_toolbox The -Dmigration_path_for_coreos_toolbox option enables a different code path that's currently not tested by the CI at all. In fact, since it's a build-time option, the corresponding code path is not even built by the CI. To properly support the -Dmigration_path_for_coreos_toolbox option, it needs to be covered by the CI. This is a step in that direction by running the unit tests on it. https://github.com/containers/toolbox/pull/1095 2022-08-31 11:09:44 +00:00			`---`
			`- hosts: all`
			`tasks:`
			`- include_tasks: dependencies.yaml`

			`- name: Set up build directory`
playbooks: Make all Meson warnings fatal This should help detect the kind of problem that was fixed in the previous commit. https://github.com/containers/toolbox/pull/1096 2022-08-31 17:31:13 +00:00			`command: meson -Dmigration_path_for_coreos_toolbox=true --fatal-meson-warnings builddir`
.zuul, playbooks: Run unit tests on -Dmigration_path_for_coreos_toolbox The -Dmigration_path_for_coreos_toolbox option enables a different code path that's currently not tested by the CI at all. In fact, since it's a build-time option, the corresponding code path is not even built by the CI. To properly support the -Dmigration_path_for_coreos_toolbox option, it needs to be covered by the CI. This is a step in that direction by running the unit tests on it. https://github.com/containers/toolbox/pull/1095 2022-08-31 11:09:44 +00:00			`args:`
			`chdir: '{{ zuul.project.src_dir }}'`

			`- include_tasks: build.yaml`