>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3569432. --> Reported by: [q0rban](https://www.drupal.org/user/31022) Related to !51 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>I noticed that the current Tugboat config.yml only is using the init and update command groups. Normally on any other d.o project, that might not cause an issue, but since you have a Base Preview, when an MR is opened, this means that no commands will be executed. (When a preview is created from a Base Preview, only the build command group is executed. See <a href="https://docs.tugboatqa.com/building-a-preview/preview-deep-dive/how-previews-work/index.html#why-build-phases-matter">Why Build Phases Matter</a>.)</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>There are two approaches we could take. The first is to change `update` to `build`. This would mean that every MR would wipe out the existing CMS installation and recreate from scratch. This is slower, but will ensure a clean slate. The other option would be to add a `build ` command group that runs the typical steps that an existing site would need to perform when upgrading Byte (composer install, drush deploy, anything else?). This is faster and tests how an MR will interact with an existing site rather than a clean CMS install. </p>