CI/CD convert workflow to pipeline
cicd_convert_workflow_to_pipelineConvert a repository's existing CI definition - GitHub Actions workflows, a .gitlab-ci.yml, a bitbucket-pipelines.yml or a .circleci/config.yml - into an Ankra pipeline (.ankra/pipeline.yaml), the definition Ankra's own pipeline engine runs inside the cluster. Read the files first with github_read_file (or workspace_read_file) and pass their contents here. Returns the rendered pipeline_yaml, a notes list naming every construct the conversion could not carry across faithfully, and a validation verdict. This tool only PROPOSES text - it writes nothing to the repository; open a pull request with scm_create_pull_request (agent mode) or github_create_pull_request to land it. A converted pipeline is a starting point a person reviews, never a drop-in replacement: marketplace actions, Bitbucket pipes and CircleCI orb commands the mapping table knows become the matching Ankra stage or ankra/* step, and an unmappable third-party step becomes a stage that FAILS with an explanation rather than being silently dropped, so always show the user the notes. Bounded to 20 files and 256KB of content per call.
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": {
"workflow_files": "<workflow_files>"
},
"name": "cicd_convert_workflow_to_pipeline"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | OPTIONAL. The source format. Omitted, it is inferred from the paths: a file named .gitlab-ci* selects gitlab_ci, a file named bitbucket-pipelines* selects bitbucket_pipelines, a path under .circleci/ selects circleci, anything else selects github_actions. | |
| application_id | No | OPTIONAL. The Ankra Application this repository belongs to. When it resolves, the converted pipeline's metadata.name is the application's name instead of one derived from the workflow; when it does not, the conversion still returns a pipeline and says so in the notes. | |
| workflow_files | Yes | The CI definition files to convert, with their repository paths. For GitHub Actions pass every workflow that participates in the build - they are converted into ONE pipeline, because a repository's workflows share one checkout and one run. For GitLab, Bitbucket and CircleCI pass exactly one file: the .gitlab-ci.yml, the bitbucket-pipelines.yml or the .circleci/config.yml. |