• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, when you trigger a pipeline, the pipeline name/description will be the commit message.

      It would be great to have the ability to customize/change the name/description of the pipeline : 

            [BCLOUD-22070] Ability to customize/change the pipeline name/description

            Bump, would love a feature like this.

            Even just the ability to add a prefix through the `bitbucket-pipelines,yml` would already be huge

            Jamilio Rasidi added a comment - Bump, would love a feature like this. Even just the ability to add a prefix through the `bitbucket-pipelines,yml` would already be huge

            R.Board added a comment -

            I'd love to have a name for each one that I can see when I need to run a pipeline manually.

            R.Board added a comment - I'd love to have a name for each one that I can see when I need to run a pipeline manually.

            Marcin Kielar added a comment - - edited

            Real world use-case:

            We're using Semantic Versioning when building release artifacts (Docker Images, .NET Libraries, Python Packages, etc.) We tag these in Artifact Repositories/Registries as well as in Git. It would be great, for tracking purposes to be able to name pipeline runs with the version of released artifact (i.e. dynamically, from a script in a pipeline).

            Ideally there would be a PATCH or PUT handler for /repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid} }}endpoint which would allow updating the name of the pipeline (or {{build_number{}}}, although this one is a number and would probably require way more work switching to string, than simply adding a new attribute to the pipeline object).

            Anyway, this is a much needed feature.

            Marcin Kielar added a comment - - edited Real world use-case: We're using Semantic Versioning when building release artifacts (Docker Images, .NET Libraries, Python Packages, etc.) We tag these in Artifact Repositories/Registries as well as in Git. It would be great, for tracking purposes to be able to name pipeline runs with the version of released artifact (i.e. dynamically, from a script in a pipeline). Ideally there would be a PATCH or PUT handler for /repositories/{workspace}/{repo_slug}/pipelines/{pipeline_uuid} }}endpoint which would allow updating the name of the pipeline (or {{build_number {}}}, although this one is a number and would probably require way more work switching to string, than simply adding a new attribute to the pipeline object). Anyway, this is a much needed feature.

            Orudzhali Nagaev added a comment - - edited

            Please add this feature! We run multiple automated testing scopes using a pipeline and cannot easily recognize which one is running by looking at the list of running pipelines

            Orudzhali Nagaev added a comment - - edited Please add this feature! We run multiple automated testing scopes using a pipeline and cannot easily recognize which one is running by looking at the list of running pipelines

            Please add this feature!

            Andrew Fellman added a comment - Please add this feature!

            Neil Coles added a comment -

            this would be very useful for pipelines im triggering via API

            Neil Coles added a comment - this would be very useful for pipelines im triggering via API

            Kamil Wrobel added a comment - - edited

            +1 on this issue
            We have a lot of pipelines in 1 project and often I want to see history of specific pipeline - now I have to dig in details of each pipeline because name does not say what pipeline was executed - only custom one are printed

            Kamil Wrobel added a comment - - edited +1 on this issue We have a lot of pipelines in 1 project and often I want to see history of specific pipeline - now I have to dig in details of each pipeline because name does not say what pipeline was executed - only custom one are printed

            +1 on this issue

            Aevin Sison Bulaong added a comment - +1 on this issue

            +1 on this issue

            Joel Esperanza added a comment - +1 on this issue

            +1 as well, I'd love to see this feature. It would be useful for custom pipelines triggered via the API and not via a code merge.

            Don MacKinnon added a comment - +1 as well, I'd love to see this feature. It would be useful for custom pipelines triggered via the API and not via a code merge.

              57465700c4e1 Edmund Munday
              641e77b2eb21 Patrik S
              Votes:
              73 Vote for this issue
              Watchers:
              35 Start watching this issue

                Created:
                Updated: