Skip to content
Recued
Menu
← Back to recipes

Run a CircleCI pipeline definition

by recued-core v1

Approval-gated CircleCI pipeline run workflow. It reads the project and selected pipeline definition, then runs exactly one CircleCI pipeline definition on a selected branch through recued-core.circleci.pipeline.run. It does not create or delete projects, edit pipeline definitions, mutate triggers or schedules, roll back deployments, read environment variables, or call arbitrary CircleCI API routes.

How it works 10 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (10 steps)
provider trim
Trim whitespace from setting provider
organization trim
Trim whitespace from setting organization
project_name trim
Trim whitespace from setting project
definition_id trim
Trim whitespace from setting pipeline definition id
branch trim
Trim whitespace from setting branch
project_slug template
Generate text from a template
project ?
definition ?
run ?
card to_summary
Format results as a summary card
Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

branch setting = main
project setting =
circleci setting =
provider setting = gh
organization setting =
pipeline definition id setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Circleci connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

circleci circlecipipelinespipeline-definitionci-cdapprovaldeveloper-workflowpack:circleci

Details

10 steps 6 configurable settings recipe_id: run-circleci-pipeline-definition