jenkinsci / jenkinsci/gerrit-trigger-plugin

[JENKINS-31252] Two parallel running builds are assigned to the same buildnumber

Open
#747 0 comments 0 reactions 0 assignees View on GitHub
component:gerrit-trigger-plugin imported-jira-issue priority:minor resolution:unresolved
Dominant language
Java
Stars
226
Forks
289
PR merge metrics
No merged PRs in 30d

Description

Sometimes two parallel builds on our Jenkins server are combined into one build. when that happens, the first build gets all the artifacts attached to it, the second build is not listed in jenkins. See the attached screenshot how it looks like on the first build page.

As you can see the build data for the moudles is there, also the links for both builds work, the second build is just assigned to the wrong "parent".

In this case here build 4785 failed, but the gerrit trigger plugin notified the failure on the commit of build 4784.

---
Originally reported by tisoft_media, imported from: Two parallel running builds are assigned to the same buildnumber


  • assignee: rsandell
  • status: Open
  • priority: Minor
  • component(s): gerrit-trigger-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 1
  • imported: 2025-12-06

Raw content of original issue

Sometimes two parallel builds on our Jenkins server are combined into one build. when that happens, the first build gets all the artifacts attached to it, the second build is not listed in jenkins. See the attached screenshot how it looks like on the first build page.

As you can see the build data for the moudles is there, also the links for both builds work, the second build is just assigned to the wrong "parent".

In this case here build 4785 failed, but the gerrit trigger plugin notified the failure on the commit of build 4784.

environment

```
Jenkins 1.634

Gerrit Trigger Plugin 2.17.0
```

1 attachment

- [Bildschirmfoto vom 2015-10-29 10-53-51.png](https://issues.jenkins.io/secure/attachment/30987/Bildschirmfoto%20vom%202015-10-29%2010-53-51.png)
> ![Bildschirmfoto vom 2015-10-29 10-53-51.png](https://issues.jenkins.io/secure/attachment/30987/Bildschirmfoto%20vom%202015-10-29%2010-53-51.png)

Contributor guide

Open the contributing guide

Research direction

Reproduce the parallel-build behavior using Jenkins 1.634 and Gerrit Trigger Plugin 2.17.0, starting with how builds are assigned to their parent and how failure notifications select a commit. Done means parallel builds remain distinct, retain the correct artifacts, and the failure for build 4785 is reported on its own commit rather than build 4784.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.