Problem/Motivation

Now that 10.1.x is security-only, it will only get commits for security releases, or in rare cases a dependency update or critical upgrade path bug fix. Given that, we don't need to run tests on it every 24 hours, and should move all jobs to on-commit. Once all jobs are on-commit, we can remove the schedule entirely.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3409961

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:

About issue forks

Comments

catch created an issue. See original summary.

catch opened merge request !5894

catch’s picture

catch
he/him
Primary language English
commented
Status: Active » Needs review
fjgarlin’s picture

fjgarlin commented
Status: Needs review » Reviewed & tested by the community

Changes look good to me and it's only for 10.1.x.
RTBC.

  • longwave committed d36e28b8 on 10.1.x 
    Issue #3409961 by catch, fjgarlin: Set all 10.1.x jobs to on commit and...
longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Status: Reviewed & tested by the community » Fixed

Committed d36e28b and pushed to 10.1.x. Thanks!

Also removed the pipeline schedule for 10.1.x.

Status: Fixed » Closed (fixed)

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

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Title: Set all 10.1.x jobs to on commit and remove the 10.1.x schedule » Set all 10.1.x jobs to run on commit and remove the 10.1.x schedule

Fix the issue title: add the missing word.