>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3385691. --> 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!</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Tim from the DA :wave::skin-tone-3:</td> </tr> <tr> <td>markdorison</td> <td>Mark from Chromatic! :meow-wave-peek:</td> </tr> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>Bjorn from SWIS, Netherlands. :stuck_out_tongue_winking_eye:</td> </tr> <tr> <td>andypost</td> <td>Andy from Hanau</td> </tr> <tr> <td>kimb0</td> <td>Kim from Sydney</td> </tr> <tr> <td>tyler36</td> <td>Hi from Japan</td> </tr> <tr> <td>Nick_vh</td> <td>Hi Nick from GitLab, Belgium &#128578; Mostly observing and trying to build bridges where needed</td> </tr> <tr> <td>wimleers (he/him)</td> <td>:wave:</td> </tr> <tr> <td>hestenet (he/him)</td> <td>:clock11: Okay - getting this started!This meeting:&#10148; Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.&#10148; Usually happens every other Wednesday at 11:00 PT / Thursday 18:00 UTC&#10148; Is done over chat.&#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!&#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.&#10148; Has a public agenda anyone can add to in the issue&#10148; *Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a &#128100; emoji. To take a comment or thread off the record, start with a &#128683; emoji.</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> </table> <h2>2&#65039;&#8419; GitLab CIAlso some DrupalCI_Environments issues (still used by Gitlab CI) in this top level thread&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>andypost</td> <td>Explored option and shaved few seconds when database docker images has pre-initialized database but as tests are running on the same node and using tmpfs, so runner's helper image an setup some "drupal magic" for caching code/node_modules/database</td> </tr> <tr> <td>hestenet (he/him)</td> <td>And I owe you some reviews in the drupalci_environment queue I think.</td> </tr> <tr> <td>hestenet (he/him)</td> <td>I think I have time tomorrow.</td> </tr> <tr> <td>andypost</td> <td>yes, I need another pair of eyes on review and splitting PHP image into maintainable sets of php-cli/nodejs/chrome/apache/nightwatch <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-3"><a href="https://www.drupal.org/project/drupal/issues/3386474" title="Status: Closed (duplicate)">#3386474: [omnibus] Speed up gitlab ci runs</a></span>#comment-15236589&nbsp;(edited)</td> </tr> <tr> <td>andypost</td> <td>also some prometheus/grafana instance could be very helpful <a href="https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#integrate-with-gitlab-ui">https://docs.gitlab.com/ee/administration/monitoring/performance/grafana_configuration.html#integrate-with-gitlab-ui</a></td> </tr> <tr> <td>andypost</td> <td><a href="https://docs.gitlab.com/runner/configuration/advanced-configuration.html#override-the-helper-image">https://docs.gitlab.com/runner/configuration/advanced-configuration.html#override-the-helper-image</a> speed-up/secure/predictable</td> </tr> <tr> <td>hestenet (he/him)</td> <td><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupalci_environments/issues/3388135" title="Status: Closed (fixed)">#3388135: Fix base image for Mysql 8.0/5.7</a></span>#comment-15240193Two cherry picks for MySQL 5.7 and 8 to production - images are built - comment has two test runs to validate that it is all working.</td> </tr> </table> <h2>2&#65039;&#8419; 1&#65039;&#8419; CI for Modern CoreTruly incredible progress in the last couple weeks especially. We are looking at the possibility of sub-10-minute core runs.Meta issue:<span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/3388162" title="Status: Active">#3388162: Investigate realistic resource requests for core jobs</a></span>(edited)</h2> <table> <tr> <td>larowlan</td> <td>Yay :tada: pats on the back to everyone involved</td> </tr> <tr> <td>andypost</td> <td>hey! at core side it makes sense to improve protocol <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/3240792" title="Status: Closed (fixed)">#3240792: Use lullabot/mink-selenium2-driver and lullabot/php-webdriver for functional browser testing</a></span></td> </tr> <tr> <td>andypost</td> <td>Also using PHP 8.0+ with JIT and preloading can give another 20-30% speed-up <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/3108687" title="Status: Active">#3108687: Compatibility with/take advantage of code preloading in PHP 7.4</a></span></td> </tr> <tr> <td>andypost</td> <td>feeling lack of metrics (only manual measures) but looking for review/ideas about further docker image optimizations in layering per test job in context of <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-8"><a href="https://www.drupal.org/project/drupalci_environments/issues/3387737" title="Status: Needs review">#3387737: Split PHP image into php(cli/apache) and yarn(node/nightwatch)</a></span>#comment-15238693&nbsp;(edited)</td> </tr> <tr> <td>Juraj Nemec</td> <td>@hestenet (he/him) maybe we can link the meta issue here as well, where all these issue are linked: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/drupal/issues/3387107" title="Status: Active">#3387107: [meta] GitLab CI feature parity with DrupalCI</a></span></td> </tr> <tr> <td>hestenet (he/him)</td> <td>@Juraj Nemec good idea - done.</td> </tr> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>Joined the fun for once lol :stuck_out_tongue_winking_eye:</td> </tr> <tr> <td>wimleers (he/him)</td> <td>Thanks for these links, following all of them!</td> </tr> </table> <h2>2&#65039;&#8419; 2&#65039;&#8419; CI for Drupal 7 CoreMR in Needs Review: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/3387052" title="Status: Closed (fixed)">#3387052: [D7] GitLab CI integration for core</a></span>&nbsp;(edited)&nbsp;</h2> <table> </table> <h2>2&#65039;&#8419; 3&#65039;&#8419; CI for Modern contrib -- this has already been 'done' for a while - may benefit from some improvements we are finding.</h2> <table> <tr> <td>larowlan</td> <td>Yes I wonder what we can improve based on core things</td> </tr> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>I'd wait until we get a little further, but there is loads of things we can port that are quite valuable, as inline codestyle issues, and perhaps the concurrency support.Hopefully it hasnt diverged to much.</td> </tr> <tr> <td>andypost</td> <td>I hope search api, redis, memcache contrib can benefit from new docker images&nbsp;(edited)</td> </tr> <tr> <td>wimleers (he/him)</td> <td>Yes I wonder what we can improve based on core things:100:Core has jumped so far ahead now that it feels ancient? :stuck_out_tongue:</td> </tr> <tr> <td>wimleers (he/him)</td> <td>But +1 to first getting 100% of core done, and then applying lessons learned to contrib.</td> </tr> </table> <h2>2&#65039;&#8419; 4&#65039;&#8419; CI for D7 contrib - A template for CI for D7 contrib has been proposed here: <a href="https://drupal.slack.com/archives/CGKLP028K/p1695227405485629 ">https://drupal.slack.com/archives/CGKLP028K/p1695227405485629 </a>(edited)&nbsp;</h2> <table> <tr> <td>hestenet (he/him)</td> <td><span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/gitlab_templates/-/issues/3343810" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/gitlab_templates/-/issues/3343810</a></span></td> </tr> </table> <h2>3&#65039;&#8419; GitLab InfrastructureIncreased usage has exposed performance issues.The concurrency limit in GitLab config was set/raised.One issue is already (mostly) resolved - excessive redirects: <a href="https://drupal.slack.com/archives/C51GNJG91/p1695140980564319Our">https://drupal.slack.com/archives/C51GNJG91/p1695140980564319Our</a> GitLab1 needs a migration from OSU OSL to AWS alongside GitLab-aws - we are working on a staging cluster to validate that geo replication will survive the transition. (edited)</h2> <table> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>:crossed_fingers:</td> </tr> <tr> <td>markdorison</td> <td>Gitlab1 and Gitlab2 are different instances used for failover?</td> </tr> <tr> <td>drumm</td> <td>gitlab2 actually no longer exists. gitlab1 is the geo primary, gitlab-aws is the secondary and serves most http traffic</td> </tr> <tr> <td>drumm</td> <td>We also need to set all of this up in staging so we know what to expect when promoting a secondary to primary</td> </tr> </table> <h2>4&#65039;&#8419; GitLab Issues - we are making some progress on getting ready for the SSO work that enables the credit migration that enables the issue opt-in process.@heddn has been working with us on that, keycloak instance updated, rebasing/rerolling some issues etc.We won't have the sso migration/issue opt in switch before Lille, but I hope we can get to it as the next big push after we get back.With all the CI momentum I'm really feeling the energy to move this next.&nbsp;(edited)&nbsp;</h2> <table> </table> <p>Participants:</p> <p>andypost, hestenet, larowlan, poker10, bbrala, Wim Leers, markdorison, drumm</p>