Development platform: GitLab 18.10 introduces login via Passkey

The release enables passwordless login with Passkeys and detects false positive SAST vulnerabilities using the GitLab Duo Agent Platform.

https://www.heise.de/en/news/Development-platform-GitLab-18-10-introduces-login-via-Passkey-11219869.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#ContinuousIntegration #Entwicklungsumgebung #Git #IT #Passkey #Versionskontrolle #news

Development platform: GitLab 18.10 introduces login via Passkey

The release enables passwordless login with Passkeys and detects false positive SAST vulnerabilities using the GitLab Duo Agent Platform.

heise online

Entwicklungsplattform: GitLab 18.10 führt Anmeldung per Passkey ein

Das Release ermöglicht die passwortlose Anmeldung mit Passkeys und erkennt falsch positive SAST-Vulnerabilities mithilfe der GitLab Duo Agent Platform.

https://www.heise.de/news/Entwicklungsplattform-GitLab-18-10-fuehrt-Anmeldung-per-Passkey-ein-11219727.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#ContinuousIntegration #Entwicklungsumgebung #Git #IT #Passkey #Versionskontrolle #news

Entwicklungsplattform: GitLab 18.10 führt Anmeldung per Passkey ein

Das Release ermöglicht die passwortlose Anmeldung mit Passkeys und erkennt falsch positive SAST-Vulnerabilities mithilfe der GitLab Duo Agent Platform.

heise online

Test failures on CI often result in time consuming root cause analysis involving scrolling through lengthy GitHub Actions CI logs.

Check out our latest blog post to learn how the new Test Failure Details feature surfaces test failures directly in Pull Requests to streamline the troubleshooting process!

https://testlens.app/blog/2026/03/18/test-failure-details/

#ContinuousIntegration #Testing #Java #GitHub

Analyze Test Failures Quickly With the Test Failure Details View

Test failures on CI often result in time consuming root cause analysis involving scrolling through lengthy GitHub Actions CI logs. To address this well-known pain point, we've introduced the test failure details view, that surfaces the failing assertion directly in you pull request.

iX-Workshop: Deep Dive in Helm – Kubernetes-Anwendungen effizient verwalten

Lernen Sie praxisnah, wie Sie Kubernetes-Applikationen mit Helm in modernen Containerumgebungen aktiv und effizient verwalten.

https://www.heise.de/news/iX-Workshop-Deep-Dive-in-Helm-Kubernetes-Anwendungen-effizient-verwalten-11203508.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#Containerisierung #ContinuousDelivery #ContinuousIntegration #DevOps #IT #iXWorkshops #Kubernetes #OpenSource #news

iX-Workshop: Deep Dive in Helm – Kubernetes-Anwendungen effizient verwalten

Lernen Sie praxisnah, wie Sie Kubernetes-Applikationen mit Helm in modernen Containerumgebungen aktiv und effizient verwalten.

heise online

c’t-Workshop: GitLab CI im Praxiseinsatz

GitLab CI/CD verstehen und anwenden: Der Workshop zeigt, wie Sie Pipelines für Builds, Tests und Deployments strukturieren und effizient im Team nutzen.

https://www.heise.de/news/c-t-Workshop-GitLab-CI-im-Praxiseinsatz-11211686.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#ContinuousDelivery #ContinuousIntegration #Git #IT #Softwareentwicklung #news

c’t-Workshop: GitLab CI im Praxiseinsatz

GitLab CI/CD verstehen und anwenden: Der Workshop zeigt, wie Sie Pipelines für Builds, Tests und Deployments strukturieren und effizient im Team nutzen.

heise online
What CI Actually Looks Like at a 100-Person Team

575K CI jobs, 1.18 billion log lines, 33 million test executions — in one week. What we learned building an AI agent for PostHog's CI at scale.

I organize a weekly "office hour", for questions about Radicle CI, distributed CI, local-first CI, or related topics. Sometimes there's a demo or little presentation.

It's on Wednesdays, alternate weeks either morning (08 UTC) or evening (17 UTC), at https://meet.ffmuc.net/radicleciofficehour (Jitsi, only needs browser, mic and webcam optional but helpful).

This week on Wednesday, March 18, at 17:00 UTC (18 CET, 19 EET).

cc @radicle

#Radicle #RadicleCI #ContinuousIntegration #OfficeHour

Jitsi Meet

Join a WebRTC video conference powered by the Jitsi Videobridge

Quality by a thousand cuts — ottorask.com

Refactoring a codebase should be a continuous activity, even outside “regular feature development”. It should be painless, swift, and as automated as possible to refactor a single line of code and ship that change into production on its own. This approach requires continuous integration and continuous delivery, and will become nearly impossible with a pull request based workflow. Being able to ship miniscule commits multiple times an hour will allow you to enhance your codebase so much more than any quality-gate setup will. In software we should be able to improve quality with many more much smaller steps, hence achieving quality by a thousand cuts.

Pull requests: quality theater with questionable results — ottorask.com

Does your organization prefer or maybe even force pull requests for reviewing and validating changes before integrating to a mainline? I have news for you: you’re engaged in quality theater and the only thing the PRs are doing for you is add cognitive load and delays while preventing you from finding better ways to ensure you’re shipping a quality product without delays.

The purpose of Continuous Integration is to fail

CI is only valuable when it fails. When it passes, it's just overhead: the same outcome you'd get without CI.

NixCI Blog