Workspaces
Last updated
Last updated
A workspace is a container in which you code. For example, say you're trying to commit the code changes through EZ-Commit to a version control repository branch. In such case, a workspace gets created dynamically and it gets assigned to your repository/branch. Multiple workspaces get created for each commit/merge operation in ARM. If the workspace is already available, then the operation will get invoked in the existing one.
Each workspace has a total storage limit of 500 GB allocated per tenant. An email notification will be sent to users once the workspace limit is about to be reached. On the limit being reached, users will not be able to run any further operations in ARM unless the workspace size is either increased or idle workspaces are deleted.
This section describes how Org Administrators can manage existing workspaces within an ARM instance.
To view the workspace:
Log in to your ARM account.
Hover your mouse over the Admin tab and click on Workspaces.
The list of workspaces created/available to date will be listed on this page.
Each workspace will have:
Workspace label
Date/time stamp for workspace created
Workspace allocated author detail
Repo and Branch details
Workspace status, i.e., running or in idle state
The module on which the workspace has been allotted
Last used on along with the size consumed
You can reset your workspace to revert to the default workspace settings for your user account.
In the Workspaces tab, check for your workspace label and click on Reset.
Upon confirmation, the workspace is reset to the default workspace for your user account.
You can delete a workspace if it is no longer required. Deleting a workspace is permanent and unrecoverable, and it may have an impact on the jobs running on the workspace. However, deleting a workspace will not delete the repository or branches within it. Repositories/branches that belong to other workspaces will not be affected.
An Org Administrative user can delete the workspaces of another user.
Important Note: If you are unable to delete a workspace, it is because you lack the required permissions. The Delete option will not be available.
Once confirmed, the workspace gets deleted.
Deleting inactive workspaces can free up resources for other users. Workspace Settings allow you to delete multiple workspaces at one time that are in an idle state for a longer period of time.
Click on the Settings button and specify the final date when all workspaces are cleared.
If the workspace limit is reached, the user may submit a request to increase the size of their workspace. Our super administrator will confirm the same with the user, and the workspace limit is extended based on the user subscriptions.
The Super Admin needs to log in to ARM with super admin credentials and then navigate to Workspace Mgmt. page.
Based on the user's org requirement/subscription, the super admin will add additional workspace to the current org limit. The max size limit which can be increased is 1,000 GB.
