Please VS Artifactory

Please Reviews

Artifactory Reviews

Please mentions (11)

• Top programming languages created in the 2010's on GitHub by stars

  I’m not sure a JS library qualifies as a PL. Or automation software (SoftStack). Or an API description language. Or a build system. Source: over 1 year ago

• Just Use a Monorepo

  Regarding your first point, a good alternative to Bazel is [Please][https://please.build/] - its build graph can solve exactly this problem in CI. - Source: Hacker News / over 1 year ago

• Need to know about various distributed build tools available

  Checkout: https://please.build/ - CMake is not directly supported, but you can easily extend please.build to invoke cmake commands to build your targets. - It does supports both Windows(ehweee) and Linux - MIT - BONUS: it is fast. Really fast(||)! Single binary. It is also versatile. I am using it to build a repo with multiple programming languages(C++(Wasm),Go,Js, Flutter), while spinning up vagrant and... Source: over 1 year ago

• When to Use Bazel?

  > the best way forward is to take the ideas of Bazel (hermetic and deterministic builds) and package them as a good small build system, perhaps even compatible with Bazel so you don't have to rewrite build rules all the time. How does https://please.build measure up? - Source: Hacker News / over 1 year ago

• I'm building an experimental successor to Bazel™

  Good luck! I assume you are aware of please.build? Source: over 1 year ago

Artifactory mentions (20)

• Where to store executables shared by a team/project

  I kind of hate it, but Artifactory seems popular at companies: https://jfrog.com/artifactory/. Source: 10 months ago

• Adding Virtual Environments to Git Repo

  When not providing all dependencies yourself, you might suffer from people deleting the packages you depend on (IMHO a very rare scenario). If it is really that critical (hint: usually it isn't), create a local mirror of Pypi (full or only the packages you need). Devpi, Artifactory, etc. Can do that or you just dump the necessary files into Cloud storage, so you have a backup. Source: about 1 year ago

• Authenticated Docker Hub image pulls in Kubernetes

  Operate a pull-through cache registry, like Artifactory or the open source reference Docker registry. This will allow you to pull images from Docker Hub less frequently, improving your chances of staying under the anonymous usage limit. - Source: dev.to / about 1 year ago

• Concretely, how do you trust the experts? That is, how do you a) identify experts relevant to something and b) determine if they have a consensus (and if so, what it is) on a given topic?

  Like suppose for a second that . . . Idk . . . a product team wants our ci workflows to start using Artifactory. Okay great, I don't know Artifactory integration but I'm going to tell them "Sure, I'll get right on that.". Source: about 1 year ago

• What do I do with large "asset" files?

  If these "assets" have an independent release schedule I would treat them separately (especially if they are externally provided). If they are not built from source then treat them as artefacts, they don't belong in git. You can store the in an artefact repository (like Artifactory of Nexus) or (as u/nekokattt points out) in something like S3. Source: over 1 year ago