Support pipeline inputs in create_pipeline#742
Open
caiconkhicon wants to merge 1 commit into
Open
Conversation
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
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds support for passing pipeline inputs to
create_pipeline.The project pipeline API (
POST /projects/:id/pipeline) accepts aninputshash attribute (GA in GitLab 18.1). This adds an optional
inputsargumentto
create_pipeline, sent through as-is to the API.Backward-compatible: existing 2- and 3-argument calls are unchanged.
See: https://docs.gitlab.com/api/pipelines/#create-a-new-pipeline