Appveyor vs Blue Ocean: What are the differences?
Appveyor: Continuous Integration and Deployment service for busy Windows developers. AppVeyor aims to give powerful Continuous Integration and Deployment tools to every .NET developer without the hassle of setting up and maintaining their own build server; Blue Ocean: A reboot of the Jenkins CI/CD User Experience. Designed from the ground up for Jenkins Pipeline and compatible with Freestyle jobs, Blue Ocean reduces clutter and increases clarity for every member of your team.
Appveyor and Blue Ocean belong to "Continuous Integration" category of the tech stack.
Some of the features offered by Appveyor are:
- Scriptless, repetitive, one-click deployment of build artifacts to multiple environments
- YAML configuration
- Backed by Windows Azure platform
On the other hand, Blue Ocean provides the following key features:
- Sophisticated visualizations of CD pipelines, allowing for fast and intuitive comprehension of software pipeline status.
- Pipeline editor (In Development) that makes automating CD pipelines approachable by guiding the user through an intuitive and visual process to create a pipeline.
- Personalization of the Jenkins UI to suit the role-based needs of each member of the DevOps team.
"Github integration" is the primary reason why developers consider Appveyor over the competitors, whereas "Beautiful interface" was stated as the key factor in picking Blue Ocean.
Blue Ocean is an open source tool with 2.49K GitHub stars and 435 GitHub forks. Here's a link to Blue Ocean's open source repository on GitHub.
According to the StackShare community, Appveyor has a broader approval, being mentioned in 19 company stacks & 16 developers stacks; compared to Blue Ocean, which is listed in 4 company stacks and 10 developer stacks.