Creating Deployments

This guide walks you through creating and executing deployments in Mantis.

Deployment Sources

You can deploy from three sources:

Source	Description	Use Case
Solution	Complete deployment package	Full application deployment
Sequence	Specific workflow	Targeted operation
Action	Single operation	Quick fix or test

Creating a Solution Deployment

Step 1: Navigate to Deployments

1. Open Lens in your browser
2. Click Deployments in the sidebar
3. Click New Deployment

Step 2: Select Solution

1. Choose Solution as the source type
2. Select the solution from the dropdown
3. Choose the version to deploy

┌─────────────────────────────────────────────────────────┐
│  Create Deployment                                      │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  Source Type:  ● Solution  ○ Sequence  ○ Action         │
│                                                         │
│  Solution:     [customer-portal                   ▼]    │
│  Version:      [1.3.0                             ▼]    │
│                                                         │
└─────────────────────────────────────────────────────────┘

Step 3: Select Environment

Choose the target environment:

┌─────────────────────────────────────────────────────────┐
│  Select Environment                                     │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  ● Development    (2 targets)                           │
│  ○ Staging        (4 targets)                           │
│  ○ Production     (12 targets)                          │
│                                                         │
└─────────────────────────────────────────────────────────┘

Step 4: Configure Execution

Set execution options:

Option	Description	Default
Execution Mode	Parallel, Sequential, or Rolling	Parallel
Failure Strategy	Stop, Continue, or Ignore failures	Stop
Timeout	Maximum step duration	300 seconds
Priority	Queue priority	0 (normal)

Step 5: Review and Deploy

1. Review the deployment summary
2. Verify targets and versions
3. Click Deploy

┌─────────────────────────────────────────────────────────┐
│  Review Deployment                                      │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  Solution:      customer-portal v1.3.0                  │
│  Environment:   Production                              │
│  Targets:       12 machines                             │
│                                                         │
│  Sequences:                                             │
│    1. run-migrations (^1.0.0 → 1.2.0)                  │
│    2. deploy-backend (^2.0.0 → 2.3.1)                  │
│    3. deploy-frontend (^1.0.0 → 1.1.0)                 │
│                                                         │
│  Execution:     Rolling (batch size: 3)                 │
│  Failure:       Stop on first failure                   │
│                                                         │
│                        [Cancel]  [Deploy]               │
└─────────────────────────────────────────────────────────┘

Creating a Sequence Deployment

For targeted operations without a full solution:

1. Select Sequence as source type
2. Choose the sequence and version
3. Select targets directly (not via environment)
4. Configure and deploy

Creating an Action Deployment

For quick single operations:

1. Select Action as source type
2. Choose the action and version
3. Provide argument values
4. Select target(s)
5. Execute

Quick Deploy

From the solution detail page:

1. Navigate to the solution
2. Click Deploy next to an environment
3. Confirm the deployment

This uses default execution settings.

Variable Override

During deployment, you can override variable values:

┌─────────────────────────────────────────────────────────┐
│  Variable Overrides                                     │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  Use environment values:                                │
│    database_host: prod-db.company.com                   │
│    log_level: warn                                      │
│                                                         │
│  Override for this deployment:                          │
│  ┌─────────────────────────┬────────────────────────┐   │
│  │ log_level               │ [debug            ]    │   │
│  └─────────────────────────┴────────────────────────┘   │
│  [+ Add Override]                                       │
│                                                         │
└─────────────────────────────────────────────────────────┘

Overrides apply only to the current deployment.

Scheduled Deployments

Scheduled deployments are managed through the Schedules feature, which is separate from creating an ad-hoc deployment. To deploy at a future time or on a recurring basis, create a schedule rather than a deployment directly.

See Schedules for details on creating and managing scheduled deployments.

Deployment from CLI

Using the mantisctl deployment create command (IDs may be UUIDs or SqIds):

# Deploy a solution to an environment (parallel mode by default)
mantisctl deployment create \
  --solution-id customer-portal \
  --source-version 1.3.0 \
  --environment-id production

# Deploy a sequence to specific targets
mantisctl deployment create \
  --sequence-id deploy-backend \
  --source-version 2.0.0 \
  --target web-prod-01 \
  --target web-prod-02

# Deploy an action with a variable
mantisctl deployment create \
  --action-id health-check \
  --source-version 1.0.0 \
  --target web-prod-01 \
  --var check_url=http://localhost/health

Pre-Deployment Checklist

Before deploying to production:

• Tested in lower environments
• Variable values configured for target environment
• All targets are online
• No deployment freeze is active
• Team is available to monitor
• Rollback plan is ready

Troubleshooting

Cannot Select Environment

Cause: Environment has no targets assigned

Solution: Assign targets to the environment first

Version Not Available

Cause: Requested version doesn’t exist or is archived

Solution: Check available versions in the solution/sequence

Deployment Blocked by Freeze

Cause: A deployment freeze is active

Solution: Wait for freeze to end or request override

Next Steps

• Target Selection - Choose deployment targets
• Execution Modes - Parallel, sequential, rolling
• Monitoring - Track deployment progress
• Overview - Return to deployments overview