Manage test quarantine
manage_test_quarantineChange a connected repository's flaky-test quarantine. action quarantine quarantines one test (test_key and reason), so its failures stop failing runs. action release ends a quarantine (quarantine_id, optional reason). action settings changes the quarantine's settings; name only the ones to change. Address the repository with exactly one of repository_id, application_id, or owner and repo. Needs pipelines.manage.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"action": "<action>"
},
"name": "manage_test_quarantine"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| repo | No | Repository name, with owner. | |
| owner | No | Repository owner (organisation or user), with repo, instead of repository_id. | |
| action | Yes | What to do. | |
| reason | No | Why: required to quarantine, optional on release. At most 500 characters. | |
| enabled | No | settings only: turn the quarantine on or off. | |
| provider | No | Narrows owner and repo when the same repository is connected on two providers. | |
| test_key | No | quarantine only: the test's 64-character key. | |
| min_samples | No | settings only: how many observed runs a test needs before it is proposed. | |
| quarantine_id | No | release only: the quarantine's id. | |
| repository_id | No | The connected repository's id, from list_pipeline_repositories. | |
| application_id | No | An application whose linked repository to address, instead of repository_id. | |
| min_flaky_rate | No | settings only: the flaky rate, 0 to 1, from which a test is proposed. | |
| release_after_passes | No | settings only: consecutive passes after which a quarantine is released. |