Skip to content

QuickStart Guide - JFrog Cloud

Overview

The purpose of this guide is to easily get you started with your JFrog cloud instance.

Step 1: Login to JFrog

Login URL = https://medtronic.jfrog.io/ Use SSO login button on login page.

The steps below will introduce you to JFrog solutions that are included with Medtronic subscription:

  • JFrog Artifactory: Universal package management supporting all major packaging formats, build tools, and CI servers.
  • JFrog Xray: Open source security scanning and license compliance enabling DevSecOps and ensuring application security throughout your SDLC.
  • JFrog CLI: Compact client, developed to enhance and simplify command line interactions with JFrog products. JFrog CLI commands will deploy, resolve and upload multiple artifacts in parallel.

Step 2: JFrog Repository Management

The JFrog Platform hosts the following repository types:

  • Local (physical repository)
  • Remote (physical repository)
  • Virtual (An aggregation of above 2 types used to create controlled domains for search and resolution of artifacts)
  • Federated
  • Distribution (Enable fast, trusted software releases across the globe — ensuring security and overcoming limited bandwidth and network lag)
  • Release Bundle Repository

Local

Local repositories are physical, locally managed repositories into which you can deploy artifacts. Typically, these are used to deploy internal and external releases as well as development builds, but they can also be used to store binaries that are not widely available on public repositories such as 3rd party commercial components. Using local repositories, all of your internal resources can be made available from a single access point across your organization from one common URL.

Remote

Remote repositories serves as a caching proxy for a repository managed at a remote site such as ConanCenter. Artifacts are stored and updated in remote repositories according to various configuration parameters that control the caching and proxying behavior.

Virtual

A virtual repository encapsulates any number of local and remote repositories, and represents them as a unified repository accessed from a single URL. It gives you a way to manage which repositories are accessed by developers since you have the freedom to mix, match and modify the actual repositories included within the virtual repository. You can also optimize artifact resolution by defining the underlying repository order so that Artifactory will first look through local repositories, then remote repository caches, and only then Artifactory will go through the network and request the artifact directly from the remote resource. For the developer it’s simple. Just request the package, and Artifactory will safely and optimally access it according to your organization policies.

  • Most virtual repositories do not contain a [locator], and are made up of [projectkey]-[packagetype]-[environment]
  • A common use case is for an entire CRM Org to use a virtual repository that aggregates all repositories of a specific technology, such as Docker, for both resolution and read permissions
  • In general, its best practice that all consumption and writes are done through virtual repositories, as opposed to local/remote repositories
  • This is so that as many implementation details as possible can be omitted, letting the users work with a single, well-known URL

Distribution (Reach out to DevEx if you are interested in using)

JFrog Distribution enables you to speed up deployments and concurrent downloads at scale throughout your SDLC: from CI, to CD, through device management – spanning remote sites, hybrid infrastructure, clouds, edges, embedded devices, and IoT fleets.