search

openshift-pipelines / pipelines-as-code

Pipelines-as-Code for Tekton
https://pipelinesascode.com
Apache License 2.0
124 stars 81 forks source link

Enable custom build status names #1682

Open DevOpsJeremy opened 1 month ago

DevOpsJeremy commented 1 month ago

Issue

Currently Pipelines as Code provides a build status to the git provider. The name/label of this build status is always what's set as the application-name (default is "Pipelines as Code CI").

This label isn't very informative as it is--especially if there are multiple different PipelineRuns defined in the repository. In some git providers such as Bitbucket Server, the only information available in the interface is the application name and build status--as such, there's no way to know which Pipeline is running without logging into OpenShift to see the status of the pipeline.

See example: Untitled

Proposal

Enable the build label to be defined per-PipelineRun or per-Pipeline.

This could be defined in the annotations or maybe labels, something like: 

labels:
  pipelinesascode.tekton.dev/application-name: build-docker-containers

If not specified in the PipelineRun, of course, it would default to what's defined in the ConfigMap.

chmouel commented 1 month ago

Hi, which git provider ? most of them would show the application/pipelinerunname

DevOpsJeremy commented 1 month ago

This is for Bitbucket Server. It shows the application name "Pipelines as Code CI". But this name doesn't give any indication as to which pipeline is running. Below is an example of how the interface looks in Bitbucket Server:

Untitled

https://confluence.atlassian.com/bitbucketserver/view-builds-information-in-bitbucket-1014275096.html