What users are saying about

Apache Maven

38 Ratings

CircleCI

28 Ratings

Apache Maven

38 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 7.7 out of 101

CircleCI

28 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.1 out of 101

Add comparison

Likelihood to Recommend

Apache Maven

Building and automating packaging of software can be a challenging task. As the complexity of the project grows so do the dependencies on third-party artifacts. Using Maven we can define and manage the project structure centrally and it helps improve overall build times.
No photo available

CircleCI

CircleCI is an excellent tool for generic CI/CD. It integrates well with GitHub, runs your tests, and gives you the ability to deploy when your tests succeed on a certain branch. It doesn't really offer anything more sophisticated than that, I've seen CI tools that will actually try to bisect test failures for you, CircleCI will definitely not do anything that sophisticated. But it executes well on the relatively simple (at least from a customer perspective) use case of running tests on every commit and executing special hooks when they succeed.
Valeri Karpov profile photo

Pros

  • Apache Maven uses a simple hierarchical structure for building and packing a software artifact.
  • Different configurations of the software can be used while working on the dev server as opposed to a live production environment. This makes testing the application very easy.
heather collins profile photo
  • Full customization and scripting abilities. Using tools like bash scripts, SSH, and Node, running almost anything upon committing some code to GitHub becomes possible.
  • Integration with all of our favorite services. GitHub and Slack in particular are crucial to our business and CircleCI's integration is seamless and full-featured.
  • Great config file syntax. Many CI services require you to perform advanced configuration in a UI. This is fine at first (and CircleCI offers this for many options available), but when you start needing to manage a large number of projects, committing configuration changes to a Git repository is more consistent and maintainable than making the change many different times manually in a UI.
Ben McClure profile photo

Cons

  • One of the issues with building software using Apache Maven is that its cache resolution is not optimal. It pulls down all the artifacts onto the developer's local machine and can sometimes result in conflicts.
  • The build process can vary in time and gets progressively longer as the project's complexity increases.
heather collins profile photo
  • It would be nice if you could configure everything via the YML file. Some things are only available via YML, and some things are actually only available in the UI, and many other things have full overlap between the two. I'm sure there are good reasons for this, but this is a pretty confusing situation. For example, certain PHP versions are only available on certain Ubuntu releases. Configuring the PHP version is done via the .yml file, but configuring the Ubuntu release being used for the build has to be done in the UI. This can easily lead to things not building properly.
Ben McClure profile photo

Alternatives Considered

heather collins profile photo
Travis has full YML configuration in areas where CircleCI is slightly lacking still, which is great, but CircleCI offers more features, settings, and potential performance.Codeship is simpler to use, you can use it entirely from their UI without modifying your Git repository at all. To some, this is important, existing Git repos need to be supported without adding files to them.For others, and this is our situation, the opposite holds true--we'd rather keep our testing and deployment configuration along with our code in Git than managed somewhere separate. I believe this is a better approach in the long-term, especially when managing a large number of projects.It also means most of our team members don't need to be in the CircleCI interface at all, possibly ever. They get added to the team, someone turns deployments on in CircleCI for the project, and then everyone can collaborate on making changes to the configuration, relying on Git's excellent merging abilities, rather than having multiple people potentially in the UI modifying configuration simultaneously, potentially reverting each others' changes.
Ben McClure profile photo

Return on Investment

  • The tool has greatly improved our overall software build times and had a positive impact on our release schedules.
  • Being a free application from an Open Source Community, there was no upfront investment needed on our part.
heather collins profile photo
  • Since the adoption of Circle CI, we have seen a great improvement in our automation testing and regression analysis of the software.
  • Overall, it has resulted in a marked improvement in our software quality standards.
No photo available

Pricing Details

Apache Maven

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details

CircleCI

General
Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No
Additional Pricing Details