home.social

#gitlab — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gitlab, aggregated by home.social.

  1. How to Install #GitLab on #AlmaLinux #VPS Easily

    In this tutorial we are going to show you in detail how to install Gitlab on AlmaLinux VPS.
    What is GitLab?
    GitLab is open-source ...
    Continued 👉 #dedicatedserver #selfhosting #rubygems #opensource #installguide #rubyonrails #selfhosted

    How to Install GitLab on AlmaL...

  2. GitLab Patches Code Execution Flaw in CI/CD Compiler

    GitLab has patched a critical code-execution flaw in its CI/CD compiler that allowed remote attackers to run arbitrary code on targeted instances. The vulnerability, tracked as CVE-2026-97229, was caused by an integer overflow weakness in the CI/CD Regular Expression Compiler.

    osintsights.com/gitlab-patches

    #Gitlab #CodeExecution #Cicd #RegularExpressionCompiler #Cve202697229

  3. GitLab security advisory. The standout CVE is a 10.0 critical CVE-2026-97229 - Integer Overflow issue in CI/CD Regular Expression Compiler impacts GitLab CE/EE

    docs.gitlab.com/releases/patch

  4. GitLab Critical Patch Release: 19.4.2, 19.3.4, 19.2.8

    Fixed an integer overflow in the CI/CD regular expression compiler that could allow an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in CI/CD configuration (CVE-2026-97229)

    whatsnew.fyi/product/gitlab/re

    #GitLab #DevTools

  5. GitLab Patches CVE-2026-97229 (CVSS 10.0) Flaw That Lets Unauthenticated Attackers Execute Arbitrary Code

    securityonline.info/gitlab-cve

  6. The bill for my CI runner fleet came to $270, which doesn't sound like a lot of money until it's money you haven't got.

    The two easy answers were spend more or test less. I wasn't having the second one. I'd rather pay in waiting time than drop a single test.

    So I went through the receipt line by line: three weeks, 3,373 merge-request pipelines, 31,247 jobs. My hunch about where the money went was wrong.

    The scary heavy jobs (mutation, fuzz, cross-arch) came to 5.7% of merge-request minutes. Renovate's branches were nearly half. Release merge requests were another 20.4%, entirely self-inflicted: I'd put CHANGELOG.md in the test jobs' change rules, so a file of markdown woke the whole suite.

    Then main was rerunning the heavy jobs on the exact commit the merge request had already tested. 1,075 runner minutes to produce the same answer.

    The fixes add up to something like 40% fewer merge-request minutes, and not one of them is a test I stopped running.

    Most of that receipt was things I'd bought twice, which stings a bit more than the $270 did.

    phpboyscout.uk/which-tests-wou

  7. The bill for my CI runner fleet came to $270, which doesn't sound like a lot of money until it's money you haven't got.

    The two easy answers were spend more or test less. I wasn't having the second one. I'd rather pay in waiting time than drop a single test.

    So I went through the receipt line by line: three weeks, 3,373 merge-request pipelines, 31,247 jobs. My hunch about where the money went was wrong.

    The scary heavy jobs (mutation, fuzz, cross-arch) came to 5.7% of merge-request minutes. Renovate's branches were nearly half. Release merge requests were another 20.4%, entirely self-inflicted: I'd put CHANGELOG.md in the test jobs' change rules, so a file of markdown woke the whole suite.

    Then main was rerunning the heavy jobs on the exact commit the merge request had already tested. 1,075 runner minutes to produce the same answer.

    The fixes add up to something like 40% fewer merge-request minutes, and not one of them is a test I stopped running.

    Most of that receipt was things I'd bought twice, which stings a bit more than the $270 did.

    phpboyscout.uk/which-tests-wou

  8. I just sponsored zaccesss for the git-tutorial. Go sponsor the people behind open-source dependencies and projects!

    Practical Git learning guide covering version control foundations, Codeberg, forgejo, gitea, GitHub, GitLab, branching, collaboration workflows and advanced command line usage:
    github.com/zaccesss/git-unlock

    @isaacadjei is #newhere, he registered on 9. October 2026

    isaacadjei.me/
    github.com/sponsors/zaccesss

    #sponsor #opensource #git #course #greatpeople #forgejo #codeberg #git #github #branching #gitlab #gitea #uk #developer #new #plboost #boost

  9. Shipped today: Enkihost can now deploy your app straight from GitLab.

    Connect your repo, push your code, and your Ruby, Rails or Jekyll site goes live. No server setup, no babysitting.

    Still early days, so if you try it, I’d love to hear what works and what doesn’t.

    enkihost.com

    #Ruby #RubyOnRails #Jekyll #GitLab #BuildInPublic

  10. @NuclearSquid I was not a big fan either until I discovered this #git feature.
    Also, I'll use it on #Codeberg, not #Github.
    I'm sooooo glad that my next employer uses #gitlab and not #github!
    @halibut @TheyCallMeHacked

  11. Your GitLab container registry doesn't have to fill up with untagged images from 18 months ago. Learn automated garbage collection and retention policies at 2 AM prevention: valtersit.com/guides/gitlab/gi #gitlab #devops

  12. A Woodpecker CI 3.19 bezárta a titkokat kihasználó sebezhetőséget és hozott szerver által kikényszerített agent-címkéket — ez mit jelent a te CI-dre? Új runtime változók és local backend rugalmasság is van, érdemes elolvasni.

    linuxmint.hu/hir/2026/10/megje

    #WoodpeckerCI #CI #CICD #security #agent #GitHub #GitLab #localbackend #kubernetes

  13. Bonjour à toutes et à tous ! 👋

    Concevoir un Pad institutionnel, collaboratif et directement hébergé sur la Forge : cela me trottait dans la tête depuis un moment... 👀

    C'est maintenant disponible et ça s'appelle TickéPad !

    → tickepad.forge.apps.education.

    (1/3)

    #NumériqueÉducatif #GitLab #LaForgeÉdu #CommunsNumériques #LogicielLibre

Share on Mastodon

Enter the server where you have an account.