I answered my own question. Looks like the build numbers align between the top level jenkins job and the underlying jvm-specific version. I wonder if this is only coincidence as anyone can kick off manual builds on either of the sub-jobs.
-n On Mon, Aug 17, 2015 at 10:45 AM, Nick Dimiduk <[email protected]> wrote: > Hi folks, > > Looks like some nice work happened in Apache Jenkins around the 1.2 branch > (Sean's hand, I assume). Kudos! > > Is it possible to have the console output of the top level job to link > directly to the console output of the JVM specific version run? Right now > the lines "Triggering latest1.7,Hadoop" and "latest1.7,Hadoop completed > with XXX" are linking only to that job's overall build history, not to the > specific build invocation. > > I can investigate this myself if the cycles are not available at the > moment, just thought I'd raise the question. > > Thanks a lot for the work in this area. > -n >
