Need advice about which tool to choose?Ask the StackShare community!
wercker vs Github Actions: What are the differences?
What is wercker? Build, test, and deploy container-native applications. Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.
What is Github Actions? Automate your workflow from idea to production. It makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
wercker and Github Actions belong to "Continuous Integration" category of the tech stack.
Some of the features offered by wercker are:
- Pipelines - Wercker's Pipelines enable developers to fully automate builds, tests and deployments with Docker as a first class citizen.
- Workflows - With Workflows: a collection of pipelines can be chained and triggered to achieve complex automation goals.
- Steps Store - A step is a self contained best practice for accomplishing a specific automation task. Build your own or help yourself to our community based store.
On the other hand, Github Actions provides the following key features:
- Multiple workflow files support
- Free and open source
- Workflow run interface
HENNGE, heycar, and FashionUnited are some of the popular companies that use wercker, whereas Github Actions is used by Craftbase, Rainist, and Walls.io. wercker has a broader approval, being mentioned in 135 company stacks & 111 developers stacks; compared to Github Actions, which is listed in 39 company stacks and 60 developer stacks.
Pros of GitHub Actions
- Integration with GitHub8
- Free5
- Easy to duplicate a workflow3
- Ready actions in Marketplace3
- Configs stored in .github2
- Docker Support2
- Read actions in Marketplace2
- Active Development Roadmap1
- Fast1
Pros of wercker
- Automatic Deployments35
- Free33
- Easy config via yaml25
- Awesome UI23
- Github integration23
- Continuous Deployment22
- Supports both Github and Bitbucket16
- Easy to setup14
- Reliable12
- Bitbucket Integration11
- Community-driven components (boxes and steps)4
- Fast builds4
- Easy to get started4
- Docker based4
- Easy UI3
- Flexible configuration via YAML3
- Multi-target deploys2
- Trigger by branch name1
- Great UI, free and an active Slack channel :)1
- Docker support1
- Multiple configurable build steps1
Sign up to add or upvote prosMake informed product decisions
Cons of GitHub Actions
- Lacking [skip ci]5
- Lacking allow failure4
- Lacking job specific badges3
- No ssh login to servers2
- No Deployment Projects1
- No manual launch1