Drupal.org now supports automated issue previews via Tugboat (see #3161760: Provide automated testing environments for Drupal Core issues (using Tugboat).

These previews currently use the standard installation profile and have no sample data. This makes it difficult for reviewers to check their work. A common scenario is that they have to

  1. Enable the module
  2. Create some menu items
  3. Create one or more pieces of content (including media).
  4. etc etc

This can get very tedious very fast -- especially if the preview rebuilds on every commit.

I had a discussion with @lauriii earlier today, and he suggested using the Umami profile as the default profile for Tugboat previews.

This would have the benefit of default content including menu items, taxonomies, media entities, multiple different types of fields (including entity references), and multiple modules enabled (maybe even layout builder ... not sure).

Personally as a maintainer of Olivero this would even help me because of the default content. I would only have to switch themes instead of manually creating content.

Comments

mherchel created an issue.

juampynr’s picture

This is for core, right? If so, Tugboat config files for core are at https://github.com/TugboatQA/drupalorg/tree/master/drupal.

You will see there branches and then a default folder. The branch folders are for core branches that required an extra step to build the site. All the other branches for 8 and 9 use the config from the default folder.

If we finally move forward, this would be the file to tweak https://github.com/TugboatQA/drupalorg/blob/master/drupal/default/config...

drumm’s picture

Now that the Tugboat integration with Drupal.org is stable, it might be a good time to see if https://github.com/TugboatQA/drupalorg/blob/master/drupal/default/config... would be a good to have in core itself. Using the external configuration for core is now a bit of an edge case, that would be nice to remove.

q0rban’s picture

Now that the Tugboat integration with Drupal.org is stable, it might be a good time to see if https://github.com/TugboatQA/drupalorg/blob/master/drupal/default/config... would be a good to have in core itself.

This would simplify a lot! We wouldn't need to maintain separate config and push it in via the API, which means we could also begin to rely more on GitLab's webhooks to trigger things automatically without needing automation in drupalog code. What would next steps be to work towards this?

juampynr’s picture

juampynr’s picture

@drumm, #3280730: Add Tugboat configuration to core is ready for review. I verified that Tugboat picks up the config from the merge request and not the GitHub repository.