-
Suggestion
-
Resolution: Unresolved
-
None
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
I'd love to have a name for each one that I can see when I need to run a pipeline manually.
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.
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
+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 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.
yes, This would be really helpful and if we want to add something like (some key-words to identify anything ) has to be print here to save time that would be great . Right now I have to open every executed pipeline to see that.
+1 on this issue
When running a scheduled pipeline for integrations tests having a set pipeline title such as "End to end tests" rather than the default commit message would be very helpful.
This would be really helpful, especially when triggering pipelines one after the other. I would like to have something like:
Triggered by [other-repo] [commit message]
Bump, would love a feature like this.
Even just the ability to add a prefix through the `bitbucket-pipelines,yml` would already be huge