>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3382960. --> Reported by: [hestenet](https://www.drupal.org/user/54034) >>> <p>This meeting:<br> &#10148; Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.<br> &#10148; Usually happens every other Wednesday at 11:00 PT / Thursday 18:00 UTC<br> &#10148; Is done over chat.<br> &#10148; Happens in threads, which you can follow to be notified of new replies even if you don&rsquo;t comment in the thread. You may also join the meeting later and participate asynchronously!<br> &#10148; Lots of threads get posted all at once! Don't worry - start at the top and then jump into the threads that most interest you.<br> &#10148; Has a public agenda anyone can add to in the issue<br> &#10148; *Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.</p> <p>ping: @mixologic @FeyP @jurgenhaas (go to the issue of the next meeting to add or remove yourself from the list)</p> <h2>Transcript</h2> <h2>0&#65039;&#8419; Who is here today? Comment in the thread below to introduce yourself!Maybe share: are you a halloween person? Or not so much?&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Tim from the DA, in Portland, OR USA.DA staff wound up talking about halloween during our social stand -up today - so I'll share my edward scissorhands costume from college (only have a tiny picture)</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Tim as Edward Scissorhands (1).png</td> </tr> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>Wow that's pretty good :smile:</td> </tr> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>Old picture is a fun one.</td> </tr> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>Can't find a fun one ;(Bj&ouml;rn Netherlands, SWIS. The one that would like to do everything, everywhere, all at once.</td> </tr> <tr> <td>tyler36</td> <td>Hi all from Japan.</td> </tr> <tr> <td>quietone</td> <td>Hi. Not really into Halloween, although I do have fond memories of 'moving night'. Where I lived that was the night before Halloween where one did stuff like soap car windows (ivory brand soap) and move garden furniture.</td> </tr> <tr> <td>markdorison</td> <td>Hello! Mark from Chromatic catching up!</td> </tr> </table> <h2>1&#65039;&#8419; Do you have any topics to propose for the meeting today? Feel free to propose them in this thread, and then I will give them their own unique threads for discussion. Conversation moving slow? Go ahead and open your own thread in the next numeric order.</h2> <table> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>I noticed that failure on style failures is only a warning right now without failure. Shouldn't this be configurable?</td> </tr> </table> <h2>2&#65039;&#8419; Status on GitLab Issues and blockers:The next major issue is the SSO solution - so that we can then deploy the issue migration work without having to migrate the rest of d.o We have a meeting next week with our partners at Tag1 to review the current state and see where we are to get this deployed and start the user migration. </h2> <table> <tr> <td>moshe</td> <td>Is there any way to remove this as a blocker? I ask because we seemingly already have so between d.o and Gitlab for mrs and comments.</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Not that I think would be faster to execute with the migration scripts for issues and credit written as they are right now. I am hoping this is close to ready, but will find out next week.</td> </tr> <tr> <td>heddn</td> <td>I'm hopeful we can move fairly quickly on this.</td> </tr> <tr> <td>heddn</td> <td>I'm dusting things off. @hestenet (he/him) can we send a note to cloud-iam asking them to upgrade to KC 21 or 22? whatever is the latest GA version they support now?&nbsp;(edited)</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Good idea... I'll make a note to try and do that after myc urrent call</td> </tr> </table> <h2>3&#65039;&#8419; GitLab CI:GitLab CI for core is looking great thanks to work by @fjgarlin with the help of others in the community - and some of the performance improvements will help everyone.There are three open issues to help us get ready to fully deprecate DrupalCI:SQLite integrationMariaDB integrationDrupal 7 integration</h2> <table> <tr> <td>catch</td> <td>I think once we have sqlite and MariaDB covered, we could try enabling this for on-commit and daily branch tests and as long as it's stable wind down and eventually switch off the DrupalCI equivalents. This would be easy to do because they don't interact with issues that much (except waiting for branch to pass, but if we keep one branch test on-commit that would be covered). We could also try that with MySQL and PostgreSQL now even.What is the situation for setting up pipelines for daily/on-commit?Separately, gitlab CI for MRs seems not far off too, but what's the situation for triggering on-demand tesdt runs for different PHP/database combinations on MRs? And also would we just skip d.o integration for reporting the results until we migrate to gitlab issues?</td> </tr> <tr> <td>fjgarlin</td> <td>I&rsquo;ll try to reply to a few of these things.The current workflows are defined here: <a href="https://git.drupalcode.org/project/gitlab_templates/-/blob/1.0.x/includes/include.drupalci.workflows.yml?ref_type=headsThey">https://git.drupalcode.org/project/gitlab_templates/-/blob/1.0.x/includes/include.drupalci.workflows.yml?ref_type=headsThey</a> can be overwritten as needed. Currently, it&rsquo;ll run on: MR, tag, commit to default and release branches, via the web and web IDE and on schedule. The schedule can be defined here <a href="https://git.drupalcode.org/project/drupal/-/pipeline_schedules">https://git.drupalcode.org/project/drupal/-/pipeline_schedules</a> if needed.This d.o issue will show MR pipeline status in issues: [#3383089]As for the different combinations of php+dbyou can see that we can define that here: <a href="https://git.drupalcode.org/project/gitlab_ci_testbed_for_drupal_core/-/blob/11.x/.gitlab-ci.yml?ref_type=heads#L91-152and">https://git.drupalcode.org/project/gitlab_ci_testbed_for_drupal_core/-/blob/11.x/.gitlab-ci.yml?ref_type=heads#L91-152and</a> it matches what you see here <a href="https://git.drupalcode.org/project/gitlab_ci_testbed_for_drupal_core/-/pipelines/18364If">https://git.drupalcode.org/project/gitlab_ci_testbed_for_drupal_core/-/pipelines/18364If</a> we remove the when = manual from any of the blocks, it&rsquo;ll then run automatically, whereas if when = manual is present, then we need to click on the play button for the pipeline.</td> </tr> <tr> <td>catch</td> <td>So could we start enabling this for what's currently working on <a href="https://git.drupalcode.org/project/drupal">https://git.drupalcode.org/project/drupal</a>, and start disabling the equivalent things on Drupal CI (maybe after a week's overlap) do you think?</td> </tr> <tr> <td>catch</td> <td>One more question, with <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3383089" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3383089</a></span>, what happens to patches?</td> </tr> <tr> <td>fjgarlin</td> <td>I&rsquo;m not sure if anything will need to be done on the infra side of things, as this will probably bring much more load to the runners than what we currently have.but yeah, defo agree that we could have some things running in parallel during some time and we can start turning off the equivalent drupalci once probed that the gitlabci is working as expected.I don&rsquo;t have a lot of knowledge of the intricacies of drupalci, so not sure how easy or difficult is to turn things on and off there.all this is definitely worth bringing to today&rsquo;s DA + core maintainers meeting (happening at 17:00 your time?)</td> </tr> <tr> <td>fjgarlin</td> <td>we can&rsquo;t have gitlabci on patches.so far, that issue has been built as add-on, only with a flag to hide DrupalCI results if desired.I think the disabling of patches will be a separate issue altogether.</td> </tr> <tr> <td>catch</td> <td>We can turn off branch level testing on DrupalCI via the project UI so committers can do that bit.I will try to make the meeting although unlikely to be able to join the zoom.&nbsp;(edited)</td> </tr> </table> <h2>4&#65039;&#8419; Speaking of Deprecating Drupal CI - GitLab CI results summaries are now displayed on project pages, and the 'automated testing' tab warns that DCI is deprecated.<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3379791" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3379791</a></span></h2> <table> </table> <p>Participants:</p> <p>bbrala, moshe weitzman, hestenet, heddn, catch, fjgarlin</p>