#WoodpeckerCI is so cool. It took some finagling, but I've finally got it set up. I have it linked to my #Codeberg, with an arm64 and amd64 agent. The whole setup, including all agents, is running in podman containers (though pipeline steps still need to talk to Docker, because podman's docker socket support didn't work correctly.

I'm really happy about this. My first foray into self-hosted CI, and it's pretty great. It looks good and is pretty fast. Excited to start testing the limits.

**v1.0.2** got released, please update, it contains a security fix

#release #security #WoodpeckerCI #update

Presenting Woodpecker 1.0.0

https://woodpecker-ci.org/blog/release-v1.0.0

#release #WoodpeckerCI #blog #boost #SelfHosting #selfHosted #FOSS

Today marks an awesome milestone!

Our v1.0.0 just got #released out into the wild.
Catch it if you can ... and play around, it got a ton of improvements over our old versions.

Also please #boost so everybody notice it.

#WoodpeckerCI #cicd #release #SelfHosting #awesome #coding #ci #cd

https://github.com/woodpecker-ci/woodpecker/releases/tag/v1.0.0

@WoodpeckerCI
Depends on time and topic.
But in general yes, if remote.
@kielux @opensourcetage

#workshop #talk #WoodpeckerCI #community #topics

@determinatesystems
We should try to translate it to #CodeBerg or #WoodpeckerCI actions to make it available for really free git forges.

#nix #github

Even got automatic build of Jekyll blog with #WoodpeckerCI , thanks @0xMRTT for help with setting it up!

What about #CI on #Codeberg?

We are providing access to our #WoodpeckerCI instance to those who need it, some caveats still apply.

Also, you can read about the upcoming #ForgejoActions.

Check out our docs to learn more about the state of CI on Codeberg: https://docs.codeberg.org/ci/

if you use **next** - please either update asap or apply this pull:

https://github.com/woodpecker-ci/woodpecker/pull/1890

#security #alert #WoodpeckerCI #update #SelfHosting

Well if you use the 'next' tag/branch be aware!!!

We renamed 'pipeline:' keyword to 'steps:' to match our terminology

PS: old pipelines will still work

#cicd #woodpecker #WoodpeckerCI

Another milestone on my self hosting journey: last week I installed WoodpeckerCI to complement my Forgejo intance (a gitea fork). And this week I automatically published my first rust crates to https://crates.io from this CI pipeline.

These past few weeks were very productive.
#GeekLife #SelfHosting #WoodpeckerCi #RustLang (vdx.hu s/hJol)

por fin resolví un antiquísimo problema que tenía con el flujo de #gitlabci para #tiempoRs .

Y no-lo-se-rick creo que la intefaz que ofrece #gitlab para configurar el #ci es propensa a los malentendidos y las confusiones.

Ya voy a probar #woodpeckerCi para de una vez migrar todo a #codeberg

@WoodpeckerCI

i finished the polish language of #Woodpeckerci

https://translate.woodpecker-ci.org/projects/woodpecker-ci/ui/pl/

I've been experiemtning with #WoodpeckerCI last night and I like it. Although it looks like quite some way to go before I can think about using it in production.
I'm having issues with looking through huge build logs (output of a maven multi module project)
And I guess I need to find some tool to create nice error reports from JUnit xml.

What I like is the old Unix philosophy of "one tool does one job and does it well"

Ich habe Woodpecker CI ausprobiert und was darüber geschrieben:

https://pwa.io/articles/installing-woodpecker-in-your-homelab/

#woodpecker #woodpeckerci #ci #dev #webdev

Codeberg provides #Git hosting to more than 50.000 users, and more than 300 users rely on our hosted #WoodpeckerCI.

Thanks to your donations and contributions, the dream of a libre software forge is reality. Thank you a lot!

Learn how you can help: https://docs.codeberg.org/improving-codeberg/

That took a frustrating amount of time to get my https://d.moonfire.us and https://fedran.com working on Woodpecker CI again (for the first time for Fedran's). I ended up removing the built-in clone Git plugin and switched to doing it via an Alpine image. (I got the "cannot enter user name" bug I get periodically and never found a consistent way to fix.)

Switch from SSH-based Git cloning to HTTPS. I was trying to be SSH-only because of vague hopes of eventually getting to like SourceHut (which doesn't allow HTTP-based clones).

But, I also managed to stop using my custom NixOS docker image and used nixpkgs/nix-flakes instead, though I had to jump through a couple uncomfortable hoops to make that work.

But, it's working which means, I have a now page for my blog and Fedran should poke Antenna on Gemini when I post new chapters.

( #Fedran #NixOS #WoodpeckerCI #Gemini )

Does anyone use Woodpecker CI here? I'm currently still on Drone CI and currently planning to move over, gut I have a problem: I can't seem to find any info on whether Woodpecker also has Drone's Jsonnet support? I find that quite nice and use it e.g. in for my Docker CI, where I have a jsonnet function defined for creating and pushing the images, and then use it for all my local Homelab containers. Without jsonnet, I would need to do a lot of copy and paste.

#HomeLab #WoodpeckerCI

Did you know, #WoodpeckerCI does have #localization ?

If your #language is not there jet or not finished, just start #translating and if it is just a few words. https://translate.woodpecker-ci.org/

If you love #selfhosting and #ansible you should check out this project: https://github.com/mother-of-all-self-hosting/mash-playbook

We try to put as many services as we can into one playbook. To enable a service you often only need to put in 1-3 variables. It is less than a week old and we already have quite a few services integrated, from #nextcloud, #vaultwarden and #miniflux to #gitea or #WoodpeckerCI

Have a look!