Environments

Overview

Environments are used to aggregate project resources (repository, Pipeline source, etc.) to simplify their management. Artifactory contains two default environments - DEV (Development) and PROD (Production), and additional custom environments can be created for specific projects, or for all projects, as needed. Each repository can be assigned to one environment only. Multiple repositories can be assigned to the same environment.

Manage Custom Environments

Artifactory release 7.53.1 introduces custom environments, a feature that enables you to allocate repositories in ways that best serve the needs of your organization. 

Custom environments can be created at the global level, where they are available for users of all projects, or at the project level for the members of that project. At the project level, specific roles can be assigned to custom environments, which enable you to implement a more granular permissions model for that project. 

Create a Custom Global Environment

Creating a custom global environment enables the users of all projects to perform actions on the repositories assigned to that environment, as defined by their roles. To create a custom global environment, you must be a Platform Admin, as described in Setting Environments and Actions for Global Roles.

1. In the Administration tab, go to Environments.
2. From the dropdown list at the top of the window, select All.
   
   
   
   
3. Click Create New Environment.
4. Enter a name for the environment and click Create. The maximum length is 32 characters.

Next, create a custom project environment.

Create a Custom Project Environment

Creating a custom project environment enables the users assigned to that project to perform actions on the resources assigned to that environment, as defined by their roles. 

1. In the Administration tab, go to Environments.
2. If you are a Platform Admin or the Project Admin of multiple projects, select the name of the relevant project from the dropdown list at the top of the window. (If you are a Project Admin for a single project, you will already be in your project and can skip this step.)
   
   
   
   
3. Click Create New Project Environment.

4. Enter a name for the environment and click Create. The maximum length is 32 characters.
   
   

   When creating a project environment, the name of the project is used as the prefix for the environment. Because of the prefix, multiple projects can have environments with the same name.

   
   

5. Continue with the following procedures:

• • Assign Environments to Global and Project Roles
  • Assign Environments to Repositories

Assign Environments to Global and Project Roles

After setting up the environments required by the organization, admins can modify existing roles (except the Project Admin role, which cannot be modified) by assigning these environments to the relevant roles:

• A Project Admin can assign global and project environments to project-specific roles. 
• A Platform Admin is required for assigning global environments to global roles.

The roles, which are assigned to groups and users, determine which actions can be performed on the resources contained in the environment.

For further instructions, see Managing Project Roles and Members.

Assign Environments to Repositories

Assign environments to repositories to define the resources included as part of the environment, either at the project level or at the global level.

1. In the Administration tab, go to Repositories > Repositories.
2. Click the name of a local or Federated repository. 

3. On the Basic tab, select the environment to which the repository should be assigned from the dropdown list.
   
   

   If any repository was assigned previously to more than one environment (e.g. DEV and PROD), you must change the selection to a single environment. The next time you log in to the JFrog Platform, the Basic tab will reflect the new UI below.

   
   
   
   

4. Click Save.

For more information, see Repository Management.

Delete a Custom Environment

A custom environment cannot be deleted if any roles or repositories are assigned to it. First remove the environment from the role or repository, and then delete the environment.

1. In the Administration tab, go to Environments. 
2. Select All or a specific project from the dropdown list.
3. Find the environment and verify that no roles or repositories are assigned to it.
   
   
   
   
4. Click the action menu and select Delete.