Concourse VS woodpecker

Compare Concourse vs woodpecker and see what are their differences.

woodpecker

Woodpecker is a simple yet powerful CI/CD engine with great extensibility. (by laszlocph)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Concourse woodpecker
46 54
7,141 3,588
0.7% 5.1%
9.1 9.9
7 days ago 4 days ago
Go Go
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Concourse

Posts with mentions or reviews of Concourse. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-03.
  • The worst thing about Jenkins is that it works
    12 projects | news.ycombinator.com | 3 Dec 2023
  • Show HN: Togomak – declarative pipeline orchestrator based on HCL and Terraform
    12 projects | news.ycombinator.com | 24 Oct 2023
  • GitHub Actions could be so much better
    21 projects | news.ycombinator.com | 22 Sep 2023
    > Why bother, when Dagger caches everything automatically?

    The fear with needing to run `npm ci` (or better, `pnpm install`) before running dagger is on the amount of time required to get this step to run. Sure, in the early days, trying out toy examples, when the only dependencies are from dagger upstream, very little time at all. But what happens when I start pulling more and more dependencies from the Node ecosystem to build the Dagger pipeline? Your documentation includes examples like pulling in `@google-cloud/run` as a dependency: https://docs.dagger.io/620941/github-google-cloud#step-3-cre... and similar for Azure: https://docs.dagger.io/620301/azure-pipelines-container-inst... . The more dependencies brought in - the longer `npm ci` is going to take on GitHub Actions. And it's pretty predictable that, in a complicated pipeline, the list of dependencies is going to get pretty big - at least a dependency per infrastructure provider we use, plus inevitably all the random Node dependencies that work their way into any Node project, like eslint, dotenv, prettier, testing dependencies... I think I have a reasonable fear that `npm ci` just for the Dagger pipeline will hit multiple minutes, and then developers who expect linting and similar short-run jobs to finish within 30 seconds are going to wonder why they're dealing with this overhead.

    It's worth noting that one of Concourse's problems was, even with webhooks setup for GitHub to notify Concourse to begin a build, Concourse's design required it to dump the contents of the webhook and query the GitHub API for the same information (whether there were new commits) before starting a pipeline and cloning the repository (see: https://github.com/concourse/concourse/issues/2240 ). And that was for a CI/CD system where, for all YAML's faults, for sure one of its strengths is that it doesn't require running `npm ci`, with all its associated slowness. So please take it on faith that, if even a relatively small source of latency like that was felt in Concourse, for sure the latency from running `npm ci` will be felt, and Dagger's users (DevOps) will be put in an uncomfortable place where they need to defend the choice of Dagger from their users (developers) who go home and build a toy example on AlternateCI which runs what they need much faster.

    > I will concede that Dagger’s clustering capabilities are not great yet

    Herein my argument. It's not that I'm not convinced that building pipelines in a general-purpose programming language is a better approach compared to YAML, it's that building pipelines is tightly coupled with the infrastructure that runs the pipelines. One aspect of that is scaling up compute to meet the requirements dictated by the pipeline. But another aspect is that `npm ci` should not be run before submitting the pipeline code to Dagger, but after submitting the pipeline code to Dagger. Dagger should be responsible for running `npm ci`, just like Concourse was responsible for doing all the interpolation of the `((var))` syntax (i.e. you didn't need to run some kind of templating before submitting the YAML to Concourse). If Dagger is responsible for running `npm ci` (really, `pnpm install`), then it can maintain its own local pnpm store / pipeline dependency caching, which would be much faster, and overcome any shortcomings in the caching system of GitHub Actions or whatever else is triggering it.

  • We built the fastest CI in the world. It failed
    11 projects | news.ycombinator.com | 12 Sep 2023
    > Imagine you live in a world where no part of the build has to repeat unless the changes actually impacted it. A world in which all builds happened with automatic parallelism. A world in which you could reproduce very reliably any part of the build on your laptop.

    That sounds similar to https://concourse-ci.org/

    I quite like it, but it never seemed to gain traction outside of Cloud Foundry.

  • What are some good self-hosted CI/CD tools where pipeline steps run in docker containers?
    4 projects | /r/devops | 14 May 2023
    +1 to GitLab on-prem. If that is too heavy just for the CI/CD, there are a bunch of tools, e.g. https://github.com/concourse/concourse
    4 projects | /r/devops | 14 May 2023
    Concourse: https://concourse-ci.org
  • JSON vs XML
    5 projects | /r/programming | 6 Apr 2023
  • Choosing a CI/CD tool for your product
    4 projects | /r/devops | 26 Feb 2023
  • Why I joined Dagger
    3 projects | dev.to | 6 Feb 2023
    My first attempt was Concourse, a CI/CD system that scheduled pipelines written in declarative YAML. Choosing YAML for Concourse made it for all, but it was definitely not once; we had to constantly rework its declarative model to handle more use cases. As time went on I started to wonder if the final frontier was actually a “language for CI/CD.”
  • Elm 2022, a year in review
    15 projects | dev.to | 30 Jan 2023
    Ableton ⬩ Acima ⬩ ACKO ⬩ ActiveState ⬩ Adrima ⬩ AJR International ⬩ Alma ⬩ Astrosat ⬩ Ava ⬩ Avetta ⬩ Azara ⬩ Barmenia ⬩ Basiq ⬩ Beautiful Destinations ⬩ BEC Systems ⬩ Bekk ⬩ Bellroy ⬩ Bendyworks ⬩ Bernoulli Finance ⬩ Blue Fog Training ⬩ BravoTran ⬩ Brilliant ⬩ Budapest School ⬩ Buildr ⬩ Cachix ⬩ CalculoJuridico ⬩ CareRev ⬩ CARFAX ⬩ Caribou ⬩ carwow ⬩ CBANC ⬩ CircuitHub ⬩ CN Group CZ ⬩ CoinTracking ⬩ Concourse CI ⬩ Consensys ⬩ Cornell Tech ⬩ Corvus ⬩ Crowdstrike ⬩ Culture Amp ⬩ Day One ⬩ Deepgram ⬩ diesdas.digital ⬩ Dividat ⬩ Driebit ⬩ Drip ⬩ Emirates ⬩ eSpark ⬩ EXR ⬩ Featurespace ⬩ Field 33 ⬩ Fission ⬩ Flint ⬩ Folq ⬩ Ford ⬩ Forsikring ⬩ Foxhound Systems ⬩ Futurice ⬩ FörsäkringsGirot ⬩ Generative ⬩ Genesys ⬩ Geora ⬩ Gizra ⬩ GWI ⬩ HAMBS ⬩ Hatch ⬩ Hearken ⬩ hello RSE ⬩ HubTran ⬩ IBM ⬩ Idein ⬩ Illuminate ⬩ Improbable ⬩ Innovation through understanding ⬩ Insurello ⬩ iwantmyname ⬩ jambit ⬩ Jobvite ⬩ KOVnet ⬩ Kulkul ⬩ Logistically ⬩ Luko ⬩ Metronome Growth Systems ⬩ Microsoft ⬩ MidwayUSA ⬩ Mimo ⬩ Mind Gym ⬩ MindGym ⬩ Next DLP ⬩ NLX ⬩ Nomalab ⬩ Nomi ⬩ NoRedInk ⬩ Novabench ⬩ NZ Herald ⬩ Permutive ⬩ Phrase ⬩ PINATA ⬩ PinMeTo ⬩ Pivotal Tracker ⬩ PowerReviews ⬩ Practle ⬩ Prima ⬩ Rakuten ⬩ Roompact ⬩ SAVR ⬩ Scoville ⬩ Scrive ⬩ Scrivito ⬩ Serenytics ⬩ Smallbrooks ⬩ Snapview ⬩ SoPost ⬩ Splink ⬩ Spottt ⬩ Stax ⬩ Stowga ⬩ StructionSite ⬩ Studyplus For School ⬩ Symbaloo ⬩ Talend ⬩ Tallink & Silja Line ⬩ Test Double ⬩ thoughtbot ⬩ Travel Perk ⬩ TruQu ⬩ TWave ⬩ Tyler ⬩ Uncover ⬩ Unison ⬩ Veeva ⬩ Vendr ⬩ Verity ⬩ Vnator ⬩ Vy ⬩ W&W Interaction Solutions ⬩ Watermark ⬩ Webbhuset ⬩ Wejoinin ⬩ Zalora ⬩ ZEIT.IO ⬩ Zettle

woodpecker

Posts with mentions or reviews of woodpecker. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-03.
  • The worst thing about Jenkins is that it works
    12 projects | news.ycombinator.com | 3 Dec 2023
    12 projects | news.ycombinator.com | 3 Dec 2023
  • GitHub: “Human eyes” will never see the contents of your private repositories
    6 projects | news.ycombinator.com | 23 Jun 2023
    > I wish it had some sort of CI like github actions or bitbucket pipeline

    I use Gitea with Drone CI and it works pretty well: https://www.drone.io/

    Some might also prefer the Woodpecker CI fork due to the license: https://woodpecker-ci.org/

    I setup Drone as a part of my migration away from GitLab Omnibus and have no complaints so far: https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-...

  • What self-hosted Git server ?
    4 projects | /r/selfhosted | 25 May 2023
    https://woodpecker-ci.org/ Open source clone of drone.io
  • GitHub actions top alternatives
    3 projects | /r/devops | 10 May 2023
    https://www.drone.io/ or the more open fork https://woodpecker-ci.org/
    3 projects | /r/devops | 10 May 2023
  • Codeberg – Fast Open Source Alternative to GitHub
    9 projects | news.ycombinator.com | 7 Apr 2023
    I’m trying to migrate of my personal repos from GitHub to Codeberg. The biggest problem is to find a replacement for GitHub Actions (the free offering is so generous), and my current solution for that is to self-host an instance of Woodpecker CI [1].

    I’d like to see even more diversity in Git hosting beyond “let’s all migrate from X to Y”, and for that to happen, Forgejo (a soft fork of Gitea) has already began implementing federation [2].

    [1]: http://woodpecker-ci.org/

  • JSON vs XML
    5 projects | /r/programming | 6 Apr 2023
    The open source version of drone is https://woodpecker-ci.org/
  • Can any Hetzner user, please explain there workflow on Hetzner?
    20 projects | news.ycombinator.com | 22 Mar 2023
    I use Hetzner, Contabo, Time4VPS and other platforms in pretty much the same way (as IaaS VPS providers on top of which I run software, as opposed to SaaS/PaaS), but here's a quick glance at how I do things.

    > deploy from source repo? Terraform?

    Personally, I use Gitea for my repos and Drone CI for CI/CD.

    Gitea: https://gitea.io/en-us/

    Drone CI: https://www.drone.io/

    Some might prefer Woodpecker due to licensing: https://woodpecker-ci.org/ but honestly most solutions out there are okay, even Jenkins.

    Then I have some sort of a container cluster on the servers, so I can easily deploy things: I still like Docker Swarm (projects like CapRover might be nice to look at as well), though many might enjoy the likes of K3s or K0s more (lightweight Kubernetes clusters).

    Docker Swarm: https://docs.docker.com/engine/swarm/ (uses the Compose spec for manifests)

    K3s: https://k3s.io/

    K0s: https://k0sproject.io/ though MicroK8s and others are also okay.

    I also like having something like Portainer to have a GUI to manage the clusters: https://www.portainer.io/ for Kubernetes Rancher might offer more features, but will have a higher footprint

    It even supports webhooks, so I can do a POST request at the end of a CI run and the cluster will automatically pull and launch the latest tagged version of my apps: https://docs.portainer.io/user/docker/services/webhooks

    > keep software up to date? ex: Postgres, OS

    I build my own base container images and rebuild them (with recent package versions) on a regular basis, which is automatically scheduled: https://blog.kronis.dev/articles/using-ubuntu-as-the-base-fo...

    Drone CI makes this easy to have happen in the background, as long as I don't update across major versions, or Maven decides to release a new version and remove their old version .tar.gz archives from the downloads site for some reason, breaking my builds and making me update the URL: https://docs.drone.io/cron/

    Some images like databases etc. I just proxy to my Nexus instance, version upgrades are relatively painless most of the time, at least as long as I've set up the persistent data directories correctly.

    > do load balancing? built-in load balancer?

    This is a bit more tricky. I use Apache2 with mod_md to get Let's Encrypt certificates and Docker Swarm networking for directing the incoming traffic across the services: https://blog.kronis.dev/tutorials/how-and-why-to-use-apache-...

    Some might prefer Caddy, which is another great web server with automatic HTTPS: https://caddyserver.com/ but the Apache modules do pretty much everything I need and the performance has never actually been too bad for my needs. Up until now, applications themselves have always been the bottleneck, actually working on a blog post about comparing some web servers in real world circumstances.

    However, making things a bit more failure resilient might involve just paying Hetzner (in this case) to give you a load balancer: https://www.hetzner.com/cloud/load-balancer which will make everything less painless once you need to scale.

    Why? Because doing round robin DNS with the ACME certificate directory accessible and synchronized across multiple servers is a nuisance, although servers like Caddy attempt to get this working: https://caddyserver.com/docs/automatic-https#storage You could also get DNS-01 challenges working, but that needs even more work and integration with setting up TXT records. Even if you have multiple servers for resiliency, not all clients would try all of the IP addresses if one of the servers is down, although browsers should: https://webmasters.stackexchange.com/a/12704

    So if you care about HTTPS certificates and want to do it yourself with multiple servers having the same hostname, you'll either need to get DNS-01 working, do some messing around with shared directories (which may or may not actually work), or will just need to get a regular commercial cert that you'd manually propagate to all of the web servers.

    From there on out it should be a regular reverse proxy setup, in my case Docker Swarm takes care of the service discovery (hostnames that I can access).

    > handle scaling? Terraform?

    None, I manually provision how many nodes I need, mostly because I'm too broke to hand over my wallet to automation.

    They have an API that you or someone else could probably hook up: https://docs.hetzner.cloud/

    > automate backups? ex: databases, storage. Do you use provided backups and snapshots?

    I use bind mounts for all of my containers for persistent storage, so the data is accessible on the host directly.

    Then I use something like BackupPC to connect to those servers (SSH/rsync) and pull data to my own backup node, which then compresses and deduplicates the data: https://backuppc.github.io/backuppc/

    It was a pain to setup, but it works really well and has saved my hide dozens of times. Some might enjoy Bacula more: https://www.bacula.org/

    > maintain security? built-in firewall and DDoS protection?

    I personally use Apache2 with ModSecurity and the OWASP ruleset, to act as a lightweight WAF: https://owasp.org/www-project-modsecurity-core-rule-set/

    You might want to just cave in and go with Cloudflare for the most part, though: https://www.cloudflare.com/waf/

  • Gitea 1.19.0
    2 projects | /r/programming | 20 Mar 2023

What are some alternatives?

When comparing Concourse and woodpecker you can also consider the following projects:

drone - Gitness is an Open Source developer platform with Source Control management, Continuous Integration and Continuous Delivery. [Moved to: https://github.com/harness/gitness]

Jenkins - Jenkins automation server

gitlab-runner

GitlabCi

github-act-runner - act as self-hosted runner

Jenkins - A static site for the Jenkins automation server

Buildbot - Python-based continuous integration testing framework; your pull requests are more than welcome!

Laminar - Fast and lightweight Continuous Integration

onedev - Git Server with CI/CD, Kanban, and Packages. Seamless integration. Unparalleled experience.

Go - Main repository for GoCD - Continuous Delivery server