一千萬個為什麽

搜索

JFrog Artifactory還是JFrog Bintray,何時使用其中一個?



我們實際上正在為我們的項目尋找一個包裹管理系統。 目標很簡單,有一個集中系統來保留我們的軟件包(應用程序和中間件),並將它們用於我們的CI/CD工具(Jenkins,Ansible,Docker ...)

尋找我發現的選項 JFrog ArtifactoryJFrog Bintray 。他們似乎都做了同樣的工作,但我不相信JFrog正在維護兩個具有相同選項的並發產品。

Artifactory和Bintray有什麽不同?
我們如何選擇一個,為什麽?

轉載註明原文: JFrog Artifactory還是JFrog Bintray,何時使用其中一個?

一共有 1 個回答:

JFrog Artifactory and JFrog Bintray both manage binaries (and any other file type you can think of). I'd like to see them as two different parts of your CI/CD pipeline.

Artifactory is mostly meant to be used inside the organization. For managing all binaries coming in as dependencies (like maven central jars) and being produced by your build process (like your pack.rpm or org/pack-docker docker image). These can later be used by others in the org or released to Bintray.

Bintray is meant to provide a universal distribution platform for your end deliverables. For example, the pack.rpm you want to be available for your customers to download. And also that org/pack-docker docker image.

查看每一個的功能列表,看看他們有何不同,以便最好地匹配他們的預期角色。

我希望這有助於解釋差異。

Disclosure: I work at JFrog