Support arguments and/or environment for custom pipelines

Issue #18030 duplicate
Daishi Harada created an issue

Sample use case:

We currently use custom pipelines to do "version bump" processing (e.g., git tagging, etc). This currently is a two-step process, where we update the version in a file in the repository, then invoke the custom pipeline through the web UI for the appropriate branch.

It would be much simpler for us if the custom pipeline could take arguments, for example through additional environment variables.

For example, we might have:

pipelines:
  custom:
    tag-version:
      - step:
          script:
            - ./tag_version.sh $VERSION

Then the existing "Run Pipeline for <branch>" window could have an optional "Add Environment Variables to pipeline run" which allows the user to specify additional variables beyond what's already configured in Settings/Pipelines/Repository Variables.

The use of environment variables is just an example here, and I'm not attached to that specific solution if there are alternative ways to pass information from the "run pipeline" UI to the pipeline script.

Comments (2)

  1. Aneita Yang

    Hi @Daishi Harada,

    Thanks for reaching out and for the suggestion.

    We're currently tracking this feature request on issue #13737 - I encourage you to vote for / watch that issue if it's something that you're interested in. We hope to be able to support parameterised builds later this year.

    Aneita

  2. Log in to comment