Need help with other JFrog products?
JFrog Enterprise+
JFrog Artifactory
JFrog Xray
JFrog Distribution
JFrog Pipelines
JFrog Bintray
JFrog Access
JFrog CLI
Released: January 17, 2019
Deprecated Version Warning
The Mission Control 3.4.0 version has been deprecated and will no longer be available to download.
This is due to an issue related to the mc.key file, that was fixed in the latest 3.4.1 version.
Released: January 23, 2019
To lower the overhead when installing and upgrading Mission Control, Mission Control 3.4 has replaced its use of MongoDB with PostgreSQL. This will also facilitate the support of additional relational database in the future.
JFrog Mission Control 3.4 introduces a highly available active-active cluster architecture, central management and monitoring your services. ensuring continuous security and governance to your software packages. This feature is available from Enterprise license onwards.
Java 11 compatibility has been added to Mission Control, as Java 8 support end of life is coming up, and Mission Control contains components that require Java to run properly and include Java runtime as part of the Mission Control.
To harden security when providing encrypted data (secrets) such as connection strings to external databases, from this version, when running Mission Control, you can optionally provide secrets in a temporary file. Mission Control will load the parameters specified in a temporary secrets file, located in jfmc.secrets.location,
at startup and then delete the file. Notice that this is an additional recommended functionality that will not change your current behavior if not used.
From Mission Control 3.4, MBeans has been deprecated.
Resolved an issue with cronjob. The rpm/deb installer now also adds a cronjob that runs every 2 minutes. The cronjob triggers a script which validates that mission-control is running as expected and in case of errors, attempts to restart the services.
Resolved an issue whereby Mission Control Docker services restarted only on failure exit code.
Resolved an issue whereby a white label error page is displayed at times when attempting to log in using SSO.
Resolved an issue whereby the `latitude` and `longitude` coordinates were not detected in the Sites table.
Resolved an issue whereby reindexing an index with big size is timing out after 30000 ms when upgrading Elasticsearch.
Resolved an installation issue in relation to writing temporary files in Docker Compose.
Resolved an issue whereby a Mission Control account was locked due to multiple POST requests.
Released: January 30, 2019
In addition to using a signed URL and connecting to JFrog Bintray, you can now upload your license buckets to JFrog Mission Control using an offline bucket file. This saves the need for Mission Control to connect to Bintray, enabling an easy configuration for users with Mission Control configured behind a firewall.
License buckets can be uploaded from the Mission Control UI and using REST API.
JFrog Mission Control can now be installed using a Docker offline installation.
Support for ElasticSearch credentials and certificates. For ElasticSearch OSS, credentials can be enabled using the Search Guard plugin.
Released: March 11, 2019
Released: November 6, 2018
Mission Control now provides a set of dedicated Access Federation APIs that allow you to set, get, and modify access federation configurations on the service level or for all services.
You can now manually install Mission Control without scripts for Debian and RPM.
From Mission 3.3, you can install Mission Control as a new installation using Docker Compose allowing you to orchestrate your setup using Docker Compose. This will ensure you have all the required services specified in a single JSON file with pre-configured parameters.
The following enhancements have been made to the Zip installation:
Released: December 12, 2018
Released: December 13, 2018
Released: October 10, 2018
Proxy management is now simplified as admins can configure and manage proxies on the Site level instead of configuring a proxy for each individual Service. This enables the right proxy to be selected based on the Site on which the Service is located. Proxy settings from previous versions are automatically migrated to reflect the existing Site pairing and the Onboarding Wizard has been modified to accommodate the need to configure a proxy for Mission Control.
Insight Projects now allows you to drill down into the build/run allowing users to see consolidated data from all the tools connected to the Project in one single location. The dashboard layout has also been enhanced to enable showing more details.
From 3.2, Service Trends has replaced the Graphs tab. You can now view a set of dedicated trends and specific data related to the JFrog services including storage and usage, vulnerabilities, and distributions.
As part of the JFrog SLA based support, you can now collect Mission Control logs in a support bundle using REST API. The logs will be pushed to Mission Control Authentication provider Artifactory and will be available for download or upload to the JFrog support site.
Access Federation has been simplified allowing you to select entity types per connection instead of per source. The wizard now lets you specify the target only for the single direction sync setup.
You can now view the Repository scan % and Build Info scan % statistics for the Xray service.
Mission Control Docker users no longer need root access to the Container.
Mission Control scripts now support Conda package type.
Released: March 8, 2019
Released: July 2, 2018
Installing Mission Control has been made easier with the availability of generic installers for RPM based systems (CentOS and Red Hat) and Debian based systems (Debian and Ubuntu). In addition, a ZIP installation is now also available for all LINUX flavors supported by Mission Control. For updates to the installation process, please refer to Installing Mission Control.
Setting up access federation has a new UI making this process easier than ever.
Mission Control now supports Elasticsearch clusters to support scaling up while maintaining performance.
Mission Control projects have been enhanced and now allow extraction of data from multiple services or builds to give insights over a wider range of services at a time including both upstream and downstream Jenkins jobs. In addition, insights can now also be obtained over any custom time range that contains data. A project can provide insights from up to 25 builds, and you can select up to 10 builds to display in the dashboard.
Artifactory Edge nodes can now be provided to Mission Control configuration scripts as user input by specifying "EDGE" as the user input type in Mission Control scripts.
The script template that sets up a Star Topology has been enhanced to include replication blocks that let you configure the parameters that govern the replication between the Artifactory services in the star topologies.
/usr/bin
. Released: August 21, 2018
Previous versions of JFrog Mission Control presented an issue with the implementation of Disaster Recover for Artifactory services (6.1 and 6.2) in which security settings (users, groups and permissions) were not properly DR protected. This release of Mission Control, together with the release of JFrog Artifactory 6.3 solves this issue with the following enhancements:
Mission Control's management of Disaster Recovery has been enhanced to use JFrog Access service in order to allow security entities (users, groups and permissions) to be synchronized from a Master Artifactory service to its corresponding Target service. Need to configure Circle of Trust functionality between Master and Target services.
This patch release of Mission Control fully supports DR for Artifactory 6.3 and above. If you are using Artifactory 6.1 or 6.2 and want to implement DR for your Artifactory services, you need to upgrade to Artifactory 6.3. Note however, that if you do not wish to implement DR, you may upgrade to this release of Mission Control without having to upgrade your Artifactory services.
Released: May 17, 2018
Announcing the new Enterprise+ Platform, that provides a complete solution for covering all the steps involved in creating a secure, trustworthy, and traceable software release in a multi-site development environment.
The solution works in conjunction with source version control, continuous integration, and deployment tools.
The JFrog Enterprise+ platform bundle includes:
JFrog Mission Control: all features available in Mission Control with the addition of:
the ability to add instances of Jenkins-CI, JFrog Distribution and JFrog Artifactory Edge as services in the system and monitor them
Insight and analytics on build processes through as set of metrics on the end to end build process
The following dedicated Enterprise+ features are a part of the Mission Control 3.0 release:
Gain Insight into Projects: Projects provide insight into your release process through a set of metrics generated from various tools including Jenkins and Artifactory. A Project can be a single microservice or a complete application and is defined using a set of builds in Artifactory. Project resources are automatically discovered from the different tools, and the data is collected and refreshed periodically resulting in a set of metrics that visualize the release process in the Project dashboard.
Distribution: The Distribution service manages Release Bundles and their distribution processes, including release content, permission levels, and target destinations. For more information, see Distribution Service.
Jenkins: The Jenkins service collects information on your builds in Jenkins and extends the view you gain in the Enterprise+ Projects Dashboard by integrating Jenkins as part of your build process in the CI/CD process. For more information, see Jenkins Service.
Managing Access Federation in Mission Control: Access Federation gives you control over access to all, or any subset of your global JFrog Artifactory, JFrog Xray, and JFrog Distribution services from one location by synchronizing all security entities (users, groups, permissions and access tokens) between the federated services. Once access federation has been set up, you can manage all security entities in the federated services from one place. For more information, see Managing Access Federation.
Access Federation is initially configured through a YAML configuration file that is uploaded to the different access Services, and the results are displayed in Mission Control in the Admin module/ Access Federation/ Configuration page. For more information, see Access Federation.
When accessing Mission Control for the first time or when doing an upgrade from Mission Control 2.x version, Mission Control launches the Onboarding Wizard that lets you go through the basic setup and configuration so you can get started immediately. The Onboarding Wizard lets you reset the admin password, create a site, add license buckets and configure the Authentication Provider. For more information, see Mission Control Onboarding Wizard.
From version 3.0, JFrog Mission Control offers a granular permissions model that provides Mission Control administrator ability to grant permission to users and groups on different resources in Mission Control. The resources include services, scripts, and projects (E+ feature). Mission Control does not keep local users and groups but assigns permissions to users and groups located on an Artifactory service configured as an Authentication Provider. For more information, see Permissions.
From Mission Control version 3.0, user management in Mission Control has been greatly simplified. By adding the ability to authenticate Mission Control users through your corporate Artifactory service. All you need to do is define a leading Artifactory service as an "Authentication Provider" in the Mission Control Onboarding Wizard. For more information, see Authentication.
SSO allows you to log into all your JFrog applications using a single set of user credentials that are stored in the Authentication Provider Artifactory instance. When SSO is applied, the user logs into the JFrog product using a set of predefined credentials and is granted access across the board to the JFrog products. SSO eliminates the need to re-enter the credentials every time a product is accessed. It is automatically enabled for all the JFrog services that use an Authentication Provider for managing security. For more information, see Authentication Using Single Sign-On.
From Mission Control 3.0, you can apply permissions to scripts. The Mission Control admin can create scripts and configure the VCS together with the ability to grant the Execute Script permission to users.
Prior to running Mission Control REST API calls you need to generate an access token. The token is valid for 60 minutes.
Supports Elasticsearch version 6.1
Following customer requests for an automated process for installing Mission Control, we have added to option to use default parameters when performing installations and upgrades.
The clean Installation:
Sets a default data folder location.
Uses internal databases (not custom databases).
When SELinux is enforced, the mongo policy package is installed without requiring user confirmation.
The upgrade process:
Skips the step whereby the user is required to confirm whether to proceed with the upgrade.
Uses the same configuration for folder locations and databases.
Removed PHP dependencies.
Docker log enhancements including fixing issues and adding log rotation for mission-control docker microservice.
API v1 and v2 were deprecated in Mission Control 2.x and are now deleted in Mission Control 3.0.
Released: May 28, 2018
Released: June 26, 2018
Fixed an issue connected to user or group names containing the "dot" (".") character.
For a Mission Control installation, click to download this latest version of JFrog Mission Control.
Released: January 8, 2018
This release introduces support for additional flavors of Linux and adds Ubuntu 16.x and and Red Hat 7.x as supported platforms. For details on how to install Mission Control on these platforms, please refer to Installing Mission Control. .
Mission Control uses Elasticsearch, MongoDB and PostgreSQL databases for its different functions, and until now, would install dedicated instances of each of these databases. This version gives you more control of your resources and lets you direct Mission Control to use instances of these databases you may already have installed and in use, rather than creating new ones. Offering full flexibility, during the installation or upgrade process, Mission Control lets you select which databases should externalized and which Mission Control should create for its own dedicated use.
In addition to the replication status, for Maven packages, the DR Repositories tab now also includes the metadata file count and size for each repository.
Mission Control now displays your general system status as an icon on the top ribbon of the UI. Services notifications are automatically updated at all times.
Released: January 23, 2018
This release adds full support in Mission Control for Helm Chart repositories which were introduced in JFrog Artifactory 5.8.
Released: November 20, 2017
This release introduces many changes from version 1.x to improve workflow and efficiency in managing your global Artifactory and Xray services. Yes, you read correctly, Mission Control now also manages your Xray services. In addition, Mission Control 2.0 introduces significant changes in installation and upgrade procedure, workflow for adding and managing services, a new concept of Sites that associate services to a geographic location, improvements in Usage Graphs and more.
Note that some of the new features and enhancements are breaking changes that are not compatible with version 1.x. In these cases, we offer a migration path to version 2.0.
For details about the changes introduced by Mission Control 2.0, please read the sections below.
In addition to managing your Enterprise Artifactory instances, Mission Control can now also manage the JFrog Xray instances attached to them. This allows you to do things like configure connections between Artifactory and Xray services, use scripts to create Watches and more.
To manage Artifactory or Xray instances through Mission Control, they must be added as Services and be assigned to Sites.
Scripting has undergone significant changes in Mission Control 2.0. Most importantly, configuration scripts are now much more flexible allowing you to operate on as many Artifactory or Xray services, and on any number of repositories as you want in a single script (previously, each script could only perform one action on a single service). To support this capability, Mission Control 2.0 introduces service closures in configuration scripts. These define the Artifactory and Xray instances on which the script operates and enclose the different configuration blocks that create or implement changes on Artifactory and Xray services.
The scripting DSL has also been significantly enhanced with new configuration blocks. These include configuration blocks to create and configure Xray services, a security block to configure users, groups and permissions in Artifactory services and more. Make sure to check out the Star Topology configuration blocks that make it very easy to set up a complex one-to-many replication relationship using three lines of code. Not also that applying a Star Topology configuration to all members of a star actually implements a full mesh topology.
Breaking Change - You need to migrate your scripts
The new scripting mechanism is a breaking change which means that scripts written for JFrog Mission Control 1.x will not work in version 2.0 and above. While there is no way to migrate your scripts automatically, the process is not very complicated. For guidelines and best practices for migrating your scripts please refer to Migrating Scripts from Version 1.x to Version 2.x.
The Graphs UI has been enhanced to give you an easy way to focus on different Artifactory instances and repositories and also zoom in on specific time periods on historical usage graphs. From version 2.0, Mission Control uses a new Elasticsearch database to store historical usage data. Upon installation of the new version, the previous InfluxDB database will no longer be used, and usage data will only be collected in the new database.
[Optional] You may migrate historical usage data from InfluxDB to Elastic Search
If you wish to continue viewing historical usage data collected in the InfluxDB database of versions 1.x, you can migrate this data to the new Elasticsearch database using the process described in Migrating Scripts from Version 1.x to Version 2.x.
Instructions for installing and upgrading to version 2.0 have changed, but remain simple procedures, with support for CentOS, Debian and Docker installations.
To install Mission Control 2.0 as CentOS or Debian distribution, please refer to Installing Mission Control.
To install and run the Mission Control Docker image, please refer to Running with Docker.
ZIP installation is deprecated
From version 2.0, Mission Control is no longer available as a ZIP installation.
Mission Control 2.0 introduces a completely new REST API that accommodates all the new functionality introduced in this version. The new REST API adds several new endpoints, but also removes some, including endpoints related to configuring users, groups and permissions in Artifactory since this functionality is now available through JFMC scripting. From Mission Control 2.0, the REST API v3 is active, while the REST API v2 is deprecated.
Breaking Change - You need to migrate your REST API calls
The new REST API is a breaking change which means any scripts that use the previous REST API version will not work. To learn how to migrate your scripts to the new REST API, please refer to Version Mappings in the new Mission Control REST API page.
Sites are a new concept in JFrog Mission Control. They represent physical locations (cities) into which you can aggregate the different Artifactory and Xray services serving them. Any service defined in Mission Control must be assigned to a site. Sites are displayed in the Explore module (which replaces the old Dashboard module) and can display sites as a list view or on a map.
Existing Artifactory services are automatically assigned to a site
When you upgrade to Mission Control 2.0, any Artifactory services already managed by your current version of Mission Control will be assigned to new Sites that will be created according to the location of your Artifactory instances. For example, an Artifactory service located in San Fransisco, will be assigned to a new site in Mission Control that's located in San Fransisco.
Artifactory services that do not have a location will be placed in the "Unassigned Services" site by default.
"Groups" feature is deprecated
From version 2.0, collecting managed Artifactory services into "Groups" is deprecated. All services should be placed in the context of a Site.
Released: August 9, 2017
clientTlsCertificate
, has been added to the Replication and Multi-push replication DSL blocks.filelist.xml
metadata file in RPM repositories, a new field, enableFileListsIndexing
, has been added to the Local Repository DSL block. Released: June 2, 2017
The Mission Control Graphs module has been updated to include a Storage and Artifact Usage graph showing the amount of storage used and number of artifacts. It allows you to get an overall view of all Artifactory instances (and their repositories) managed by Mission Control, or to focus on a specific instance and repository. This graph supports Predictions, and when enabled, it will also estimate how these figures will grow over time 3, 6, 12 and 24 months into the future.
The "Top 5 Instances (Historical)" and "Top 5 Repositories (Historical)" graphs have been removed.
Released: April 3, 2017
To prevent the InfluxDB log files from becoming inflated, Mission Control now manages them automatically using log rotation. Log rotation is currently supported for RPM and Debian installations.
The Mission Control extensions used to reconnect to Artifactory instances have been enhanced. After upgrading to this version, make sure you upload the updated extensions to Artifactory as described in Reconnecting to Managed Instances.
Released: May 14, 2017
Released: February 21, 2017
This release updates Mission Control to support the latest features released with Artifactory 5.1.
This release of Mission Control complements new features in Artifactory 5.1 by adding support for Chef and Puppet. This provides administrators with central control, management and monitoring of Chef Cookbook and Puppet repositories across all of an organizations’ worldwide Artifactory instances.
Released: February 13, 2017
This release updates Mission Control to support the latest features released with Artifactory 5.0.
This release of Mission Control complements new features in Artifactory 5.0 by adding support for Artifactory's Cluster License Manager for HA installations.
snapshotVersionBehavior
in the localRepository block DSL has been corrected to show "unique" as the default value.Released: December 28, 2016
Mission Control launches event notifications by email. By configuring a set of policies on managed instances and repositories, Mission Control will send email alerts based on specific events. Currently, events connected to storage are supported, so you can get email alerts when an instances free space passes the set percentage threshold, or when a repository's used space passes the set usage threshold.
Mission Control Graphs have been enhanced to show not only historical data, but also predictive data. Now, you don't have to second guess how your instances and repositories will behave in the future. Mission Control runs a predictive analysis and displays an estimation of how your instances and repositories will use storage 3, 6, 12 and 24 months into the future.
In addition to UI enhancements and many bug fixes, this release includes the following main updates:
bucket_id
parameter can take either the bucket name or the bucket ID.Released: January 25, 2017
Released: November 16, 2016
Mission Control standalone installations for Windows, Mac and Linux now come in separate ZIP files.
Mission Control Docker upgrade has been greatly simplified and uses an installation script.
Mission Control displays Graphs showing historical data on Artifactory instances and repositories giving you a view to past usage and insights on trending behavior. This is supported by an InfluxDB database which is now included in all variants of Mission Control installation files.
In addition to above main enhancements and bug fixes, this release includes the following updates:
Released: December 14, 2016
Mission Control takes centralized global repository management to the world of C/C++ development. With the addition of support for Conan in the latest release of JFrog Artifactory, v4.15, Mission Control is fully aligned and also supports Conan repositories for C/C++ binary components.
In addition to UI enhancements and many bug fixes, this release includes the following main updates:
Released: September 27, 2016
Several enhancements have been made to Disaster Recovery:
JMX MBeans can also monitor changes in an Artifactory's instance state (started up, or went down)
Mission Control Docker installation has been greatly simplified and uses an installation script.
In addition to UI enhancements and many bug fixes, this release includes the following main updates:
Released: October 20, 2016
This version supports PHP Composer repositories introduced in Artifactory v4.14.0
Released: November 2, 2016
Repository configuration scripts have been enhanced to include the blockXrayUnscannedArtifacts
and xrayMinimumBlockedSeverity
parameters that control download blocking in Artifactory.
Released: August 8, 2016
Monitor a variety of parameters using any JMX agent.
Manage configuration scripts in a Git repository.
Get instant feedback from Mission Control on validity of your configuration scripts
Mission Control is now available as a Docker image
In addition to UI enhancements and many bug fixes, this release includes the following main updates:
Released: July 3, 2016
JFrog Mission Control now offers one-click disaster recovery for your Artifactory instances. Once DR is configured, in case of any event that makes one of your Artifactory installations inoperable, you may resume operations almost immediately at the click of a button in Mission Control. Users of the downed instance may not even notice that anything happened.
JFrog Mission Control REST API has been upgraded to v2. This version is significantly changed from v1 of the REST API which is now deprecated, and we strongly recommend that you upgrade your scripts to use the new API.
Mission Control can manage backup and disaster recovery for Artifactory, but what happens if the server on which you're running Mission Control itself goes down? To support this scenario, and facilitate nearly instant recovery, Mission Control may now be easily backed itself up to facilitate near-real-time recovery.
In addition to UI enhancements and many bug fixes, this release includes the following main updates:
Released: May 20, 2016
JFrog Mission Control introduces License Bucket management which automates, and therefore, greatly simplifies the management of licenses for large numbers of Artifactory instances.
In addition to UI enhancements and many bug fixes, this release includes the following main updates:
Released: February 28, 2016
Mission Control is now available for installation as a Debian distribution.
In addition to UI enhancements and many bug fixes, this release includes the following main updates:
Released: February 1, 2016
JFrog is proud to announce the release of JFrog Mission Control 1.0. This version follows several weeks of customer testing and implements many of the requests provided in the feedback we received on our preview version.
Mission Control's monitoring capabilities have been greatly enhanced and allow its operator to view a variety of information about managed Artifactory instances. These include JVM parameters, storage summary, replication data and running Artifactory tasks.
To facilitate quick, repeatable and accurate setup of Artifactory instances, Mission Control now offers the capability to import configuration parameters from existing Artifactory instances, tweak them as necessary, and then deploy them to other Artifactory instances. This presents a quick and easy way to provision uniform configuration to any number of Artifactory instances.
Mission Control now exposes a rich REST API to allow fully automated management of Artifactory instances including creating and updating instances, creating and updating repositories, creating and updating users, groups and permissions, all through REST API.
Mission Control now provides convenient wizard-based license management. Easily deploy licenses to all your Artifactory instances in a single bulk operation and be alerted of duplicate licenses that you may have in your global Artifactory network.
In addition to UI enhancements and many bug fixes, this release includes the following main updates: