Skip to main content

​
What this check does

DSALTA looks for build validation / status policies applied to default branches.
This check also runs on 1 other integration — see Merging of code changes should require passing status-checks for the full list.
Passes when: Assessed branches require successful builds or checks before merge per policy.

​
Why this matters

Build policies help ensure changes are tested before merge.

​
How to fix

Require passing builds before merging
  1. In Azure DevOps, open your project and go to Repos → Branches.
  2. Hover over the default branch (e.g. main), open the ⋯ menu, and select Branch policies.
  3. Under Build Validation, click + to add a build policy.
  4. Choose the Build pipeline that runs your checks, set Trigger to Automatic, and set Policy requirement to Required.
  5. Click Save.
Once resolved, DSALTA records a 200 (compliant) result on this test’s Source Data tab at the next scheduled run.

​
Frequently asked questions

Once a day, at 02:00 America/New_York, while the integration is connected. A run is skipped entirely if the integration is not in a connected state, or if the test has been deactivated.To see a fix reflected sooner, open the test from Data Library → Tests and click Run in the Run Test row. You need Full Access to run a test on demand.
The Status column answers “did the check run?”, not “did I pass”. Completed means DSALTA reached your system and finished evaluating — a check that ran and found a problem is still Completed.To see what it found, open the test and read the result code on the Source Data tab. 200 means nothing to fix; 204 means the check did not apply to your environment; 207 means it ran and found a compliance gap you need to act on. See Understanding test results.
Usually not. On an integration-powered check, Failed means DSALTA was blocked and could not evaluate it — result code 403 (a missing permission) or 428 (a setting DSALTA still needs from you). Code 500 means the run failed on DSALTA’s side.A genuine compliance gap does not turn the list red — it runs to completion and shows 207.
Deactivate it: open the test from Data Library → Tests, then use the ⋮ menu at the top right of the panel and choose Deactivate Test. It applies immediately, with no confirmation step.Write your justification in the Comments tab before you deactivate. Once deactivated, every other tab is grayed out, so Comments is the only place an auditor can read why — see Test detail.
No. DSALTA only reads. It never creates, modifies, or deletes resources, and every remediation step is performed by your team directly in the third-party product.