@WoodpeckerCI@floss.social
🚀 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@floss.social
🚀 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
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@hongminhee@hollo.social
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:
@bart@floss.social
Looking into alternate #CI systems this weekend. Cirrus CI looks neat. https://garden.pacia.tech/cirrus_ci_is_the_best.html
@pedro@mastodon.pepicrft.me
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/
@pedro@mastodon.pepicrft.me
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/
@lig@fosstodon.org
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
@lig@fosstodon.org
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
@WoodpeckerCI@floss.social
🚀 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
@pedro@mastodon.pepicrft.me
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
@orhun@fosstodon.org
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
@orhun@fosstodon.org
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
@gnome@floss.social
🧪 "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.
@kevinveenbirkenbach@microblog.veen.world
🚀 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! 🤝✨
@smallcircles@social.coop · Reply to Librecast's post
Congratulations on the release, #Librecast team! 🎉
It is a very exciting #multicast use case you are driving lcagent with, and I am looking forward to learn more about your experiences with this #CI setup.
Thank you, for all the hard work!
@daniel@masto.doserver.top
Status update: I'm now automatically building and releasing a signed fork of stable moshidon with my patches. #CI is cool!
@hugovk@mastodon.social
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/
@hugovk@mastodon.social
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/
@hugovk@mastodon.social
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/
@hugovk@mastodon.social
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/
@pedro@mastodon.pepicrft.me
The mobile #CI space is plateauing, and we might be on the verge of a DevX innovation in mobile tooling. Let me explain why.
@jonn@social.doma.dev
@jonn@social.doma.dev
@pedro@mastodon.pepicrft.me
"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
@u03c1@bzh.social · Reply to nixCraft 🐧's post
How many projects or CI stacks, critical or not, in production or not, rely on some Dockerfile starting with "FROM alpine:xxx" ?
https://alpinelinux.org/posts/Seeking-Support-After-Equinix-Metal-Sunsets.html
#alpinelinux #docker #CI #dev #webdev #saas #programming #devops
@u03c1@bzh.social · Reply to nixCraft 🐧's post
How many projects or CI stacks, critical or not, in production or not, rely on some Dockerfile starting with "FROM alpine:xxx" ?
https://alpinelinux.org/posts/Seeking-Support-After-Equinix-Metal-Sunsets.html
#alpinelinux #docker #CI #dev #webdev #saas #programming #devops
@feagults@kmy.blue
@unspeaker@mastodon.social
shout out to @Codeberg for launching #CodebergActions #CI
after some fiddling with that base image to use, i decided to go with #nixos/#nix
and so, my #diy #tui #daw now has a green check https://codeberg.org/unspeaker/tek/actions/runs/690/jobs/0
now, to figure out nix and #cargo caching...
@arichtman@eigenmagic.net
What are folk's approaches to integration testing against cloud stuff?
For example we have an Enterprise Application as an IdP in Azure
Do you usually mock it out? Have a long-lived nonprod instance? Terraform spin up and tear down?
#AWS #Cloud #Testing #DevOps #IntegrationTesting #PlatformEngineering #CICD #CI #ContinuousIntegration
@pedro@mastodon.pepicrft.me
“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
