Re: overriding Project.upstreamProjects
On Mon, Feb 24, 2014 at 3:00 AM, James Nord (jnord) wrote: > No workspace --> no artifacts --> no fingerprints. Possibly the flow job type needs to be able to record artifacts from another build that it is referring to somehow. > // get the latest stable build of project X, project Y and project Z Since effectively you are doing something with those artifacts here. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
RE: overriding Project.upstreamProjects
> > there is no workspace and hence no upstream projects. > > Not sure what you mean. Upstream/downstream project relationships have > nothing to do with workspaces. No workspace --> no artifacts --> no fingerprints. > > it (and many other things) seem to be based around the assumption of > > fingerprints > > Rightly so. Why do you need to fake anything? Just make sure that whatever > information is passed from build to build is properly fingerprinted, and the > causal relationship will fall out of that automatically. But when you don't directly consume artifacts there is nothing to fingerprint. For example commit build --(triggers)-> flow build flow build is // pseudo code // get the latest stable build of project X, project Y and project Z // add them to RunParamters Build(testA, parameters) Parallel( build(testB, parameters), build(testC,parameters)) SO the flow runs multiple tests - and should aggregate these results so you only need to look at the "Flow" to see the test results - not have to drill into each project. On top of that - there is no point showing all the combined test results if you can't tell in the flow what changed from Run X to Run Y without having to drill into logs, and then search up and around in Jenkins. That is I want to be able to look at the "flow build" job and see all tests and dependency changes by just looking at the "job/flow_build" page. Hope that clarifies what I am attempting to achieve. /James -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: overriding Project.upstreamProjects
On Sun, Feb 23, 2014 at 10:09 AM, James Nord (jnord) wrote: > there is no workspace and hence no upstream projects. Not sure what you mean. Upstream/downstream project relationships have nothing to do with workspaces. > it (and many other things) seem to be based around the assumption of > fingerprints Rightly so. Why do you need to fake anything? Just make sure that whatever information is passed from build to build is properly fingerprinted, and the causal relationship will fall out of that automatically. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
overriding Project.upstreamProjects
Hi all, For the buildflow plugin upstream projects are not recorded - as in reality there is no workspace and hence no upstream projects. But this is not really the case - the flow could be retrieving a run and passing that as a parameter to many sub jobs - so I would like to be able to see the upstream changes (and aggregated results of the tests in the flow) in a single place. Whilst overriding getUpstreamProjects() would be possible - it (and many other things) seem to be based around the assumption of fingerprints, and I'm wondering if there is some fundamental reason why just overriding getUpstream wouldnlt work and if I really need to start faking fingerprint useage so that the main jenkins depenedency graph is in sync. Regards /James -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
