JFrog Connect
HomePricingDashboardRegister Now
Search…
JFrog Connect
OVERVIEW
Architecture
Getting Started
JFrog Platform
Register
Register a device
Registering devices at scale
Registering Yocto image
Create Update
Update Flow
Integrations
Upload Files
Deploy Files
Deploy Container
Git Repository
Artifacts
Release Bundle
Rollback
Update Devices
Update Deployment
Applications
Deployment Best Practice
Device Registration & Deployment
Schedule Update
Devices
Filter bar
Map / Location
Delete a device
Control Center
Remote control
Remote access
Remote commands
Monitor
Resources monitor
Processes monitor
Data monitor
Alerts
Alerts
Fetch
Fetch logs
Device security
Active
REST API
Overview
Device state
Bulk devices state
Get devices details
Change devices details
Data monitor
Deploy Update
Update Trigger
Tags
Apps
Environment
Environment variables
Running Commands as User
SETTINGS
Account
User management
Notifications
Security
Troubleshooting
Device registration
Display issue - "0.0"
Micro update
Remote control
FAQ
GENERAL TERMS OF SERVICE
Frequent questions
Service-Level Agreement
Billing
Deprecated
(Deprecated) OTA updates tools
Send Logs
Non-Linux Agent
Powered By GitBook
Git Repository
Git block allows you to pull your latest version directly from a git repository.

Overview

Connect's Update Flow allows you to pull your code directly from a git repository, whether it's a public or your own private repository, you can use the Git Repository block.
When a Git block is used, devices will utilize a git clone command to have a standardized and functional git repo.

Configuration

Git Account

Select your Git Account, if it does not exist, please follow our Git integration guidelines.

Destination Path on Device

The Device path is the directory on the device that the files will be pulled into.
The directory on the device must exist beforehand, otherwise, the update will fail.
JFrog Connect does not automatically create directories when deploying updates, you may create a folder using the "Run Command" block in the General Section.

Remote Repository URL

The intended repository URL to pull the files.
​
​
​

On Fail

Allows you to define the occurrences upon failure of the Git Repository block.
To read more about On Fail configuration, refer to the Rollback section.
Previous
Docker Compose
Next - Create Update
Artifacts
Last modified 2mo ago
Copy link
Contents
Overview
Configuration
Git Account
Destination Path on Device
Remote Repository URL
On Fail