Problem/Motivation

The DA-supported shared Gitlab CI testing templates have support to make it really easy to do automated testing across multiple configurations of core. We should use that to make sure we're ready for movement from core, to confirm we still work with the older versions of things we claim to support, etc.

Steps to reproduce

Proposed resolution

Add the following to our .gitlab-ci.yml file, under variables:

  OPT_IN_TEST_PREVIOUS_MINOR: 1
  OPT_IN_TEST_NEXT_MINOR: 1
  OPT_IN_TEST_PREVIOUS_MAJOR: 1
  OPT_IN_TEST_MAX_PHP: 1

Remaining tasks

User interface changes

API changes

Data model changes

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

dww created an issue. See original summary.

dww’s picture

dcam’s picture

Status: Needs review » Reviewed & tested by the community

I reviewed the available variables at https://git.drupalcode.org/project/gitlab_templates/-/blob/1.0.x/include.... Only one other opt-in variable is not implemented here, OPT_IN_TEST_NEXT_MAJOR. I don't believe it's necessary or wise to turn it on at this stage of the 11.x lifecycle. Therefore, the changes proposed here seem like a good idea to me.

dww’s picture

Yeah, I didn't mention it but I intentionally excluded that one. I don't want to be seeing 11.x test results yet in here. 😂

bluegeek9 made their first commit to this issue’s fork.

bluegeek9 changed the visibility of the branch 3.x to hidden.

bluegeek9’s picture

This issue is not new. Since it was created the .gitlab-ci.yml was updated.

I am leaving this issue open. (I would grant credit to @dww)

dww’s picture

Status: Reviewed & tested by the community » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.