Pipeline Operation: Deploy

This page explains how to configure and run a Deploy operation in a Revvy pipeline, including setup, execution, and tracking results.

The Deploy operation moves changes from one Salesforce org to another. It can be added as a pipeline step, either as the primary deployment or as part of a larger automated workflow.

Deploy steps can be configured with:

• Target organization (where the deployment will go).

• Run tests (default or custom test options).

• Next step (define what happens on success or failure).

Creating Deploy Step

1. Navigate to Pipelines and create a new pipeline or edit an existing one.

2. Under the Overview tab, click the + button between Start and Stop.

3. In the configuration panel, enter:

   • Name: e.g., Deploy to Dev Org.

   • Operation: Select Deploy.

   • Target organization: Choose the connected org (e.g., Source–Sandbox).

   • Run tests: Select the test option (default or custom).

   • Next step: Define behavior:

     • On pass → Continue (e.g., to next step or Stop).

     • On fail → Define rollback or stop.

4. Click Add.

Example: A Deploy step was created targeting Source–Sandbox, with both On pass and On fail set to Stop.

Running the Deploy Pipeline

1. Once the step is added, the pipeline diagram updates to show Start → Deploy → Stop.

2. Click Run pipeline in the top-right corner.

3. The system executes the deployment to the selected target org.

The pipeline now visually reflects the Deploy action as part of the flow.

Viewing Deployment Results

After running the pipeline, results are logged in the Activities tab of the related branch.

• Jobs section shows:

  • Type: Deploy

  • Status: Completed (with timestamp and duration).

  • Created by: User or system.

• Pipelines section shows:

  • Pipeline name (e.g., Dev Pipeline).

  • Status: Completed.

  • Execution duration.

Example: A deployment executed on Oct 8, 2025, completed in 5 seconds and was marked successful in both Jobs and Pipelines logs.

Best Practices

• Always validate in a lower environment before deploying to higher ones.

• Use conditional next steps (Rollback, Stop) to handle failures automatically.

• Monitor the Activities tab after each deployment to track status and logs.

• Pair Deploy steps with Run Tests for better confidence.