Compare AppVeyor and Travis CI 
- Users report that AppVeyor excels in its deployment-ready staging feature, with a score of 8.8, making it particularly appealing for teams looking for seamless integration into their deployment pipelines.
- Reviewers mention that Travis CI shines in its integration capabilities, scoring 9.4, which is highly valued by users who need to connect with various third-party services and tools effortlessly.
- G2 users highlight that AppVeyor's automation features are robust, scoring an impressive 9.8, which allows for efficient continuous integration and delivery processes, streamlining workflows significantly.
- Users on G2 indicate that Travis CI offers superior extensibility with a score of 9.4, allowing developers to customize their CI/CD processes extensively, which is crucial for complex projects.
- Reviewers say that AppVeyor's ease of setup, rated at 8.1, is a bit lower compared to Travis CI's 9.0, suggesting that while AppVeyor is powerful, it may require more initial configuration to get started.
- Users report that both platforms have strong support, but AppVeyor's quality of support is slightly higher at 8.4 compared to Travis CI's 8.3, indicating a marginally better experience when seeking assistance.
- 1 private project
- 1 concurrent job
- Super-fast build environment
- Up to 13,000 build minutes per user/per month
- Unlimited repositories
- Unlimited collaborators
I love that I do not have to maintain the build servers. Once our build configuration was set up, I could just forget about it, and it just works. Aside from that, support is great--fast, and helpful. It is also great to have that peace of mind about the...
The setup / configuration of a project is complex. We generally have .NET applications so using the MS Build process works well for those. We haven't yet configured a Node application successfully and are still relying on deployment using GitHub hooks....
I like most the Github integration part of Travis CI. When you have an existing Github (either open source or closed source) project, it can work seamlessly with the existing structure and integrates on 1-click without almost any effort on your part. The...
The service has been very intermittent in the last couple of months and that affects our development workflow.
I love that I do not have to maintain the build servers. Once our build configuration was set up, I could just forget about it, and it just works. Aside from that, support is great--fast, and helpful. It is also great to have that peace of mind about the...
I like most the Github integration part of Travis CI. When you have an existing Github (either open source or closed source) project, it can work seamlessly with the existing structure and integrates on 1-click without almost any effort on your part. The...
The setup / configuration of a project is complex. We generally have .NET applications so using the MS Build process works well for those. We haven't yet configured a Node application successfully and are still relying on deployment using GitHub hooks....
The service has been very intermittent in the last couple of months and that affects our development workflow.
