[JIRA] (JENKINS-61320) MR status doesn't replace branch status

1 view
Skip to first unread message

tobias-jenkins@23.gs (JIRA)

unread,
Mar 4, 2020, 4:57:02 AM3/4/20
to jenkinsc...@googlegroups.com
Tobias Gruetzmacher created an issue
 
Jenkins / Bug JENKINS-61320
MR status doesn't replace branch status
Issue Type: Bug Bug
Assignee: Parichay Barpanda
Attachments: image-2020-03-04-10-55-07-801.png
Components: gitlab-branch-source-plugin
Created: 2020-03-04 09:56
Environment: Jenkins ver. 2.204.2
gitlab-branch-source-plugin 1.4.4
Priority: Major Major
Reporter: Tobias Gruetzmacher

Consider a branch source job with the following configuration:

  • Discover branches: Only branches that are not also filed as MRs
  • Discover merge requests from origin: Merging the merge request with the current target branch revision

Scenario:

  1. A user pushes a branch
    • A new job is created for the branch
    • The branch is built, but the build fails
    • The plugin pushes a "failed" status with name "jenkinsci/branch" to GitLab
  2. The user creates a merge request
    • A new job is created for the merge request
    • The branch job is disabled
    • The MR job is built and also fails
    • The plugin pushes a "failed" status with the name "jenkinsci/mr-head" to GitLab
  3. User realizes the build is broken and fixes a bug in the build system (not sure if this is only a problem if the HEAD of the branch doesn't change of if that always happens)
    • The MR job is built and is now successful
    • The plugin pushes a "passed" status with the name "jenkinsci/mr-head" to GitLab

The result is now a merge request which is still considered as "failed" by GitLab, because the Job "jenkinsci/branch" will forever be "failed":

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages