Managing & Executing Pipelines

This page explains how to execute pipelines in Revvy, either automatically through triggers or manually on demand. It also describes how to monitor results after execution.

Pipelines in Revvy can be executed in two ways:

1. Automatic execution — triggered by predefined actions, such as commits or pull request merges.

2. Manual execution — triggered directly by a user from the pipeline interface.

Both approaches ultimately log results in the Activities tab, where you can track success, failures, or exceptions for each step.

Automatic Execution

1. Open the Settings tab of a pipeline.

2. Toggle Run automatically to enable automation.

3. Select a Trigger action:

   • Commit to Branch

   • Pull Request Merge

4. Choose a Trigger branch (e.g., ReleaseBranch, or feature branches).

5. Click Save.

Once configured, the pipeline launches automatically whenever the trigger condition is met.

Example: A QA pipeline is set to run automatically when code is merged into the ReleaseBranch. Every merge event automatically triggers validation, deployment, or rollback steps without user intervention.

Manual Execution

1. Go to the Pipelines tab.

2. Click Run pipeline.

3. In the modal:

   • Select a Branch.

   • Select a Pipeline.

4. Click Run to start the process.

Example: A developer manually selects the JiraUserStory branch and the QA Pipeline, then runs it on demand for validation testing.

Viewing Results

Once a pipeline runs (automatic or manual), results are visible in the Activities tab of the target branch. Each step displays:

• Status — Completed, Failed, or Exception.

• Type — operation performed (Deploy, Validate, Rollback, WebHook, Code Scan, Execute Apex, etc.).

• Created by — the user or system that triggered the run.

• Duration — how long the step took to complete.

• Timestamp — start and finish times.

Example: In the ReleaseBranch Activities tab, results may include:

• Rollback — Completed in 17s

• Deploy — Completed in 43s

• WebHook — Completed in 3s

• Code Scan — Exception in 1m 2s

This provides full traceability and ensures teams can troubleshoot or confirm successful deployments quickly.