Using the latest JFrog products?
JFrog Platform User Guide

JFrog Mission Control 3.x Documentation
To get the latest version, go to the JFrog Unified Platform

Skip to end of metadata
Go to start of metadata


In addition to storing and managing  configuration scripts in an internal database, Mission Control also lets you synchronize them to a version control systems allow versioning, sharing and collaboration on scripts as well as allowing you to create scripts using any editor you prefer. Currently, the only VCS system supported is Git. 

This section describes how to configure Mission Control to manage configuration scripts in a Git repository.

Page Contents

Configuring Git Integration

To configure Mission Control to access the Git repository where you host your configuration scripts, in the Admin module, select Scripts | Version Control.

You can access your Git account using your username and password or via SSH.

Using SSH to access your Git account?

When using SSH to access your Git account, you don’t need to enter your username and password.

Note also that your keys must to be under the ~/.ssh folder of the machine on which Mission Control is running.

Check Enable Git and fill in the details of the integration.

Remote URL

URL to the Git repository where scripts will be hosted. You may only work with the master branch and it must exist before being configured in Mission Control. You may access the Git repository via SSH, and in this case, the User Name and Password fields may remain empty.

User Name
A valid Git user with pull and push permissions.
Password for the Git account. This only needs to be provided when initially enabling Git integration, or if the password was updated.

When set, scripts can be developed externally to Mission Control (in the user’s IDE), then pushed to Remote URL and loaded into Mission Control.

Note that empty scripts do not get synchronized to your Git repository.

Restore scripts from repository
When set, scripts are loaded from the Git repository to Mission Control immediately after the configuration is saved.

  • No labels