![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Attachments:
|
mctp1.png, mctp2.png |
|
Components:
|
matrix-project-plugin |
|
Created:
|
27/Feb/15 8:58 AM
|
|
Description:
|
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
|
|
Project:
|
Jenkins
|
|
Labels:
|
build
notification
trigger
git
stash
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Natalia Pokrovskaya
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
