Created on 22 March 2023, almost 2 years ago
Updated 24 October 2023, about 1 year ago

Problem/Motivation

We should run our automated tests and code quality checks on issues and commits.

Proposed resolution

This should run for just out codebase, and not for all of core.

Remaining tasks

* Enable automated testing in the project.
* Add drupalci.yml

πŸ“Œ Task
Status

Closed: won't fix

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States brianperry

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @brianperry
  • @brianperry opened merge request.
  • Issue was unassigned.
  • πŸ‡ΊπŸ‡ΈUnited States brianperry

    Running into an issue where the Drupal test script assumes that this is a module rather than a profile. Wondering if we'll have to run these tests in Gitlab CI instead.

  • Status changed to Closed: won't fix about 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States brianperry

    Learned here that Drupal CI has some limitations when it comes to install profiles. We'll instead cover this via testing in individual module dependences, and also via Pantheon's canary nightly canary jobs for the upstream that uses this profile.

Production build 0.71.5 2024