[JENKINS-27156] Git notifications trigger previous builds

We have multiple jenkins multi-configuration projects which are triggered by web hooks from Stash server on repository changes. On Jenkins, the projects triggers builds on slaves connected via SSH.

All this works pretty well, except that each stash notifications triggers previous build before actually proceeding current notification, i.e. say, on my Jenkins server I see 7 builds, with the last one done yesterday. After pushing a new changes on git, Jenkins, instead of running a new (8th) build on slaves, relaunch 7th build on slaves (during this time 8th build is shown as "waiting..."), and only then 8th build...

Have we misconfigured something?

Thank you in advance for your help!

---
Originally reported by natalia_pokrovskaya, imported from: Git notifications trigger previous builds

• assignee: kohsuke
  
• status: Open
  
• priority: Minor
  
• component(s): matrix-project-plugin
  
• label(s): build, git, notification, stash, trigger
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-06
  

Raw content of original issue

We have multiple jenkins multi-configuration projects which are triggered by web hooks from Stash server on repository changes. On Jenkins, the projects triggers builds on slaves connected via SSH.

All this works pretty well, except that each stash notifications triggers previous build before actually proceeding current notification, i.e. say, on my Jenkins server I see 7 builds, with the last one done yesterday. After pushing a new changes on git, Jenkins, instead of running a new (8th) build on slaves, relaunch 7th build on slaves (during this time 8th build is shown as "waiting..."), and only then 8th build...

Have we misconfigured something?

Thank you in advance for your help!

environment

```
Jenkins 1.588

Atlassian Stash 3.3.0
```

2 attachments

- [mctp1.png](https://issues.jenkins.io/secure/attachment/28666/mctp1.png)
> 
- [mctp2.png](https://issues.jenkins.io/secure/attachment/28667/mctp2.png)
> 

Start by reproducing the Stash webhook flow described for the matrix-project-plugin with Jenkins 1.588 and Stash 3.3.0, then trace how a notification schedules builds on SSH-connected slaves. Done means a new notification starts the current build without rerunning the previous build first.

Written by the indexing model from the issue text.