Apache Maven vs. Google Cloud Build

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Maven
Score 9.2 out of 10
N/A
Apache Maven is an open source build automation tool.N/A
Google Cloud Build
Score 8.0 out of 10
N/A
Cloud Build is a service that executes builds on Google Cloud. Cloud Build can import source code from a variety of repositories or cloud storage spaces, execute a build to any specifications, and produce artifacts such as Docker containers or Java archives. Users can also use Cloud Build to help protect the software supply chain. Cloud Build features meet the requirements of Supply chain Levels for Software Artifacts (SLSA) level 3.N/A
Pricing
Apache MavenGoogle Cloud Build
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache MavenGoogle Cloud Build
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details
More Pricing Information
Community Pulse
Apache MavenGoogle Cloud Build
Best Alternatives
Apache MavenGoogle Cloud Build
Small Businesses
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
Enterprises
GitLab
GitLab
Score 8.7 out of 10
GitLab
GitLab
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache MavenGoogle Cloud Build
Likelihood to Recommend
9.0
(14 ratings)
-
(0 ratings)
Usability
8.0
(1 ratings)
-
(0 ratings)
Support Rating
5.1
(3 ratings)
-
(0 ratings)
User Testimonials
Apache MavenGoogle Cloud Build
Likelihood to Recommend
Apache
Maven is great if you have an application with a lot of third-party dependencies and don’t want each developer to keep track of where the dependency can be downloaded. It’s also a great way to make it easy for a new developer to be able to build the application. It’s less suitable for simple projects without any third-party dependencies.
Read full review
Google
No answers on this topic
Pros
Apache
  • If you are building in the Java ecosystem, then Maven definitely has the biggest repository of artifacts needed for such projects.
  • It has a very simple to use extendable architecture. Everything is configurable through the Pom.xml file which is very simple to follow.
Read full review
Google
No answers on this topic
Cons
Apache
  • 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
Google
No answers on this topic
Usability
Apache
The overall usability of Apache Maven is very good to us. We were able to incorporate it into our company's build process pretty quickly. We deployed it to multiple teams throughout the entire enterprise. We got good feedback from our developers stating that Apache Maven has simplified their build process. It also allowed to to standardize the build process for the entire enterprise, thus ensure that each development team is using the same, consistent process to build code.
Read full review
Google
No answers on this topic
Support Rating
Apache
I can't speak to the support, as I've never had issues. Apache Maven "just works," and errors were user errors or local nexus errors. Apache Maven is a great build/dependency management tool. I give it a 9/10 because occasionally the error message don't immediately indicate a solution...but again, those errors were always user or configuration errors, and the Maven documentation is extensive, so I don't find fault in Maven, but in its users.
Read full review
Google
No answers on this topic
Alternatives Considered
Apache
Ant, Maven's opposing framework, is often a point of comparison. Although Ant does not require formal conventions, it is procedural in the sense that you must tell Ant exactly what to do and when. It also lacks a lifecycle, along with goal definition and dependencies. Maven, on the other hand, requires less work as it knows exactly where your source code is as long as the pom.xml file is generated.
Read full review
Google
No answers on this topic
Return on Investment
Apache
  • It was very handy to roll out organization level frameworks to be used by diverse departments and business
  • Consistent build artifacts enabling smooth release cycles, thereby enabling to adhere to release calendars and feature rollouts
  • Reduced 80 man hours of work every release cycle
Read full review
Google
No answers on this topic
ScreenShots