jenkinsci / jenkinsci/gitlab-branch-source-plugin

[JENKINS-65367] Make commit status context fully customizable

Open
#693 1 comment 0 reactions 0 assignees View on GitHub
component:gitlab-branch-source-plugin imported-jira-issue pipeline priority:major resolution:unresolved
Dominant language
Java
Stars
134
Forks
113
PR merge metrics
No merged PRs in 30d

Description

Extension of JENKINS-61020">JENKINS-61020. Currently the commit status is always prefixed with 'jenkinsci/(branch|mr-head|mr-merge|tag)'. Together with a custom context this causes the commit status to be cut off in the gitlab ui. It would be great if one could set a fully custom status instead, as in our case the 'jenkinsci/(branch|mr-head|mr-merge|tag)' prefix does not have meaningful information as we already know that we are running jenkins as ci and if the commit status is from a branch or not.

---
Originally reported by dhelsper, imported from: Make commit status context fully customizable


  • assignee: surenpi
  • status: Open
  • priority: Major
  • component(s): gitlab-branch-source-plugin
  • label(s): gitlab, multi-branch, pipeline
  • resolution: Unresolved
  • votes: 0
  • watchers: 3
  • imported: 20251216-182730

Raw content of original issue

Extension of JENKINS-61020. Currently the commit status is always prefixed with 'jenkinsci/(branch|mr-head|mr-merge|tag)'. Together with a custom context this causes the commit status to be cut off in the gitlab ui. It would be great if one could set a fully custom status instead, as in our case the 'jenkinsci/(branch|mr-head|mr-merge|tag)' prefix does not have meaningful information as we already know that we are running jenkins as ci and if the commit status is from a branch or not.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.