>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3552178. --> Reported by: [fjgarlin](https://www.drupal.org/user/2495842) Related to !425 !418 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Talked about very briefly at DrupalCon Vienna with @phenaproxima. </p> <p>Drupal CMS is a key project now, so we should check if modules are compatible with it by running CI on a Drupal CMS installation.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Allow modules to test whether they would be compatible with Drupal CMS by turning on a switch, like other variants.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Are we testing just one version? <strong>Test latest stable</strong>.</li> <li>Do we need to run any additional tests other than running the normal CI flow of the module with Drupal CMS instead of just core? <strong>Yes, for recipes. See first comment.</strong></li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>We will see a new variant in the pipelines.</p> <h3 id="summary-api-changes">API changes</h3> <p>We will have a new variable <code>OPT_IN_TEST_DRUPAL_CMS</code> to enable the 'Drupal CMS' pipeline job. It will be off by default. See the <a href="https://project.pages.drupalcode.org/gitlab_templates/jobs/drupal-cms/">documentation page for more details</a></p> > Related issue: [Issue #3552331](https://www.drupal.org/node/3552331) > Related issue: [Issue #3546508](https://www.drupal.org/node/3546508)