Running Quality Clouds Scans in Copado #

When using Copado, you can perform Quality Clouds scans either automatically or manually to ensure code quality and compliance before promoting your user stories.

• Automatic Scans
  
  

Automatic scans are triggered whenever changes are committed to a user story whose associated repository has been configured in Quality Clouds.

Note: To enable automatic scans, you must have Quality Gates activated in your Quality Clouds configuration.

Automatic scans help you detect issues early — before merging or closing a user story — improving code quality and reducing rework.

• Manual Scans
  
  

Manual scans can be launched directly from a Copado user story using a custom button.

👉 How to launch a manual scan:

1. Open the user story you want to scan.
2. Click the ‘Run Quality Clouds Scan Flow’ button.
3. The scan will run on the repository branch associated with that user story.
   
   

This allows developers to verify code quality at any point during the story lifecycle.

  #

Controlling Changes with Quality Gates #

Whenever a user attempts to ‘Submit Changes’ to promote a user story, the system will enforce Quality Clouds Quality Gates. Here’s how it works:

• The app checks whether a Quality Clouds scan has been executed after the latest code changes.
• That scan must have passed all Quality Gates.
• If not, the promotion is blocked automatically, and a message will explain the reason for failure.
  
  

This ensures that only code meeting defined standards can be promoted further in the pipeline.

 

What if Quality Gates fail? #

If a user story fails the Quality Gates during promotion, there are two possible actions:

1. Fix the issues manually in the source code and re-run the scan.
2. Request a write-off (override) — click here to learn how.