Bazel vs JFrog Artifactory

Overview

Bazel

Stacks314

Followers579

Votes133

JFrog Artifactory

Stacks342

Followers374

Votes0

Bazel vs JFrog Artifactory: What are the differences?

Introduction

Bazel and JFrog Artifactory are two popular tools in the software development industry that serve different purposes. Bazel is a build system developed by Google to build and test software projects, while JFrog Artifactory is a universal repository manager that supports multiple package formats and provides artifact management capabilities.

Build System vs Repository Manager: The key difference between Bazel and JFrog Artifactory lies in their primary functions. Bazel is primarily a build system, which means it helps in compiling, testing, and packaging software projects efficiently. On the other hand, JFrog Artifactory is a repository manager that acts as a central hub for storing and managing artifacts, including libraries, binaries, and container images.
Build Performance: Bazel is known for its fast and incremental build performance. It uses a distributed caching mechanism and intelligent build graph analysis to only rebuild the necessary parts of a project, resulting in significant time savings. In contrast, JFrog Artifactory focuses more on storing and managing artifacts, and its performance is not directly related to the build process.
Language and Platform Support: Bazel supports a wide range of programming languages and platforms, including popular languages like Java, C++, Python, and Go. It can handle complex dependency management, generate build rules automatically, and provides a consistent build experience across different languages. JFrog Artifactory, on the other hand, supports multiple package formats and can integrate with various development ecosystems and tools. It is not limited to specific programming languages or platforms.
Artifact Management Features: While Bazel does have some artifact management capabilities, its main focus is on building and testing. JFrog Artifactory, being a repository manager, offers advanced artifact management features like version control, metadata management, access control, and vulnerability scanning. It provides a comprehensive solution for managing the entire lifecycle of artifacts.
Integration with CI/CD Pipelines: Bazel integrates well with continuous integration and deployment (CI/CD) pipelines. It can be seamlessly integrated with platforms like Jenkins or GitHub Actions to automate the build and test processes. JFrog Artifactory also supports integration with CI/CD tools but primarily as a repository manager, allowing for artifact deployment and management within the pipelines.
Community and Support: Bazel has a strong open-source community and is actively maintained by Google. It benefits from continuous improvements and updates contributed by a large developer base. JFrog Artifactory also has a vibrant community and offers commercial support options for enterprise customers. It has been in the market for a longer time and has established itself as a reliable solution for artifact management.

In summary, Bazel is a powerful build system focused on efficient software compilation and testing, while JFrog Artifactory is a versatile repository manager that excels in artifact management and version control. Both tools have their unique strengths and are designed to serve different purposes in the software development lifecycle.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Bazel, JFrog Artifactory

tutulbuet

May 6, 2020

Needs adviceon

Java

GitHub

JFrog Artifactory

Whenever Qualys scan finds out software vulnerability, say for example Java SDK or any software version that has a potential vulnerability, we search the web to find out the solution and usually install a later version or patch downloading from the web. The problem is, as we are downloading it from web and there are a number of servers where we patch and as an ultimate outcome different people downloads different version and so forth. So I want to create a repository for such binaries so that we use the same patch for all servers.

When I was thinking about the repo, obviously first thought came as GitHub.. But then I realized, it is for code version control and collaboration, not for the packaged software. The other option I am thinking is JFrog Artifactory which stores the binaries and the package software.

What is your recommendation?

258k views258k

Comments

Detailed Comparison

Bazel	JFrog Artifactory
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google's software, and thus it has been designed to handle build problems present in Google's development environment.	It integrates with your existing ecosystem supporting end-to-end binary management that overcomes the complexity of working with different software package management systems, and provides consistency to your CI/CD workflow.
Multi-language support: Bazel supports Java, Objective-C and C++ out of the box, and can be extended to support arbitrary programming languages;High-level build language: Projects are described in the BUILD language, a concise text format that describes a project as sets of small interconnected libraries, binaries and tests. By contrast, with tools like Make you have to describe individual files and compiler invocations;Multi-platform support: The same tool and the same BUILD files can be used to build software for different architectures, and even different platforms. At Google, we use Bazel to build both server applications running on systems in our data centers and client apps running on mobile phones;Reproducibility: In BUILD files, each library, test, and binary must specify its direct dependencies completely. Bazel uses this dependency information to know what must be rebuilt when you make changes to a source file, and which tasks can run in parallel. This means that all builds are incremental and will always produce the same result;Scalable: Bazel can handle large builds	-
Statistics
Stacks 314	Stacks 342
Followers 579	Followers 374
Votes 133	Votes 0
Pros & Cons
Pros 28 Fast 20 Deterministic incremental builds 17 Correct 16 Multi-language 14 Enforces declared inputs/outputs Cons 3 No Windows Support 2 Bad IntelliJ support 1 Constant breaking changes 1 Lack of Documentation 1 Learning Curve	No community feedback yet
Integrations
Java Objective-C C++	Debian npm

What are some alternatives to Bazel, JFrog Artifactory?

GitHub

GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

Bitbucket

Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.

GitLab

GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.

Apache Maven

Maven allows a project to build using its project object model (POM) and a set of plugins that are shared by all projects using Maven, providing a uniform build system. Once you familiarize yourself with how one Maven project builds you automatically know how all Maven projects build saving you immense amounts of time when trying to navigate many projects.

Gradle

Gradle is a build tool with a focus on build automation and support for multi-language development. If you are building, testing, publishing, and deploying software on any platform, Gradle offers a flexible model that can support the entire development lifecycle from compiling and packaging code to publishing web sites.

RhodeCode

RhodeCode provides centralized control over distributed code repositories. Developers get code review tools and custom APIs that work in Mercurial, Git & SVN. Firms get unified security and user control so that their CTOs can sleep at night

AWS CodeCommit

CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools.

Gogs

The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows.

Gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD. It published under the MIT license.

Upsource

Upsource summarizes recent changes in your repository, showing commit messages, authors, quick diffs, links to detailed diff views and associated code reviews. A commit graph helps visualize the history of commits, branches and merges in your repository.

Related Comparisons

Bazel vs JFrog Artifactory: What are the differences?

Introduction

Build System vs Repository Manager: The key difference between Bazel and JFrog Artifactory lies in their primary functions. Bazel is primarily a build system, which means it helps in compiling, testing, and packaging software projects efficiently. On the other hand, JFrog Artifactory is a repository manager that acts as a central hub for storing and managing artifacts, including libraries, binaries, and container images.
Build Performance: Bazel is known for its fast and incremental build performance. It uses a distributed caching mechanism and intelligent build graph analysis to only rebuild the necessary parts of a project, resulting in significant time savings. In contrast, JFrog Artifactory focuses more on storing and managing artifacts, and its performance is not directly related to the build process.
Language and Platform Support: Bazel supports a wide range of programming languages and platforms, including popular languages like Java, C++, Python, and Go. It can handle complex dependency management, generate build rules automatically, and provides a consistent build experience across different languages. JFrog Artifactory, on the other hand, supports multiple package formats and can integrate with various development ecosystems and tools. It is not limited to specific programming languages or platforms.
Artifact Management Features: While Bazel does have some artifact management capabilities, its main focus is on building and testing. JFrog Artifactory, being a repository manager, offers advanced artifact management features like version control, metadata management, access control, and vulnerability scanning. It provides a comprehensive solution for managing the entire lifecycle of artifacts.
Integration with CI/CD Pipelines: Bazel integrates well with continuous integration and deployment (CI/CD) pipelines. It can be seamlessly integrated with platforms like Jenkins or GitHub Actions to automate the build and test processes. JFrog Artifactory also supports integration with CI/CD tools but primarily as a repository manager, allowing for artifact deployment and management within the pipelines.
Community and Support: Bazel has a strong open-source community and is actively maintained by Google. It benefits from continuous improvements and updates contributed by a large developer base. JFrog Artifactory also has a vibrant community and offers commercial support options for enterprise customers. It has been in the market for a longer time and has established itself as a reliable solution for artifact management.

Bazel vs JFrog Artifactory

Overview

Bazel vs JFrog Artifactory: What are the differences?