Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Base the container on offical container
Proposed resolution
Comment | File | Size | Author |
---|---|---|---|
#4 | 2609626-02.patch | 901 bytes | elachlan |
#3 | 2609626-01.patch | 427 bytes | elachlan |
Comments
Comment #2
elachlan CreditAttribution: elachlan commentedComment #3
elachlan CreditAttribution: elachlan commentedComment #4
elachlan CreditAttribution: elachlan commentedComment #5
MixologicComment #6
MixologicComment #7
elachlan CreditAttribution: elachlan commentedMoved to DrupalCI Environments.
Comment #8
MixologicComment #9
tstoecklerJust dropping by to see if there's anything here I could do to help. I just hit a core bug on MariaDB >=10.2.8 and it would be awesome to be able to reproduce this on Drupal.org infrastructure. If not, then don't mind me and just know that the work on this (and DrupalCI in general, as it allows these sorts of things) is greatly appreciated, it really does make core development quite a lot more fun than it used to be. Thanks @all!
Comment #10
MixologicSo, really this is sorta the confluence of two issues.
One is that we're running into UX issues on drupal.org due to the number of PHP versions and DB containers we already support (10 php, 3 db)
So we've got requests for mysql 8, mariadb10, mysql 5.7, postgres 9.4/9.5 etc.
So, if we added five more db containers, suddenly there's 80 different environments to choose from in the matrix of all possible tests. The UX is such that devs arent necessarily sure what to select, so sometimes they select *everything*, which is cost prohibitive for the DA.
Anyhow, so, thats why I've been hesitant to add another db environment. Additionally, Im trying to avoid having to maintain any db containers, so ideally we can use the 'official' containers without needing me to own them at all.
And, at the other side of this is that Im trying to make it so that drupalci no longer uses its own php library that connects to the docker engine via the docker api to start various containers and network them together, and instead rely on docker compose files to establish the environment and let docker 'build' the environment. issue here: https://www.drupal.org/project/drupalci/issues/2949210
That way if a project wanted to define any number of docker compose environments, they could, using public containers etc.
All of that is to say this is probably postponed on https://www.drupal.org/project/drupalci/issues/2949210
Comment #11
tstoecklerThat's totally fair enough and very reasonable. Thanks for the explanation!
Comment #12
MixologicThere is a mariadb 10.2 and 10.3 container, and has been for a while. But still planning on #2949210: Drupalci Roadmap
Comment #13
Mixologic