#woodpeckerci — Public Fediverse posts

🚨 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

🚨 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

🚨 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

🚨 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

🚨 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

OK that took the whole morning, mostly getting the ingress controller to correctly serve #tls (I didn't realise that in addition to setting the host names and cert secret, I also needed to ensure that each named server has an explicit rules block otherwise nginx uses the catch-all rules and doesn't apply TLS).

So now, when I push my #gnustepweb app to main, #woodpeckerCI builds and pushes to #quayio and #argoCD pulls and deploys the app in my prod cluster.

OK that took the whole morning, mostly getting the ingress controller to correctly serve #tls (I didn't realise that in addition to setting the host names and cert secret, I also needed to ensure that each named server has an explicit rules block otherwise nginx uses the catch-all rules and doesn't apply TLS).

So now, when I push my #gnustepweb app to main, #woodpeckerCI builds and pushes to #quayio and #argoCD pulls and deploys the app in my prod cluster.

OK that took the whole morning, mostly getting the ingress controller to correctly serve #tls (I didn't realise that in addition to setting the host names and cert secret, I also needed to ensure that each named server has an explicit rules block otherwise nginx uses the catch-all rules and doesn't apply TLS).

So now, when I push my #gnustepweb app to main, #woodpeckerCI builds and pushes to #quayio and #argoCD pulls and deploys the app in my prod cluster.

OK that took the whole morning, mostly getting the ingress controller to correctly serve #tls (I didn't realise that in addition to setting the host names and cert secret, I also needed to ensure that each named server has an explicit rules block otherwise nginx uses the catch-all rules and doesn't apply TLS).

So now, when I push my #gnustepweb app to main, #woodpeckerCI builds and pushes to #quayio and #argoCD pulls and deploys the app in my prod cluster.

OK that took the whole morning, mostly getting the ingress controller to correctly serve #tls (I didn't realise that in addition to setting the host names and cert secret, I also needed to ensure that each named server has an explicit rules block otherwise nginx uses the catch-all rules and doesn't apply TLS).

So now, when I push my #gnustepweb app to main, #woodpeckerCI builds and pushes to #quayio and #argoCD pulls and deploys the app in my prod cluster.

We want to know if we have windows user and if it would be worth having our released binarys signed.

( https://github.com/woodpecker-ci/woodpecker/issues/6551 )

#survey #UserSurvey #WoodpeckerCI #Windows

Introducing Chilly Willy Agent!

It provisions a private Woodpecker CI agent on Hetzner Cloud:

- IPv6-only by default (NAT66, optional DNS64 for IPv4-only upstreams)
- Fedora CoreOS + Podman runtime
- ./chilly-willy-agent wrapper plus make targets, all hitting the Hetzner Cloud API via curl
- Image-pin enforcement, optional firewall, multi-agent

Built primarily for Codeberg CI. Apache 2.0 licensed.

https://codeberg.org/head1328/chilly-willy-agent

#OpenSource #Codeberg #WoodpeckerCI #FedoraCoreOS #Podman #SelfHosting

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

New blog post: https://blog.mei-home.net/posts/smokeweb-db-ci/

This one has a bit of Golang programming (still not sure about programming posts - I don't think I'm particularly good at writing them) and some CI setup for database testing of a Golang app in Woodpecker CI.

Special thanks go to @louis for preventing me from going on a sidequest switching my entire CI system.

#Blog #Golang #WoodpeckerCI #HomeLab

The next #release (3.14.0) takes it's time ... now we are confident and made our final #rc (https://github.com/woodpecker-ci/woodpecker/releases/tag/v3.14.0-rc.2)

please test it, so we can catch regressions if any exist ;)

#test #cicd #WoodpeckerCI

RE: https://social.treehouse.systems/@whitequark/116454915873481567

Anyone publishing a Quarto blog with Codeberg Pages? I'm new to this automation stuff, and can't decide between WebHooks, Forgejo Actions, and WoodPecker CI. If I use actions or WoodPecker, it would be just for "quarto render"; any R code output is frozen and will be run on my own computer. I have a custom domain.

#QuartoPub #CodebergPages #GitPages #ForgejoActions #WoodPeckerCI

Finally done. I can now run database tests for my Go app in Woodpecker with a real Postgres DB. So finally back to coding now.

Also: I think it is rather beneficial for my career as a CI engineer that nobody can see my Makefile and CI setup.

#WoodpeckerCI

What an extremely successful afternoon. After finding a bug in Woodpecker, creating a failing UT for it and reporting it, I've now got a fixed version of Woodpecker pushed to my Harbor instance and already confirmed that it now accepts the previously problematic pipeline Yaml.

Next one is going to be to actually make my UTs speak to the database service in the CI pipeline.

#WoodpeckerCI #HomeLab

I was able to write a UT which reproduces the bug and created an issue for Woodpecker: https://github.com/woodpecker-ci/woodpecker/issues/6493

Now onto digging into the Woodpecker build process and trying to build a version with a higher max recursion depth and testing that in my cluster.

#WoodpeckerCI

Task for today: Figuring out if I've found a Woodpecker bug. Yesterday, @louis provided me with a solution for my RWO pipeline volume problem, but for some reason the Woodpecker YAML parser chockes on the necessary yaml. I think that's due to an arbitrary recursion depth in the yaml helper lib.

So today, I will try to get a UT going and try to verify the bug, then report it, and then see whether I can work around it.

#WoodpeckerCI

So what to do instead? I'm not sure yet. But I do speak Go these days, so I will at least have a casual look at it to see how difficult it would be to implement the ability to disable the shared mount for services.

#WoodpeckerCI

Hm, it seems that what I'd like to do is not really possible. This Q&A indicates that not mounting the shared volume isn't currently an option: https://github.com/woodpecker-ci/woodpecker/discussions/5312

So my only other option would be to switch from RBD PVCs to CephFS. Which I don't want to do, because that can only be done centrally for the entire Woodpecker instance, not per-repo. Which would be problematic for my OCI container builds, because overlayFS doesn't like running on CephFS.

#WoodpeckerCI #k8s

Hm, good news and bad news. First the good ones: Woodpecker's k8s backend does support services which run in parallel with the CI pipeline. The service gets launched in its own Pod, and seems to even be getting a k8s Service.

But the downside, in my setup specifically: It tries to mount the shared pipeline volume. Which means that I can either run the service or the CI jobs, but not both - because my pipeline volume is RWO, not RWX.

#WoodpeckerCI #k8s #HomeLab

Obligatory computering on Deutsche Bahn trains picture. Today's goal is to set up a service running Postgres in my Woodpecker CI, so that I can run tests needing a database for my Smokeweb app.

#DeutscheBahn #trains #WoodpeckerCI #HomeLab

I'm currently working on adding some FreeBSD support to my crazytrace program.
I rely heavily on Codeberg's Woodpecker CI - unfortunately, however, this CI doesn't support FreeBSD.
But BoxyBSD was kind enough to provide me with a second VM, where a FreeBSD Woodpecker agent is now running, giving me a private FreeBSD CI for my projects.
It seems to be working very well.

https://codeberg.org/Codeberg-CI/feedback/issues/297
https://ci.codeberg.org/repos/13147/pipeline/313/3
https://codeberg.org/mark22k/crazytrace/src/commit/a28170353e40918f7a64c6a00e1a91adad70ea22/.woodpecker/build-freebsd.yaml

#FreeBSD #Programming #Codeberg #BoxyBSD #WoodpeckerCI

We made an #prerelease !

https://github.com/woodpecker-ci/woodpecker/releases/tag/v3.14.0-rc.0

please #test so we can catch regressions.

We are looking forward releasing it, as it will make woodpecker even more robust, get new features in and overall had a lot of #bugfixing.

#WoodpeckerCI #cicd #foss

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

Short post on using Go caches for builds in Woodpecker CI: https://blog.mei-home.net/posts/go-build-caches-in-woodpecker/

#Golang #WoodpeckerCI

First result: Reduced the build time for (sequential) ARM+x86_64 builds from about two minutes to 25 seconds by adding a go build cache.

And the module cache also works nicely.

Left for tomorrow: Coming up with some nice idea for cleanup jobs. Perhaps just a check on the PVC's utilization and nuking the caches entirely at e.g. >90%? It doesn't look like there's cache cleanup like in CCache, sadly.

#Golang #WoodpeckerCI

Sometimes, I wish I was anything else than a CI/Build engineer in my $dayjob. Because then I might be able to run an entire programming project without setting up an entire CI for a small, purely private project.

Above thought triggered by me now looking into configuring a Woodpecker CI job to mount a volume for storage of a Go build cache to speed up my build jobs. Of a ~250 line project. 🤦

#Golang #WoodpeckerCI

Yesterday was the "Digital Independence Day", which I only learned of, today. Coincidentally yesterday I wrote my first blog post in years! I used to be on wordpress.com for nearly a decade, then moved my blogging to #g+ #facebook, #linkedin and co.

With the process of shutting down all my #ustech and #bigtech accounts, I felt the need of having a place to myself again, where I could share my thoughts. For now, I've decided to use #zola as a static site generator, which gets hosted to @Codeberg

Here's my successful "Hello, world!" that'll allow me to further my journey towards #digitalindependence as this static site will not only replace my old blogging software, but I plan to replace with it so much more! What a fitting coincidence, to have that post see the light of day on the Digital Independence Day :)

https://pygospa.codeberg.page/posts/hello-world

#zola #wordpresscom #codeberg #woodpeckerci #digitalindependenceday #newblog #newbie #introduction #blogosphere #staticsite #staticsitegenerator #unplugTrump

Yesterday was the "Digital Independence Day", which I only learned of, today. Coincidentally yesterday I wrote my first blog post in years! I used to be on wordpress.com for nearly a decade, then moved my blogging to #g+ #facebook, #linkedin and co.

With the process of shutting down all my #ustech and #bigtech accounts, I felt the need of having a place to myself again, where I could share my thoughts. For now, I've decided to use #zola as a static site generator, which gets hosted to @Codeberg

Here's my successful "Hello, world!" that'll allow me to further my journey towards #digitalindependence as this static site will not only replace my old blogging software, but I plan to replace with it so much more! What a fitting coincidence, to have that post see the light of day on the Digital Independence Day :)

https://pygospa.codeberg.page/posts/hello-world

#zola #wordpresscom #codeberg #woodpeckerci #digitalindependenceday #newblog #newbie #introduction #blogosphere #staticsite #staticsitegenerator #unplugTrump

It works! I can push a commit to my #11ty website, and it'll build, upload an artifact to Codeberg, send a webhook back to my #selfHosted server, and get deployed. Using #woodpeckerCI and webhookd, and a bash script. Now it's a public repo, so I don't have to set up authentication for the webhook. Maybe that's next, but I should work on the website first.

HUGO is great. My blog switched from html+css to @gohugoio #hugo its so easy now.
Hosted on #codeberg @Codeberg and @WoodpeckerCI #WoodpeckerCI

https://mooontxt.codeberg.page/

I'll hold a #WoodpeckerCI User #meetup at the #unconference #fosdem .

Feel free to come, just chat ask questions.
You don't have to know much about CI/CD but if it's even better ;)

https://fosdem.org/2026/schedule/event/ENDASS-woodpeckerci_user_meetup/

Installed #forgejo on my #freebsd server now what ? #woodpeckerci I am looking at you !

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 🛠️

Ich sollte meinen CorpoStack (bzw. neuer Name wird vermutlich KMU!Suite) mal flott machen, dass ich ihn zum nächsten Digital Independence Day präsentieren kann.
im Anhang ein Screenshot. Ich schreibe hier mal die alternativen hin:

- Jira + Confluence -> #OpenProject
- Github + GH-Actions -> #forgejo + #WoodpeckerCI
- Outlook -> #Mailcow and #Sogomail
- Slack -> #Tuwunel + #CinnyApp
- Zoom -> #Jitsi
- Chrome Passwörter ->#Vaulwarden
- Google Drive -> #Nextcloud (mit OnlyOffice ) + Paperless-NGX + #Etherpad
(Etherpad ist eigentlich nur drin, weil Jitsi und Nextcloud nicht so gehen, wie ich es wollte.

Dann noch #Keycloack um Nutzer zu verwalten und #EspoCRM für Kunden. Achja und natürlich #Dashy für das Dashboard.

#DigitalIndependenceDay #DIDay #Element #Bitwarden

Ich sollte meinen CorpoStack (bzw. neuer Name wird vermutlich KMU!Suite) mal flott machen, dass ich ihn zum nächsten Digital Independence Day präsentieren kann.
im Anhang ein Screenshot. Ich schreibe hier mal die alternativen hin:

- Jira + Confluence -> #OpenProject
- Github + GH-Actions -> #forgejo + #WoodpeckerCI
- Outlook -> #Mailcow and #Sogomail
- Slack -> #Tuwunel + #CinnyApp
- Zoom -> #Jitsi
- Chrome Passwörter ->#Vaulwarden
- Google Drive -> #Nextcloud (mit OnlyOffice ) + Paperless-NGX + #Etherpad
(Etherpad ist eigentlich nur drin, weil Jitsi und Nextcloud nicht so gehen, wie ich es wollte.

Dann noch #Keycloack um Nutzer zu verwalten und #EspoCRM für Kunden. Achja und natürlich #Dashy für das Dashboard.

#DigitalIndependenceDay #DIDay #Element #Bitwarden

Ja ja klar, so ein git Repo mal zu #codeberg umziehen ist kein großer Akt - aber wie sieht es mit dem #CI #CD dort so aus?

Wie sind da so eure (guten) Erfahrungen? 🙂

#woodpeckerCI ist für mich noch unbekannt, aber ich denke nicht, dass es grundsätzlich andere Dinge tun wird als (selfhosted) #gitlab # github oder #azuredevops - oder?

Oder fahrt ihr besser mit Codeberg und eigener CI-Infrastruktur? Und wenn, wie sieht die aus?

...nur noch 4x schlafen bis zum kommenden #did #dut :)

Ja ja klar, so ein git Repo mal zu #codeberg umziehen ist kein großer Akt - aber wie sieht es mit dem #CI #CD dort so aus?

Wie sind da so eure (guten) Erfahrungen? 🙂

#woodpeckerCI ist für mich noch unbekannt, aber ich denke nicht, dass es grundsätzlich andere Dinge tun wird als (selfhosted) #gitlab # github oder #azuredevops - oder?

Oder fahrt ihr besser mit Codeberg und eigener CI-Infrastruktur? Und wenn, wie sieht die aus?

...nur noch 4x schlafen bis zum kommenden #did #dut :)

Ja ja klar, so ein git Repo mal zu #codeberg umziehen ist kein großer Akt - aber wie sieht es mit dem #CI #CD dort so aus?

Wie sind da so eure (guten) Erfahrungen? 🙂

#woodpeckerCI ist für mich noch unbekannt, aber ich denke nicht, dass es grundsätzlich andere Dinge tun wird als (selfhosted) #gitlab # github oder #azuredevops - oder?

Oder fahrt ihr besser mit Codeberg und eigener CI-Infrastruktur? Und wenn, wie sieht die aus?

...nur noch 4x schlafen bis zum kommenden #did #dut :)

Ja ja klar, so ein git Repo mal zu #codeberg umziehen ist kein großer Akt - aber wie sieht es mit dem #CI #CD dort so aus?

Wie sind da so eure (guten) Erfahrungen? 🙂

#woodpeckerCI ist für mich noch unbekannt, aber ich denke nicht, dass es grundsätzlich andere Dinge tun wird als (selfhosted) #gitlab # github oder #azuredevops - oder?

Oder fahrt ihr besser mit Codeberg und eigener CI-Infrastruktur? Und wenn, wie sieht die aus?

...nur noch 4x schlafen bis zum kommenden #did #dut :)

Ja ja klar, so ein git Repo mal zu #codeberg umziehen ist kein großer Akt - aber wie sieht es mit dem #CI #CD dort so aus?

Wie sind da so eure (guten) Erfahrungen? 🙂

#woodpeckerCI ist für mich noch unbekannt, aber ich denke nicht, dass es grundsätzlich andere Dinge tun wird als (selfhosted) #gitlab # github oder #azuredevops - oder?

Oder fahrt ihr besser mit Codeberg und eigener CI-Infrastruktur? Und wenn, wie sieht die aus?

...nur noch 4x schlafen bis zum kommenden #did #dut :)

Our hosted #ForgejoActions now have a `medium` runner available with 10 minutes timeout. Take a look at the announcement: https://codeberg.org/actions/meta/issues/3#issuecomment-8339199

Hosted Forgejo Actions is our second hosted CI/CD next to the existing #WoodpeckerCI which already has more generous limits.

(2/3) For those curious about the technical side: we are using #MkDocs to build the website inside #WoodpeckerCI on #Codeberg and push the resulting HTML to #Grebedoc.

We want to thank all the developers of these tools and we want to thank @Codeberg and @whitequark for the hosting of code and website.

As always in this #FOSS world: we build on the work of others to get much further much faster than we could have gone alone and we are so grateful for the FOSS community for making this possible!

WoodpeckerCI v3.11.0 is here! 🎉 Configure repo-specific config extensions, enjoy smoother logs, paginated repos & teams, and enhanced Bitbucket build status. Plus, bug fixes & docs updates for a better experience! 🚀 #WoodpeckerCI #release #DevOps #CI_CD

New blog post: https://blog.mei-home.net/posts/improving-container-image-build-perf-with-buildah/

I describe how I reduced runtimes of my container image builds, using buildah and not doing emulation via BuildKit anymore.

#HomeLab #WoodpeckerCI #buildah #blog

So in short: Running buildah builds for amd64+arm64 on a CephFS RBD backed by an SSD pool sequentially with the OverlayFS driver is faster than running the same build, on CephFS backed by HDDs with the VFS driver, with the arm64 and amd64 builds running in parallel.

#HomeLab #WoodpeckerCI #buildah