Contrib.social

GitLab Acceleration Initiative meeting on 29 June, 2022

Open on Drupal.org →
Created on 29 June 2022, over 2 years ago
Updated 3 January 2024, 11 months ago

This meeting:
➤ Is for core developers, initiative contributors, the Drupal Association and anyone interested in the initiative.
➤ Usually happens every other Wednesday at 11:00 PT / Thursday 06:00 UTC
➤ Is done over chat.
➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ 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.
➤ Has a public agenda anyone can add to in the issue
➤ *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.

ping: @mixologic @FeyP @jurgenhaas (go to the issue of the next meeting to add or remove yourself from the list)

Transcript

0️⃣  Who is here today? Comment in the thread below to introduce yourself!

1️⃣ 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.

2️⃣ Testing updates:

2️⃣ 1️⃣  Cost controls - working with GitLab to add the ability to set per-project CI/CD limits:@irinaz has done a lot of work with Drew Cimino at GitLab to help get initial work ready to add per-project limits: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/90537And they have a related MVC with a target of version 15.5, which would be: 2022-10-22: https://gitlab.com/gitlab-org/gitlab/-/issues/357760

2️⃣ 2️⃣ GitLabCI runners have been having scheduling errors lately - #3277265: Pods go away randomly while running phpunit → - and it looks like this is actually a broader issue with our k8s configuration, as we also see it with the D10 project analysis job which uses a k8s cluster managed by jenkins rather than GitLab. Because the clusters are ephemeral, getting useful logs is tough, so we're adding more introspection to try and track down the cause.

2️⃣ 3️⃣  Additional projects have been added to the GitLab opt-in, per: #3261803: Using GitLab CI instead of Drupal CI →

3️⃣ Issue migration updates:

3️⃣ 1️⃣ Before we can move issues to GitLab we're going to need to handle all of the references to existing d.o issues. @fran on our team has been auditing the use of issue entity references, etc, to get us ready for this transition process. #3265097: Remove/replace issue integration with the rest of www.drupal.org → (and child issues)

3️⃣ 2️⃣ In particular - one of the areas that will be impacted is Change Notices - today change notices can provided an embedded view of all referenced issues, which is functionality that will go away. We will need to provide the simplest possible option for the key maintainers who use entity references to easily add relevant GitLab issues. Something to start thinking about. #3265112: Decouple change records from www.drupal.org issues →

4️⃣ Auth/SSO updates:Improving authentication and account creation to make it easier to join the community was set as a goal during Dries' initial GitLab Acceleration proposal, though it's not really directly related to GitLab itself - nevertheless, we have some good progress to report.

4️⃣ 1️⃣  We've been working with the team at Tag1 on setting up an Oauth-based identity system, using KeyCloack. We're in the phase where we're doing initial user migration (in the background, nothing users can see yet), and resolving blockers along the way that come from d.o's very long user account history.e.g: Resolving legacy users with duplicate case-sensitive usernamesWe're very close to getting through all the migration blockers, and then will need to finalize account management/ui changes/build catch-up migration process, and schedule this.

Participants:

hestenet, moshe, drumm

🌱 Plan
Status

Fixed

Component

Meeting

Created by

🇺🇸United States hestenet Portland, OR 🇺🇸

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024