[JIRA] [core] (JENKINS-27635) Downstream build can start running before upstream build has completed
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27635 Downstream build can start running before upstream build has completed Change By: Jesse Glick Labels: pipeline trigger Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
[JIRA] [core] (JENKINS-27635) Downstream build can start running before upstream build has completed
SCM/JIRA link daemon commented on JENKINS-27635 Downstream build can start running before upstream build has completed Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/model/Run.java test/src/test/java/hudson/tasks/BuildTriggerTest.java http://jenkins-ci.org/commit/jenkins/ad56599e5c54d9a5f850f365ca0ff969d7c7f87d Log: Merge pull request #1628 from olivergondza/JENKINS-27635 JENKINS-20989 PeepholePermalink RunListenerImpl oncompleted should be triggered before downstream builds are triggered 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.
[JIRA] [core] (JENKINS-27635) Downstream build can start running before upstream build has completed
Oliver Gondža started work on JENKINS-27635 Downstream build can start running before upstream build has completed Change By: Oliver Gondža (27/Mar/15 9:18 AM) Status: Open InProgress 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.
[JIRA] [core] (JENKINS-27635) Downstream build can start running before upstream build has completed
Oliver Gondža
updated JENKINS-27635
Downstream build can start running before upstream build has completed
Change By:
Oliver Gondža
(27/Mar/15 9:04 AM)
Description:
Thisisaproblemincasedownstreambuildreferstothebuildofaparentprojectbypermalinksuchas{{LAST_SUCCESSFUL}}andexpectitwillmatchtheexactbuildthattriggeredthedownstreambuild.Thisisareasonableexpectationifdownstreambuildistriggeredforstable/successfulbuildsonly.Iobservedseveraldownstreambuildscopieddifferentversionsofartifactsfromupstreamproject.Duetoaheavilycontendedqueueittook~2minutestoschedulealldownstreambuildsusing{{hudson.tasks.BuildTrigger}}.Andastheactualschedulingisdonebeforeupstreamcompletes,severaldownstreambuildswasscheduledfastenoughtoobserveoldpermalinkvalue.Theschedulingshouldtakeplace*after*upstreambuildisdone.
Btw,Iwasnotable
EDIT:Nothingspecialneeds
to
findanydocumentationfortheassumptionthat
happenactually.Thisiswhat
upstream
and
isdoingatthetimesingle
downstream
buildshouldnotoverlap
runs
in
time
unittestwithoutanyartificialslowdowns
.
{noformat}Executor#1formaster:executingtest0#1#35prio=5java.lang.Thread.State:RUNNABLE atjava.net.URLStreamHandler.parseURL(URLStreamHandler.java:265) atsun.net.www.protocol.file.Handler.parseURL(Handler.java:67) atjava.net.URL.init(URL.java:614) -locked0xb31a06e(ajava.util.jar.JarFile) atjava.net.URL.init(URL.java:482) atsun.misc.URLClassPath$FileLoader.getResource(URLClassPath.java:1058) atsun.misc.URLClassPath.getResource(URLClassPath.java:199) atjava.net.URLClassLoader$1.run(URLClassLoader.java:358) atjava.net.URLClassLoader$1.run(URLClassLoader.java:355) atjava.security.AccessController.doPrivileged(NativeMethod) atjava.net.URLClassLoader.findClass(URLClassLoader.java:354) atjava.lang.ClassLoader.loadClass(ClassLoader.java:425) atsun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) atjava.lang.ClassLoader.loadClass(ClassLoader.java:358) -locked0x671b9b7f(ajava.lang.Object) atjava.lang.Class.getDeclaredMethods0(NativeMethod) atjava.lang.Class.privateGetDeclaredMethods(Class.java:2615) atjava.lang.Class.getDeclaredMethod(Class.java:2007) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:165) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:149) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:86) athudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:99) atcom.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) atcom.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) -locked0x457de3bb(ajava.lang.Object) atcom.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) atcom.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) atcom.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) atcom.thoughtworks.xstream.XStream.marshal(XStream.java:1026) atcom.thoughtworks.xstream.XStream.marshal(XStream.java:1015) atcom.thoughtworks.xstream.XStream.toXML(XStream.java:988) athudson.XmlFile.write(XmlFile.java:178) athudson.model.Run.save(Run.java:1898) athudson.model.Run.execute(Run.java:1795) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:263) -locked0x4bf22da1(ajava.lang.Object){noformat}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] [core] (JENKINS-27635) Downstream build can start running before upstream build has completed
Oliver Gondža
updated JENKINS-27635
Downstream build can start running before upstream build has completed
Change By:
Oliver Gondža
(27/Mar/15 11:40 AM)
Description:
Thisisaproblemincasedownstreambuildreferstothebuildofaparentprojectbypermalinksuchas{{LAST_SUCCESSFUL}}andexpectitwillmatchtheexactbuildthattriggeredthedownstreambuild.Thisisareasonableexpectationifdownstreambuildistriggeredforstable/successfulbuildsonly.Iobservedseveraldownstreambuildscopieddifferentversionsofartifactsfromupstreamproject.Duetoaheavilycontendedqueueittook~2minutestoschedulealldownstreambuildsusing{{hudson.tasks.BuildTrigger}}.Andastheactualschedulingisdonebeforeupstreamcompletes,severaldownstreambuildswasscheduledfastenoughtoobserveoldpermalinkvalue.
Theschedulingshouldtakeplace*after*upstreambuildisdone.EDIT:Nothingspecialneedstohappenactually.Thisiswhatupstreamisdoingatthetimesingledownstreamrunsinunittestwithoutanyartificialslowdowns.{noformat}Executor#1formaster:executingtest0#1#35prio=5java.lang.Thread.State:RUNNABLE atjava.net.URLStreamHandler.parseURL(URLStreamHandler.java:265) atsun.net.www.protocol.file.Handler.parseURL(Handler.java:67) atjava.net.URL.init(URL.java:614) -locked0xb31a06e(ajava.util.jar.JarFile) atjava.net.URL.init(URL.java:482) atsun.misc.URLClassPath$FileLoader.getResource(URLClassPath.java:1058) atsun.misc.URLClassPath.getResource(URLClassPath.java:199) atjava.net.URLClassLoader$1.run(URLClassLoader.java:358) atjava.net.URLClassLoader$1.run(URLClassLoader.java:355) atjava.security.AccessController.doPrivileged(NativeMethod) atjava.net.URLClassLoader.findClass(URLClassLoader.java:354) atjava.lang.ClassLoader.loadClass(ClassLoader.java:425) atsun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) atjava.lang.ClassLoader.loadClass(ClassLoader.java:358) -locked0x671b9b7f(ajava.lang.Object) atjava.lang.Class.getDeclaredMethods0(NativeMethod) atjava.lang.Class.privateGetDeclaredMethods(Class.java:2615) atjava.lang.Class.getDeclaredMethod(Class.java:2007) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:165) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:170) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.getMethod(SerializationMethodInvoker.java:149) atcom.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:86) athudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:99) atcom.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) atcom.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) -locked0x457de3bb(ajava.lang.Object) atcom.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) atcom.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) atcom.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) atcom.thoughtworks.xstream.XStream.marshal(XStream.java:1026) atcom.thoughtworks.xstream.XStream.marshal(XStream.java:1015) atcom.thoughtworks.xstream.XStream.toXML(XStream.java:988) athudson.XmlFile.write(XmlFile.java:178) athudson.model.Run.save(Run.java:1898) athudson.model.Run.execute(Run.java:1795) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:263) -locked0x4bf22da1(ajava.lang.Object){noformat}
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
[JIRA] [core] (JENKINS-27635) Downstream build can start running before upstream build has completed
Oliver Gondža
updated JENKINS-27635
Downstream build can start running before upstream build has completed
Change By:
Oliver Gondža
(26/Mar/15 7:54 PM)
Description:
Thisisaproblemincasedownstreambuildreferstothebuildofaparentprojectbypermalinksuchas{{LAST_SUCCESSFUL}}andexpectitwillmatchtheexactbuildthattriggeredthedownstreambuild.Thisisareasonableexpectationifdownstreambuildistriggeredforstable/successfulbuildsonly.Iobservedseveraldownstreambuildscopieddifferentversionsofartifactsfromupstreamproject.Duetoaheavilycontendedqueueittook~2minutestoschedulealldownstreambuildsusing{{hudson.tasks.BuildTrigger}}.Andastheactualschedulingisdonebeforeupstreamcompletes,severaldownstreambuildswasscheduledfastenoughtoobserveoldpermalinkvalue.
the
The
schedulingshouldtakeplace*after*upstreambuildisdone.Btw,Iwasnotabletofindanydocumentationfortheassumptionthatupstreamanddownstreambuildshouldnotoverlapintime.
Labels:
pipelinetrigger
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.
