5 Best Practices for GoLang CI/CD

For developers programming in long-established languages like Java, JavaScript or Python, the best way to build continuous integration and continuous delivery (CI/CD) workflows with Artifactory is pretty familiar. A mature set of dependency management systems for those languages and container solutions like Docker provide a clear roadmap. But if you’re programming your applications in GoLang, … Continued

Helm

Steering Straight with Helm Charts Best Practices

Kubernetes, the popular orchestration tool for container applications, is named for the Greek word for “pilot,” or the one who steers the ship. But as in any journey, the navigator can only be as successful as the available map. An application’s Helm chart is that map, a collection of files that can be deployed from … Continued

JFrog and K8S

[White Paper] The JFrog Journey to Kubernetes: Best Practices for Taking Your Containers All the Way to Production

Kubernetes together with JFrog Artifactory allows you to reliably and predictably deploy your applications, scale them on the fly, seamlessly roll out new features and efficiently utilize hardware resources. This white paper reviews the complexity and the challenges facing companies wanting to adopt Kubernetes as their container orchestration tool. We hope that the lessons learned, … Continued

Artifactory Backups and Disaster Recovery

Best Practices for Artifactory Backups and Disaster Recovery

Whether you have a small JFrog Artifactory instance or a complex cross-region topology, ensuring that your binaries are available at all times is vital to your DevOps pipeline. There are many different approaches to protecting your binaries from disaster, including: System backups, directly from the Artifactory UI or using a 3rd party solution such as … Continued

Infrastructure as Binaries with Chef and Artifactory: Five Best Practices

  Infrastructure as Binaries became a reality several weeks ago when we announced that Artifactory supports infrastructure management platforms such as Chef. Both we, here at JFrog, and our infrastructure champions at Chef, believe that establishing a canonical Artifactory repository for all artifacts used in a company’s infrastructure such as Ruby Gems, NuGet packages, RPMs, … Continued

4 best practices in repository configuration

1. If you are using several technologies, (e.g. Nuget, Maven, NPM, PyPi etc..) define a unique repository for each of them. By doing that you are making sure that all of the build requests are directed to the right place rather than going to a repository that may not even have the necessary packages. 2. … Continued

Beat the binary repository developer (a.k.a. User Plugins)

From our experience with thousands of Artifactory users we know one thing for sure: we don’t know better. Every organization does its ALM differently: artifact approval flow, snapshot retention policies, build-to-release flow, governance, needed metadata and much, much more – they are all different. We definitely have some ideas on how the build and deploy … Continued

Replication! What and How.

Update Jul. 24th 2012: As of version 2.6.2  Artifactory also supports event-driven replication. Benefit from all the worlds: pull/push/event-driven!Working in distributed teams isn’t easy. There are time zone differences, language and cultural differences, and… data distribution. When the data you need is away, you are miserable. So, let’s fix it. Bring your data home Let’s take binary … Continued

Go beyond Java with CI server and Artifactory

During the last couple of years, continuous integration (CI) and automated release management methodologies have become much stronger in non-Java builds.Number of familiar tools are used for these methodologies, like the version control system to manages your sources, your build tool to actually build your software from sources and  your build server, which builds your software continuously using … Continued

Dependency Management with .NET – Doing it Right

The problem of dependency management is neither new nor original, it exists in all development platforms, and .NET is no different. Let’s go through different solutions and see how they perform. I’ll list them here in no particular order. Keeping dependencies in your source control That’s a very popular solution, and for a reason. The … Continued