Skip to content

Support pipeline inputs in create_pipeline#742

Open
caiconkhicon wants to merge 1 commit into
NARKOZ:masterfrom
caiconkhicon:feature/pipeline-inputs
Open

Support pipeline inputs in create_pipeline#742
caiconkhicon wants to merge 1 commit into
NARKOZ:masterfrom
caiconkhicon:feature/pipeline-inputs

Conversation

@caiconkhicon

Copy link
Copy Markdown

Adds support for passing pipeline inputs to create_pipeline.

The project pipeline API (POST /projects/:id/pipeline) accepts an inputs
hash attribute (GA in GitLab 18.1). This adds an optional inputs argument
to create_pipeline, sent through as-is to the API.

Gitlab.create_pipeline(5, 'master', {}, { environment: 'production' })
Gitlab.create_pipeline(5, 'master', { VAR1: 'value' }, { environment: 'production' })

Backward-compatible: existing 2- and 3-argument calls are unchanged.
See: https://docs.gitlab.com/api/pipelines/#create-a-new-pipeline

Add an optional inputs hash argument to create_pipeline, sent to the
project pipeline API (POST /projects/:id/pipeline) as the inputs
attribute. Inputs are validated against the pipeline's spec:inputs
section.

See: https://docs.gitlab.com/api/pipelines/#create-a-new-pipeline
@caiconkhicon

caiconkhicon commented Jul 10, 2026

Copy link
Copy Markdown
Author

@NARKOZ : Hi 👋 , can you please review this MR, which is to support a new feature of GitLab pipeline. Thanks.

The lint failure is from other files, so I don't think I should fix them in this merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant