Artifactory VS Dependabot

Artifactory Reviews

Dependabot Reviews

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

Dependabot mentions (13)

• Be Secure and Compliant with GitHub

  GitHub integrated security scanning for vulnerabilities in their repositories. When they find a vulnerability that is solved in a newer version, they file a Pull Request with the suggested fix. This is done by a tool called Dependabot. - Source: dev.to / almost 2 years ago

• How to configure Dependabot with Gradle

  Dependabot provides a way to keep your dependencies up to date. Depending on the configuration, it checks your dependency files for outdated dependencies and opens PRs individually. Then based on requirement PRs can be reviewed and merged. - Source: dev.to / over 2 years ago

• Yarn.lock: how it works and what you risk without maintaining yarn dependencies — deep dive

  The first approach we looked at was Dependabot - a well-known tool for bumping dependencies. It checks for possible updates, opens Pull Requests with them, and allow users to review and merge (if you're confident enough with your test suite you can even set auto-merge). - Source: dev.to / over 2 years ago

• 5 tools to automate your development

  Dependabot is dead simple and their punchline clearly states what it does. We started using it a couple of years back, a bit before Github acquired it. - Source: dev.to / almost 3 years ago

• Keeping dependencies up-to-date in Composer

  The most known tool for this is Dependabot. Dependabot integrates seemlessly into Github and is able to create pull requests for outdated dependencies. If you have set up automated tests on your codebase all you have to do is merge the pull request created by Dependabot. It does not get any easier. - Source: dev.to / almost 3 years ago