### Plastic SCM Server Shell - Starting and Connecting

Source: https://docs.unity.com/en-us/unity-version-control/release-notes/8

This example demonstrates how to start and interact with the Plastic SCM server's interactive shell. It shows the process of launching the shell, selecting a running server from a list, and establishing a connection. This is useful for managing daemonized Plastic SCM servers.

```text
C:\path\bin\server>plasticd shell
Found 2 servers running:
1. MY_LAPTOP:8084
2. MY_LAPTOP:8085
Please choose a server [1-2]: 2
Connecting to MY_LAPTOP:8085
MY_LAPTOP:8085>
```

--------------------------------

### Manage Plastic Proxy Service using plasticd command

Source: https://docs.unity.com/en-us/unity-version-control/release-notes/8

This shows how to manage the Plastic proxy service using the `plasticd` command-line tool. It includes examples for installing the service, starting the server, stopping the server, and uninstalling the service. These commands are essential for setting up and controlling the Plastic proxy on a server environment.

```bash
C:\PlasticSCM\server> plasticd proxy --installservice
Installing service Plastic Proxy...
Service Plastic Proxy has been successfully installed.
Creating EventLog source Plastic Proxy in log Application...
Service correctly installed
C:\PlasticSCM\server> plasticd proxy --startServer
started
C:\PlasticSCM\server> plasticd proxy --stopServer
stopped
C:\PlasticSCM\server> plasticd proxy --uninstallservice
Removing EventLog source Plastic Proxy.
Service Plastic Proxy is being removed from the system...
Service Plastic Proxy was successfully removed from the system.
Service correctly uninstalled
```

--------------------------------

### Get Comprehensive Help with Examples in Unity Version Control CLI

Source: https://docs.unity.com/en-us/unity-version-control/cli/help

This command provides detailed help, including examples, for a specific command. It's the most in-depth way to learn about a command's functionality and application. Replace '<command>' with the actual command name.

```bash
cm <command> --help
```

--------------------------------

### Manage Plastic Proxy Service on Windows (Command-line)

Source: https://docs.unity.com/en-us/unity-version-control/release-notes/11

Provides subcommands for installing, uninstalling, starting, stopping, and checking the status of the Plastic Proxy service on Windows. Configuration requires a 'plasticcached.network.conf' file in the server installation directory.

```bash
plasticd proxy --installservice
plasticd proxy --start
plasticd proxy --stop
plasticd proxy --restart
plasticd proxy --status
plasticd proxy --uninstallservice
```

```json
[
  {
    "port": 8085,
    "type": "tcp",
    "security": "none"
  }
]
```

--------------------------------

### Enable Automatic Startup for Unity Version Control Server (Shell)

Source: https://docs.unity.com/en-us/unity-version-control/install-uvcs-on-linux

Configures the Unity Version Control server to start automatically on system boot. This ensures the version control server is always available.

```shell
systemctl enable plasticscm-server
```

--------------------------------

### Enable Automatic Startup for Unity Version Control Proxy Server (Shell)

Source: https://docs.unity.com/en-us/unity-version-control/install-uvcs-on-linux

Configures the Unity Version Control proxy server to start automatically on system boot. This ensures the proxy is always available for managing version control operations.

```shell
systemctl enable plasticscm-proxy-server
```

--------------------------------

### Install Unity Version Control Complete Installation on Debian

Source: https://docs.unity.com/en-us/unity-version-control/install-uvcs-on-linux

Installs the complete version of Unity Version Control on Debian, including both server and client tools for on-premises setups. This provides a full version control experience.

```bash
sudo apt-get install plasticscm-complete
```

--------------------------------

### Specifying a local repository in DVCS Edition installer

Source: https://docs.unity.com/en-us/unity-version-control/release-notes/8

Provides an example of how to specify a local repository using the 'local' alias for the server name when using the new 'DVCS Edition' installer for Plastic SCM.

```bash
my_personal_toolbox@local
```

--------------------------------

### Show GameUI Help Information

Source: https://docs.unity.com/en-us/unity-version-control/release-notes/5

Demonstrates how to display help information for the GameUI executable using command-line arguments. Common arguments include '--help', '-h', '--?', and '-?'.

```bash
$> gameui.exe --help
```

--------------------------------

### View Shelveset Help (Command-Line)

Source: https://docs.unity.com/en-us/unity-version-control/release-notes/11

Provides instructions on how to access help documentation for the 'cm partial shelveset' commands. This is useful for understanding available subcommands and their specific usage, including creation, application, and deletion of partial shelvesets.

```bash
cm partial shelveset --help
cm partial shelveset create --help
```

--------------------------------

### Start Plastic Server for Client Configuration

Source: https://docs.unity.com/en-us/unity-version-control/uvcs-on-prem/saml-auth-microsoft

Command to start the Plastic server in console mode, which is a prerequisite for configuring the Plastic client via the CLI.

```bash
.\plasticd --console
```

--------------------------------

### Unity Version Control CLI: Checkout Examples

Source: https://docs.unity.com/en-us/unity-version-control/uvcs-cli/checkout

Illustrative examples of using the 'cm checkout' command for various scenarios. These examples demonstrate checking out specific files, all files with a certain extension, the current directory recursively, and using formatting options.

```bash
cm checkout file1.txt file2.txt

```

```bash
cm co *.txt

```

```bash
cm checkout .

```

```bash
cm checkout -R c:\workspace\src

```

```bash
cm co file.txt --format="Checking out item {0}" --resultformat="Item {0} checked out"

```

```bash
cm checkout link --symlink

```

```bash
cm checkout . -R --ignorefailed

```

```bash
cm co . --machinereadable --startlineseparator=">"

```

--------------------------------

### Example: Get Jira Issue Status using Unity Version Control CLI

Source: https://docs.unity.com/en-us/unity-version-control/uvcs-cli/issuetracker

Demonstrates how to retrieve the status of a specific Jira issue using the Unity Version Control CLI. This example includes the necessary parameters: tracker name ('jira'), task ID, user credentials, host URL, and project key.

```bash
cm issuetracker jira status get 11 --user=user@mail.es --password=pwd --host=https://user.atlassian.net --projectkey=PRJ
```

--------------------------------

### Perforce Multi-Branch Sync Example (CLI)

Source: https://docs.unity.com/en-us/unity-version-control/release-notes/9

An example of the 'cm sync' command demonstrating how to synchronize a Plastic repository named 'plastic-repo' with a Perforce server. This example specifies the Perforce server address, the main branch path '//depot/main', the general branches folder '//depot', and user credentials.

```bash
cm sync plastic-repo p4multibranch p4server:1666 --mainbranch=//depot/main --branchesfolder=//depot --user=user --pwd=mypwd
```

--------------------------------

### Unity Version Control CLI: cm find Pagination Examples

Source: https://docs.unity.com/en-us/unity-version-control/cli/cm-find/cm-find-syntax

Demonstrates how to use 'limit' and 'offset' parameters with the 'cm find' command to control the number of results returned and the starting point of the results.

```bash
cm find label "where owner='me'" limit 10 offset 20
cm find branches "where owner='me'" limit 10
```

--------------------------------

### Basic Usage of Unity Version Control CLI

Source: https://docs.unity.com/en-us/unity-version-control/uvcs-cli/objectspec

This command initiates the process of getting information about building object specifications using the Unity Version Control CLI. It serves as a starting point for users unfamiliar with the 'objectspec' functionality.

```bash
cm objectspec
```