Pipelines are broken currently in HEAD.

Issue fork searchstax-3574016

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

drunken monkey created an issue. See original summary.

drunken monkey opened merge request !73

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented

I just merged a first MR to get pipelines passing again:

  1. Ignored new deprecation warnings that did not relate to our code.
  2. Removed testing against Drupal 12 from the Weekly pipeline schedule, as we currently don’t support Drupal 12 anyways (and there isn’t even an Alpha (or even dev snapshot) release for it yet.
  3. I also had to disable testing against Drupal 8 for now: The reason that build was failing is that actually two of Drupal 8 Core’s dependencies, namely jcalderonzumba/MinkPhantomJSDriver and jcalderonzumba/gastonjs, have been deleted from GitHub (together with their author). I couldn’t find out what’s going on there but seems non-trivial to fix if it doesn’t resolve itself one way or another, so thought it better to provide a stopgap for now.

However, we definitely want to get testing against Drupal 8 working again. I’ll see what I can find out, last ressort would probably be to provide a public fork and get our pipelines to use that.

drunken monkey opened merge request !74

  • drunken monkey committed 97db7cdc on 1.x 
    ci: #3574016 Reactivated testing against Drupal 8.

By: drunken monkey
drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented
Status: Active » Fixed

The packages reappeared just when I had figured out a workaround for the problem, so I now just reenabled testing for Drupal 8.

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.