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.
