GitLab Acceleration Initiative meeting on 5 April, 2023

Created on 22 March 2023, over 1 year ago
Updated 26 May 2023, about 1 year ago

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️⃣ As mentioned above, GitLab has announced their intentions to adopt a community fork model for contribution to GitLab itself (or at least to try it!)This is great news, because they will be facing similar challenges, and any changes they make to support that workflow should make it easier for us to do the same: https://about.gitlab.com/blog/2023/04/04/gitlab-community-forks/

3️⃣ The update to 15.10 revealed two bugs, which we are still hoping for resolution for, from the GitLab team, we opened issues which they are working on

3️⃣ 1️⃣  Clone URL configuration no longer respected:https://gitlab.com/gitlab-org/gitlab/-/issues/404496

3️⃣ 2️⃣ 500 errors on geo primary when geo secondary is unavailable(Secondary status should not degrade primary)https://gitlab.com/gitlab-org/gitlab/-/issues/404497

4️⃣ Moshe has offered an example of some CI improvements with the Akamai test project - which I hope to incorporate into the GitLabCI templates: https://drupal.slack.com/archives/CGKLP028K/p1680482989175279

5️⃣ Could use help from people with existing GitLab CI runner configuration expertise to help improve peformance.@larowlan has been working on getting it to run the core sweet, and has been successful, except that it times out!Can we get some assistance with the performance issues seen while trying to convert core testing to use gitlab - e.g KernelTest fail after 3 hr timeout. We're at the point now where timeouts seem to be the main blocker. Both Functional (2hrs) and Kernel (3hrs) are hitting timeout limits. There's a few Javascript fails but as we know they happen from time to time in DrupalCI too. In DrupalCI we use a volume in the host config. Perhaps we don't have the equivalent mount into the database image in the gitlab runner?This is something I intend to look into but I don't personally have too much expertise in GitLab runner config.

🌱 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

Production build 0.69.0 2024