>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3300285. --> 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 06: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>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 kicking off all our threads.</td> </tr> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>Bj&ouml;rn, gitlab breaker, looking around.</td> </tr> <tr> <td>fjgarlin</td> <td>Fran, checking threads &#128578;</td> </tr> <tr> <td>irinaz</td> <td>Irina, joining late, sorry</td> </tr> <tr> <td>quietone</td> <td>Hi, Catching up</td> </tr> <tr> <td>Shriaas</td> <td>Hi :wave:</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;&nbsp; Yesterday we had a git.drupalcode.org outage -Recap: Gitlab uses Puma for it's webserver and Sidekiq for enqueuing tasks. Some combination of additional traffic, git clones for DCI testing, and GitLab's own replication behavior when it 'geo-syncs' from the primary to secondary seems to have overloaded it.We've done a few things:Tuned the number of parallel processes allowed by Puma and SidekiqIncreased server resources (primary Ram) Begun investigating things like S3 archiving for artifacts (which we'll need anyway) to reduce the load that is synced back between primary and secondary. (edited)</h2> <table> <tr> <td>hestenet (he/him)</td> <td>Prior to this we've also been working on tuning the Kubernetes runner settings for GitLabCI&nbsp; - as mentioned earlier in this channel.We're allowing more timeouts before abandoning a jobAnd we've disabled 'area balancing' which could abruptly kill a job in the middle. We do still need to investigate other causes of potential GitLabCI cluster overload, as discovered by @Bj&ouml;rn Brala (bbrala) when working on the project analysis work. (There are some separate threads where that's been going on)</td> </tr> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>Great to hear about the work you are doing. :grinning: Hopefully it will help stabilise the env</td> </tr> </table> <h2>3&#65039;&#8419; Lots of progress is being made on the issue migration toolset thanks to @fjgarlin. The tools are oriented around 5 drush commands that we would use, with a detailed description in this comment:<span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3295357" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3295357</a></span>#comment-14627344</h2> <table> <tr> <td>fjgarlin</td> <td>I&rsquo;ll try to do a short video my tomorrow-morning and link it here and in the issue. Reviews on the MR are welcome.</td> </tr> <tr> <td>fjgarlin</td> <td>Raw unedited video of a full test migration for a module (within my own d.o copy) with 3 issues with different relations between the issues, attached files, labels, etc. I tried first a module with way more issues, but it was just a lot of waiting for the same results.We can see how the script runs, creates labels, issues, comments, attached files, relationships between issues, etc.The warnings on the terminal are just because I&rsquo;m running this on my personal gitlab account and I can&rsquo;t obviously impersonate other people there.</td> </tr> <tr> <td>fjgarlin</td> <td>it&rsquo;s not 100% ready and needs plenty of testing but shows the progress made so far</td> </tr> </table> <h2>4&#65039;&#8419; GitLabCI is being used in some new ways that are certainly helping exercise our set up and find some limitations:@Bj&ouml;rn Brala (bbrala) has been using it to rebuild the D10 Project Analysis job to run independently of DrupalCI infrastructure@alexpott has been using it for what I would call a 'core-mega-patch' generation workflow for: <a href="https://www.drupal.org/project/distributions_recipes">https://www.drupal.org/project/distributions_recipes</a> </h2> <table> </table> <h2>5&#65039;&#8419; Speaking of GitLabCI usage - a kind of random question - have any of you who have done early work with the GitLabCI setup done any D7 testing with it?Or has everyone been doing just their D9+ testing so far?&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>Bj&ouml;rn Brala (bbrala)</td> <td>I'm privileged, I have no real d7 experience except as a migration source :sweat_smile:</td> </tr> <tr> <td>irinaz</td> <td>@moshe, are you doing any Gitlab testing for D7 modules? :thankful:</td> </tr> <tr> <td>moshe</td> <td>No.</td> </tr> <tr> <td>irinaz</td> <td>@moshe, thanks!&nbsp; For D7 (core and modules) would you suggest having a separate gitlab-ci file in D7 branch or try to integrate one gitlab-ci&nbsp; file for both D7 and D9+? My approach would be to have separate files, I wanted to confirm that it is good approach.</td> </tr> <tr> <td>moshe</td> <td>I recommend not spending any time working on d7 until we deliver gitlab issues and d9+ ci.</td> </tr> <tr> <td>Brad Jones</td> <td>No D7 for me</td> </tr> <tr> <td>hestenet (he/him)</td> <td>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 06: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.ping: @mixologic @FeyP @jurgenhaas (go to the issue of the next meeting to add or remove yourself from the list)</td> </tr> </table> <h2>6&#65039;&#8419; Related to the issue migration we're going to be reviewing some policy and worklow related to GitLab labels, and how our existing issue meta data translates over.In particular:Today 'global' tags on d.o can be managed by a variety of users, not just DA staff - with GitLab permissions, that may be a staff only capability, so we may need to set up a new process/policy for that. Projects will be able to define all of their own local labels, but some labels may need to be global. How careful we need to be with all this will depend on how well searching works when the same label exists both as a local project label and as a global label (or as multiple local project labels on different projects) We'll likely ask this group for some thoughts/opinions/brainstorming. Of course if you have some label management ideas already, please feel free to share here!We'll update this issue as the parent (or directly) when we get there: <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/infrastructure/-/work_items/3254602" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/infrastructure/-/work_items/3254602</a></span>&nbsp;(edited)&nbsp;</h2> <table> <tr> <td>fjgarlin</td> <td>The work made in 3&#65039;&#8419; makes some assumptions about labels and global labels. Will try to link the issues tomorrow (phone right now).</td> </tr> <tr> <td>fjgarlin</td> <td>Turns out I already linked them &#128578;</td> </tr> <tr> <td>hestenet (he/him)</td> <td>Perfect</td> </tr> </table> <h2>7&#65039;&#8419; <span class="drupalorg-gitlab-issue-link drupalorg-gitlab-link-wrapper"><a href="https://git.drupalcode.org/project/drupalorg/-/work_items/3300281" class="drupalorg-gitlab-link">https://git.drupalcode.org/project/drupalorg/-/work_items/3300281</a></span> will be upcoming as well</h2> <table> </table> <p>Participants:</p> <p>hestenet, Bj&ouml;rn Brala (bbrala), fjgarlin, irinaz, moshe, Brad Jones</p>