Skip to content

Conversation

ShaunMaher
Copy link

GitLab's newer spec-format pipelines require manual inputs that use the $[[ inputs.BUILD_API ]] syntax, which wasn't supported by the create_pipeline function. This prevented programmatic triggering of pipelines that depend on manual input parameters.

Changes:

  • Add optional inputs parameter to CreatePipelineSchema as Record<string, string>
  • Update createPipeline function signature to accept inputs parameter
  • Include inputs in GitLab API request body when provided
  • Maintain backward compatibility with existing variables parameter

This enables automated triggering of complex CI pipelines that build multiple container images based on input selections, resolving the limitation where such pipelines could only be triggered manually via GitLab's web interface.

🤖 Generated with Claude Code

GitLab's newer spec-format pipelines require manual inputs that use the
$[[ inputs.BUILD_API ]] syntax, which wasn't supported by the create_pipeline
function. This prevented programmatic triggering of pipelines that depend on
manual input parameters.

Changes:
- Add optional inputs parameter to CreatePipelineSchema as Record<string, string>
- Update createPipeline function signature to accept inputs parameter
- Include inputs in GitLab API request body when provided
- Maintain backward compatibility with existing variables parameter

This enables automated triggering of complex CI pipelines that build multiple
container images based on input selections, resolving the limitation where
such pipelines could only be triggered manually via GitLab's web interface.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>
Co-Authored-By: Shaun Maher <[email protected]>
Copy link
Owner

@zereight zereight left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution.

Could you please share a link to the official GitLab documentation for the pipeline inputs feature?

Also, does this functionality only work with newer GitLab versions, or is it supported in older releases as well?

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.

3 participants