Pipeline Operation: Validate

This page explains how to configure, run, and manage a Validate operation in pipelines. Validation checks metadata changes without applying them to the target org, ensuring deployments won’t fail.

The Validate operation simulates a deployment to confirm whether changes can be successfully applied. It runs checks and (optionally) executes tests, but no metadata is committed to the target org.

Validate is most useful when:

• Testing changes before a production deploy.

• Ensuring dependencies are met.

• Confirming Apex tests pass.

Creating a Validate Step

1. Go to Pipelines → create or edit a pipeline.

2. Click the + between Start and Stop.

3. In the configuration panel:

   • Name: e.g., Validate to Sandbox.

   • Operation: Select Validate.

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

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

   • Next step: Define behavior:

     • On pass → Stop or move to another step.

     • On fail → Stop, Rollback, or branch to another action.

4. Click Save.\

Example: A Validate step created for Source–Sandbox with tests set to Default, and both On pass/On fail set to Stop.

Editing a Validate Step

• Open the pipeline containing the Validate step.

• Click the Validate node in the diagram.

• Select Edit to update details such as:

  • Target org.

  • Test execution options.

  • Pass/fail next steps.

• Save changes to update the pipeline.

Editing allows you to switch from a simple validation to a full test-validation flow without recreating the pipeline. \

Running the Validate Pipeline

1. Click Run pipeline.

2. Revvy simulates the deployment against the target org.

3. Results are displayed in real time in the pipeline diagram.

   • Successful validation shows a green check on the Validate step.

   • Failures are flagged in red, and logs are available.

Viewing Validation Results

After execution, results are logged under Activities for the related branch:

• Jobs show:

  • Type: Validate.

  • Status: Completed or Failed.

  • Execution duration and timestamp.

• Pipelines show:

  • Pipeline name.

  • Status: Completed.

  • Total duration.

• Logs provide detailed messages:

  • Metadata retrieval.

  • Dependency checks.

  • Test outcomes.

  • Success/failure messages.

Example log entries: [Oct 8, 2025 4:58 PM] [info] Retrieve Salesforce components started

[Oct 8, 2025 4:59 PM] [info] No local changes to validate

[Oct 8, 2025 4:59 PM] [info] Job completed

Best Practices

• Always validate in lower environments before a production deployment.

• Configure “On fail → Rollback” for safer automation.

• Run full test suites in higher environments to catch Apex issues early.

• Review logs after each validation to confirm no missing dependencies.