Use max PHP composer to run validate jobs if OPT_IN_TEST_CURRENT=0

Created on 2 April 2025, 3 days ago

Problem/Motivation

I'm trying to speed up and decrease the resource usage of pipelines for the commercetools → project, because the test execution is pretty slow.

For this, I enabled only the previous major and max PHP pipeline, and out-out from the current:

variables:
  # Disable testing with the current version in favor of the previous major and max php.
  OPT_IN_TEST_CURRENT: "0"
  OPT_IN_TEST_PREVIOUS_MAJOR: "1"
  OPT_IN_TEST_MAX_PHP: "1"

But in the pipeline I see that we still run the composer for the current version, because it is used for some validate jobs (eslint, cspell, etc).

Proposed resolution

Would be great to add a check if the current is disabled and max_php is enabled, and use the max_php for all validate jobs.

I know that it can overcomplicate the whole logic, but will decrease expenses on Drupal.org infrastructure for such projects :) So creating the issue with minor priority.

✨ Feature request

Status

Active

Component

gitlab-ci

Created by

🇦🇲Armenia murz Yerevan, Armenia

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @murz
Comment 3 days ago →
🇪🇸Spain fjgarlin
Well, the "linting" jobs do depend on the "composer" job. It's not just a dependency for the "testing" jobs so I'd really say that it's working as designed.

If you'd want to change this behaviour in your pipelines, you could do so with an override like this:

composer-lint: needs: -"composer (max PHP version)"
Also, I'd say this is a bit of an edge case, where the "current default" is being disabled in favor of a variant, so I don't think we should overcomplicate things in the templates when it is easy to override the setting as shown above.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024