Apache Maven vs Travis CI

• Makes the build process simple and easy to do.
• It provides a standard build system that can be adopted by multiple, different groups within an organization.
• It's extensible with easy to use custom extensions which our developers take full advantage of.

Read full review

• It is very simple to configure a range of environment versions and settings in a simple YAML file.
• It integrates very well with Github, Bitbucket, or a private Git repo.
• The Travis CI portal beautifully shows you your history and console logs. Everything is presented in a very clear and intuitive interface.

Read full review

• Maven provides a very rigid model that makes customization tedious and sometimes impossible. While this can make it easier to understand any given Maven build, as long as you don’t have any special requirements, it also makes it unsuitable for many automation problems.
• Maven has few, built-in dependency scopes, which forces awkward module architectures in common scenarios like using test fixtures or code generation. There is no separation between unit and integration tests

Read full review

• I think they could have a cheaper personal plan. I'd love to use Travis on personal projects, but I don't want to publish them nor I can pay $69 a month for personal projects that I don't want to be open source.
• There is no interface for configuring repos on Travis CI, you have to do it via a file in the repo. This make configuration very flexible, but also makes it harder for simpler projects and for small tweaks in the configuration.

Read full review

• Apache Maven is an open source product from the Apache Software Foundation. Being free to use without any licensing constraints, we've been very happy with this product thus far.
• The software build and packaging times for our applications have improved greatly since our use of this tool.

Read full review

• It's improved my ability to deliver working code, increasing my development velocity.
• It increases confidence that your own work (and those of external contributors) does not have any obvious bugs, provided you have sufficient test coverage.
• It helps to ensure consistent standards across a team (you can integrate process elements like "go lint" and other style checks as part of your build).
• It's zero-cost for public/open source projects, so the only investment is a few minutes setting up a build configuration file (hence the return is very high).
• The .travis.yml file is a great way for onboarding new developers, since it shows how to bootstrap a build environment and run a build "from scratch".

Read full review