#CI

#UbuCon Korea 2026 접수 마감까지 앞으로 1️⃣ 일!
이어서 다른 주제와 사례도 함께 소개 드립니다.

☁️ 인프라와 클라우드

#우분투 로 구축하는 #CI #CD, #네트워크 를 비롯,
#클라우드 #컨테이너 제작과 #배포, #가상화 기술 등
#리눅스 사용 사례가 가장 많은 #서버 에서의 #Ubuntu 사용기를 기다립니다.

지난해에는 유승우 님께서 홈 서버 구축 이야기를 해 주셨습니다 :)
https://youtu.be/v1J5UsqSfGQ?si=Z3sVznuy-Xt2gDeQ

#UbuCon Korea 2026 접수 마감까지 앞으로 1️⃣ 일!
이어서 다른 주제와 사례도 함께 소개 드립니다.

☁️ 인프라와 클라우드

#우분투 로 구축하는 #CI #CD, #네트워크 를 비롯,
#클라우드 #컨테이너 제작과 #배포, #가상화 기술 등
#리눅스 사용 사례가 가장 많은 #서버 에서의 #Ubuntu 사용기를 기다립니다.

지난해에는 유승우 님께서 홈 서버 구축 이야기를 해 주셨습니다 :)
https://youtu.be/v1J5UsqSfGQ?si=Z3sVznuy-Xt2gDeQ

🚨 Update to #WoodpeckerCI v3.14.1 for critical security fixes! Now agent_id spoofing is blocked, keeping your builds safer than ever. Huge thanks to security researchers & fixers! 🔒✨ #release #Security #DevSecOps #CI #OpenSource

WoodpeckerCI v3.14.0 is here! 🚀 Enjoy one-shot agent mode, external secret & container registry credential support, enhanced Kubernetes features, and stronger security fixes. Update now for smoother, safer CI! 🔒✨ #WoodpeckerCI #release #CI #DevOps #Kubernetes

Question for the Python people: How do you handle type checking in CI? Do you just install all the dependencies every time the pipeline runs? Do you have some logic to install missing type stubs (or the real dependencies, if there are no stubs)? Something else entirely?

#python #ci #cicd #dev

You have a #project and want to know (or block) if a contribution is AI made?

we at #WoodpeckerCI have packaged the #AgentScan as #plugin: https://woodpecker-ci.org/plugins/agentscan

#ci #automation

The @nixos_org integration tests have always been a fantastic tool - We just made them even faster and much simpler to run! 🚀 By adding a new lightweight container backend to the test driver, you can now run your suites on standard, non-KVM hosts. 👇

Here is what the new container backend brings to your NixOS workflow:

⚡ Blazing Fast Execution: How fast? Booting two machines, letting them ping each other, and tearing them down now takes ~3 seconds!
💸 Run Anywhere (Cheaper!): You no longer need bare-metal KVM-enabled hosts. Your tests can now run seamlessly on cheap, standard VMs.
🎮 GPU Testing Support: Hardware acceleration is now accessible. You can finally test GPU-dependent workloads directly inside your integration tests!

Curious how it works under the hood and how to enable it in your projects? Dive into our latest article and try it out for yourself!

🔗 Read the full breakdown here: https://nixcademy.com/posts/faster-cheaper-nixos-integration-tests-with-containers/

#NixOS #DevOps #Testing #Linux #Nix #InfrastructureAsCode #CI #Containers

The @nixos_org integration tests have always been a fantastic tool - We just made them even faster and much simpler to run! 🚀 By adding a new lightweight container backend to the test driver, you can now run your suites on standard, non-KVM hosts. 👇

Here is what the new container backend brings to your NixOS workflow:

⚡ Blazing Fast Execution: How fast? Booting two machines, letting them ping each other, and tearing them down now takes ~3 seconds!
💸 Run Anywhere (Cheaper!): You no longer need bare-metal KVM-enabled hosts. Your tests can now run seamlessly on cheap, standard VMs.
🎮 GPU Testing Support: Hardware acceleration is now accessible. You can finally test GPU-dependent workloads directly inside your integration tests!

Curious how it works under the hood and how to enable it in your projects? Dive into our latest article and try it out for yourself!

🔗 Read the full breakdown here: https://nixcademy.com/posts/faster-cheaper-nixos-integration-tests-with-containers/

#NixOS #DevOps #Testing #Linux #Nix #InfrastructureAsCode #CI #Containers

If you love automating things, this post is for you!
#DevConf_CZ 2026 is looking for speakers who know #DevOps, #CI, #CD and #Automation.

Tell the community your tips and tricks on making things work by themselves 🤖

👉 Submit proposal: https://pretalx.devconf.info/devconf-cz-2026/cfp

TestLens launches to accelerate Java and Kotlin pull request workflows!

Know this problem? You’re done with implementing a feature, but getting your PR through the CI pipeline is tedious. TestLens assists you to get your pull requests merged faster by posting an easy-to-read summary of failed tests and by rerunning failed tests only!

Read more in our announcement post and join the private beta: https://testlens.app/blog/2026/02/04/testlens-private-beta-launch

#Java #Kotlin #CI #GitHub #Gradle #Maven #JUnit #ProductLaunch

Two shifts: CI companies offering their envs as runners for Jenkins and similar. And GitHub runner providers pivoting to agent sandboxes because GitHub wants to compete with them. Both finding new ground. AWS will follow. Prices will drop. DX will differentiate. #CI #AI #DevTools #OpenSource

WoodpeckerCI v3.13.0 is here! 🚀 New CLI contexts, notes on secrets, cron custom vars & disabling, Kubernetes pod affinity & headless services support, plus enhanced security & bug fixes. Update now for a smoother CI/CD! 🔧✨ #WoodpeckerCI #release #CI #DevOps 🛠️

New #blog post: Playing around with #Woodpecker #CI

I decided to deploy Woodpecker into my LAN and hook it up to my #gitlab instance

This post talks about deploying it and configuring CI jobs to periodically rebuild some container images (which are then pulled by #watchtower at the consuming end)

There's also a bonus section on having #telegraf squash container names in metrics to avoid excessive cardinality growth

https://www.bentasker.co.uk/posts/blog/general/playing-with-woodpecker-ci.html

New #blog post: Playing around with #Woodpecker #CI

I decided to deploy Woodpecker into my LAN and hook it up to my #gitlab instance

This post talks about deploying it and configuring CI jobs to periodically rebuild some container images (which are then pulled by #watchtower at the consuming end)

There's also a bonus section on having #telegraf squash container names in metrics to avoid excessive cardinality growth

https://www.bentasker.co.uk/posts/blog/general/playing-with-woodpecker-ci.html

Does anyone knows good way to find #gig opportunity for software dev? I'd like to avoid pitfalls of well known platforms. I can do:
- #Rust CLI/Dev tools, APIs
- #C code (#FreeRTOS, #Zephyr, #Linux including some #drivers or #v4l2)
- #Cpp C++ code
- #Bash or #Python scripts, tools
- #CI workflows (GitHub, GitLab)
- #Yocto layers
- #Debian packaging + #DKMS

Anyone has experience in getting hands on small projects?

Edit: I can #teach / #training Rust or C++.

#FediHire

I'm exploring what #GitHub alternatives exist. I have something neat to share.

See the little checkmark on this repo?

https://codeberg.org/louwers/duckdb-builds

The #CI of this #Codeberg repository is running on #SourceHut. Bridged with yojo https://yojo.emersion.fr/

I think each platform has its advantages, but definitely CI is a strong aspect of SourceHut and a weak point of Codeberg / #Forgejo. Both projects are based in the #EU and are open source.

What is your experience with #GitHub alternatives?

Still a lot work to do, but for the first time, we got completely integrated CI testing of kernels running... on a phone! For what I know, this is a first for a non-multi-million-euro-company in the FOSS world!! Can't be more proud of it and all the people that helped during this journey.

https://gitlab.postmarketos.org/postmarketOS/pmaports/-/jobs/1465886 is a bit cryptic, and might look like any other gitlab CI job, but is actually booting on a OP6T at @mupuf farm!!

There's still a long road ahead, but in the future we might be able to automate kernel upgrades with a lot less manual testing, and continue working the "reliability" goal we presented in https://postmarketos.org/blog/2025/03/30/pmOS-year-priorities/

Huge thanks to @mupuf for all his work and dedication on ci-tron, to @cas for the initial dream and work all across the stack, to @fizzo and @corna, for the PCB that drives the phone, and to @fun, @adrianyyy, and @cas again for the work on Tauchgang. Truly team work :)

More details in some weeks in a blog post near you ;)

#postmarketos #ci #hw-ci #testing #linuxmobile #foss

🚀 Woodpecker 3.10.0 is live!
- Pull‑request metadata & task‑UUID labels for tighter CI pipelines
- New org‑listing API (CLI & Go SDK) + milestone support
- Smarter error traces, CLI auto‑completion & human‑readable queue info
- Dozens of dependency fixes

Upgrade now for a smoother CI experience! 🎉 #CI #DevOps #woodpeckerci #release

https://github.com/woodpecker-ci/woodpecker/releases/tag/v3.10.0

🚀 WoodpeckerCI 3.12.0 is here! Get full commit changes in Bitbucket pushes, support file changes in Bitbucket Cloud, agent version logging & improved log streaming. Plus many bug fixes & security updates! Upgrade now! 🔒🐦 #WoodpeckerCI #release #CI #DevOps #Changelog

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Just opened an issue for a major new task for #Fedify: building an #interoperability smoke test suite.

To ensure Fedify-built servers federate correctly with the wider #fediverse, we're planning to run automated E2E tests in #CI against live instances of Mastodon, Misskey, and more. This is crucial for a framework's reliability.

You can see the full plan and discussion here:

https://github.com/fedify-dev/fedify/issues/481

#ActivityPub #fedidev

Looking into alternate #CI systems this weekend. Cirrus CI looks neat. https://garden.pacia.tech/cirrus_ci_is_the_best.html

I wrote about how CI/CD evolved from stagnant proprietary platforms to the vibrant GitHub Actions runner ecosystem.

The runner market shows what's possible when infrastructure is decoupled and developers have real choice. Competition drives genuine innovation.

Interactive demo + Mac runner directory:
https://runs-on-mac.com/

#OpenSource #DevOps #GitHubActions #CI

I wrote a story about how CI/CD evolved from stagnant proprietary mobile CI platforms to the vibrant GitHub Actions runner ecosystem.

The runner market shows what's possible when infrastructure is decoupled and developers have real choice. Competition drives genuine innovation.

Interactive demo + Mac runner provider directory:
https://runs-on-mac.com/

#OpenSource #DevOps #GitHubActions #CI

This post of mine is just a week old and I've already sent it to three people in reply to their questions about how to do exactly that.

And I'm using it now as a reference to implement the same on another project.

So, I figured I might link to it again for those who have missed it somehow:)

https://dev.to/justlig/podman-on-gitlab-ci-fast-efficient-container-builds-no-dind-required-e2e

#Docker #Podman #GitlabCI #Gitlab #CI #CICD

🚀 Woodpecker 3.10.0 is live!
- Pull‑request metadata & task‑UUID labels for tighter CI pipelines
- New org‑listing API (CLI & Go SDK) + milestone support
- Smarter error traces, CLI auto‑completion & human‑readable queue info
- Dozens of dependency fixes

Upgrade now for a smoother CI experience! 🎉 #CI #DevOps #woodpeckerci #release

https://github.com/woodpecker-ci/woodpecker/releases/tag/v3.10.0

If you need to plug #CI runners to @Codeberg or any Forgejo instance, you might find this useful:

https://pepicrft.me/blog/2024/11/24/forgejo-runner-in-hetzner

Have you ever wanted to lint markdown... fast?

🌀 **mado** — A Markdown linter written in Rust 🦀

✅ Compatible with CommonMark and GitHub Flavored Markdown (GFM).

🔥 Approx. 49-60x faster than existing linters

⭐ GitHub: https://github.com/akiomik/mado

#rustlang #markdown #linter #github #actions #ci #commandline

Have you ever wanted to lint markdown... fast?

🌀 **mado** — A Markdown linter written in Rust 🦀

✅ Compatible with CommonMark and GitHub Flavored Markdown (GFM).

🔥 Approx. 49-60x faster than existing linters

⭐ GitHub: https://github.com/akiomik/mado

#rustlang #markdown #linter #github #actions #ci #commandline

🧪 "Let's build an openQA testsuite, from scratch"
with Sam Thursfield at #GUADEC2025
📅 25 July 🕒 09:40 CEST 📍 Brescia

🖥️ Sam shows how to set up openQA + GitLab CI to test GNOME apps visually—step by step.

🔗 https://events.gnome.org/event/259/contributions/1215/

#GNOME #openQA #Testing #CI #FOSS

🚀 Stay ahead in IT Infrastructure & Development! 💻☁️🔧
Follow me: @kevinveenbirkenbach@microblog.infinito.nexus for #CyMaIS news at https://cymais.cloud 🌐🆕

🔍 Topics: #CloudComputing #DevOps #Microservices #Kubernetes #SoftwareDev #CyberSecurity #Automation #DigitalTransformation

📈 Trends: #InfrastructureAsCode #CI #CD #Serverless #Agile #BusinessGrowth #StartupLife #DigitalStrategy

👉 Connect & grow together! 🤝✨

Status update: I'm now automatically building and releasing a signed fork of stable moshidon with my patches. #CI is cool!

https://github.com/cactichameleon9/moshidon-fork

#CICD #GithubActions #Moshidon

GitHub Actions now supports free-threaded Python!

I wrote up how to add it your workflows so you can start testing free-threaded Python 3.13 and 3.14 with either actions/setup-python or actions/setup-uv.

https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/

#Python #FreeThreaded #GitHub #GitHubActions #CI #testing

GitHub Actions now supports free-threaded Python!

I wrote up how to add it your workflows so you can start testing free-threaded Python 3.13 and 3.14 with either actions/setup-python or actions/setup-uv.

https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/

#Python #FreeThreaded #GitHub #GitHubActions #CI #testing

GitHub Actions now supports free-threaded Python!

I wrote up how to add it your workflows so you can start testing free-threaded Python 3.13 and 3.14 with either actions/setup-python or actions/setup-uv.

https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/

#Python #FreeThreaded #GitHub #GitHubActions #CI #testing

GitHub Actions now supports free-threaded Python!

I wrote up how to add it your workflows so you can start testing free-threaded Python 3.13 and 3.14 with either actions/setup-python or actions/setup-uv.

https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/

#Python #FreeThreaded #GitHub #GitHubActions #CI #testing

The mobile #CI space is plateauing, and we might be on the verge of a DevX innovation in mobile tooling. Let me explain why.

Climate change nightmare, tech edition: #CI workflow using #Nix on #Gentoo to fine-tune a #JVM implementation of a #blockchain-enabled #LLM.

Thanks for inspiration, @faassen!

Climate change nightmare, tech edition: #CI workflow using #Nix on #Gentoo to fine-tune a #JVM implementation of a #blockchain-enabled #LLM.

Thanks for inspiration, @faassen!

"I’ll tell you… You need to share the illusion that you provide more than what you really do, and hope that the years of investing in vendor-locking will prevent companies from leaving you. Ehem, Mobile DevOps. But this model is falling apart. It’s a matter of time. And we’ll see more companies iterating on the idea that they are a CI company. Give it some time…"

#Swift #CI #iOSDev
https://pepicrft.me/blog/2025/02/24/ci-is-commoditizing

“Mobile DevOps? Free Automation Ops is better. It’s free because it gives organizations the freedom to choose and move across services with minimal costs.”
#automation #ci
https://pepicrft.me/blog/2024/09/08/ci-narrow-waist