![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
mdonohue
|
|
Components:
|
join-plugin |
|
Created:
|
22/Dec/14 6:11 PM
|
|
Description:
|
If one of our downstream jobs is running behind (do to a lack of available resources on the particular node that it requires) the jobs are all collapsed together (like if we had a Quiet Period).
I wouldn't mind this so much but it uses the artifacts from the first job that kicks it off and not the last one. this means that we end up with a large number of untested changes.
SuccessConsole Output
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2043
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2044
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2045
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2046
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2047
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2048
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2049
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2050
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2051
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2052
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2053
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2054
originally caused by:
Started by an SCM change
Started by upstream project "M6_BUILD_MAIN_COMMIT" build number 2055
originally caused by:
Started by an SCM change
Building remotely on CDS_TestNode104 (TestNode SOLO OEM638 COM_12 ANT_DDDDDDDD ETHERNET DEBUG) in workspace d:\builds\Jenkins\workspace\M6_TEST_MAIN_COMMIT_SPACING_STRESS
Deleting project workspace... done
Email was triggered for: Before Build
Sending email for trigger: Before Build
An attempt to send an e-mail to empty list of recipients, ignored.
Copied 2 artifacts from "M6_BUILD_MAIN_COMMIT" build number 2043
As you can see the latest build was 2055 but it is using the artifacts from 2043.
We don't see this behavior when we are not using the Join Plugin.
|
|
Environment:
|
Windows Server and slaves. Join Plugin v1.15, Jenkins 1.554.2.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Brian Smith
|
|
|
|
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.
