LogoLogo
What's New?Connect Agent ReleasesBook a DemoPricing
  • Documentation
  • Developers
  • Administration
  • OVERVIEW
    • JFrog Connect Overview
      • Architecture Overview
        • Connect Agent
        • Connect & JFrog Platform
      • Plan Your Update Strategy
        • Software Update Objectives & Concepts
        • Software Update Process & Procedures
  • Get Started
    • Create JFrog Connect Account
    • Log in to JFrog Connect
    • Network Requirements
    • Register Device
  • Manage your Fleet
    • Register Devices at Scale
      • Freeze Image on Device
      • Build Image with Agent
    • Register & Update Device at Once
    • Organize Your Fleet
      • Create Project
      • Move Device between Projects
      • Create Groups
        • Add Device to Group
        • Add Many Devices to Group
        • Change Group Name
        • Delete Group
      • Tag Devices
        • Remove a Tag
      • Remove Many Devices
  • Devices
    • Fleet Overview
      • Filter Devices
      • Locate Devices
    • Device Details
      • Delete a Device
      • Block Updates with Update Trigger
    • Update Connect Agent
    • Delete Many Devices
  • Deployment
    • Create Update Flow
      • Actions
        • Run Command
        • Run Script
        • Deploy File
        • Deploy Docker
          • Use Docker Image
          • Use Docker Compose
          • Get Artifactory Parameters
        • Clone Git Repository
        • Download Artifact
          • Get Artifactory Path
        • Download Release Bundle
          • Get Artifactory Parameters for Release Bundle
        • Update Image
        • Install Debian Package
          • Get Artifactory Parameters for Debian
      • Use Update Parameters
      • On Failure & Rollback
      • Vulnerability Scans
      • Sample Use Case: Build Update Flow for Reuse
    • Deploy Software
      • Set Application & Version
      • Set Alert upon Failure
      • Set Phased Rollout
      • View Deployment Progress
        • Detailed Deployment Information
        • Abort a Deployment
      • Deploy in Groups
      • Sample Use Case: Deploy Docker Images to Devices
  • Tools
    • Remote Tools
      • Use Terminal
      • Open Port Tunnel Session
        • Access with VNC
        • Connect with SSH
        • Access Device Web Applications
      • Run Commands Remotely
        • Run Command as Non-Root User
      • Get Device Files (Fetch Files)
    • Alerts
      • Create Channel
      • Set Webhook
    • Monitor
      • Resource Monitor
      • Process Monitor
  • Releases
    • What's New?
    • Connect Agent Release Notes
  • Troubleshooting
    • Connect Server Status
    • Troubleshoot Topics
      • Device Registration
      • Terminal Troubleshooting
Powered by GitBook
On this page
  • Prerequisites
  • Drag the Action
  • Configure the Action
  • On Failure and Rollback
  • Free Memory Requirement
  • What’s Next?

Was this helpful?

Export as PDF
  1. Deployment
  2. Create Update Flow
  3. Actions

Clone Git Repository

The Clone Git Repository action enables you to pull your latest software version from a Git repository directly to your edge devices.

PreviousGet Artifactory ParametersNextDownload Artifact

Last updated 3 months ago

Was this helpful?

Connect's Update Flow enables your edge devices to clone from a Git repository whether you are using a public Git repository or your own private repository for your code.

When you use the Clone Git Repository action, the edge devices will use the git clone command to pull your Git repo.

Prerequisites

  • JFrog Connect account.

Drag the Action

To include the Clone Git Repository action in your update flow, do the following:

  1. Go to Deployment in the left menu and click Create Update Flow.

  2. Drag the Clone Git Repository action and drop it in the workflow.

Configure the Action

Click the action to open and configure it.

  1. Enter a name for the action.

  1. Git Repository URL: Enter the URL of the Git, for example, https://github.com/jfrog-connect/app-repo.git.

  2. Device Destination Path: Enter the path where the Git will be installed on the device, for example, /home/user/App.

Tip: The folder on the device must exist beforehand. Otherwise, the update will fail. Connect does not automatically create folders when deploying updates. You can create a folder using the Run Command action.

  1. Configure your On Failure policy and instructions for rolling back, if necessary.

  2. Save your action configuration.

On Failure and Rollback

  • Continue Update Flow: If the Clone Git Repository action fails, Connect will simply continue with the next action in the update workflow.

  • Run General Rollback: The action and the entire update workflow are rolled back.

As a general precaution, Connect Agent creates a backup of the relevant device folder in a temporary location. If a rollback is required, the agent restores the folder to its initial state.

Free Memory Requirement

To enable Rollback functionality, your device's free memory must be greater than the update size. Use the relationship below to calculate the amount of free memory required.

Free Memory Required > Current Folder Size + Update Size + 10MB

What’s Next?

Private Git: Mark this checkbox only if you are using a private Git repository. Choose the account where your repository exists. If the account is not in the list, you can add it according to the procedure in .

For your policy, choose one of the actions for Connect to do in case the Clone Git Repository action fails.

Learn more about configuring your policy and instructions for rolling back.

Add Private Git
On Failure
On Failure
GitHub account