GitKraken Reviews

Artifactory Reviews

GitKraken mentions (3)

• The Terrible UX of Git (2021)

  The Git CLI is terrifying and awful. It's far too easy to clobber your own work -- and that of others -- when the whole point of it was to prevent that. While you still need to really deeply understand several git concepts to use it, GitKraken[0] is the best GUI tool I've used in daily practice. It integrates well with git hosts and has an attractive and mostly comprehensible interface. Accordingly, it isn't free... - Source: Hacker News / over 1 year ago

• Beautiful and crazy ways to see git-log?

  I like GitKraken partially because it was originally loosely based on the look/feel of Guitar Hero. Source: about 2 years ago

• How I became a Software Developer - 5 Years Later

  This experience was also invaluable because I had a walking fountain of knowledge sitting next to me and was really cool about answering my questions and pointing out all code style errors in countless PR reviews. I cannot count the amount of times he had to explain me the whole rebase workflow. What really helped me improve my Git knowledge was GitKraken and other similar tools. - Source: dev.to / about 2 years 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: 11 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: over 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