Hi, I'm struggling to find a solution for issue reported against Xvfb plugin (https://issues.jenkins-ci.org/browse/JENKINS-14483). I cannot seem to find a solution that works both concurrently: so each matrix job doesn't overwrite process handle, and assuredly: so that all started Xvfb processes are terminated in the end.
Things that seemed to work but actually did not: - starting Xvfb process only for MatrixJob build instances - ended up overwriting process handle stored in the descriptor of the build wrapper, so in tearDown of substituted Environment only the last started process would be terminated - starting Xvfb process for MatrixBuild build instances, counting the number of MatrixJobs and decrementing the count in tearDown so when the count reaches 0 it's safe to terminate Xvfb - ended up not working (of course) too well for distributed master-slave Jenkins configurations I must be missing something here, is there no way to wrap each MatrixJob with it's own instance of BuildWrapper? If not is there a place I can store and later retrieve the process handle, or must I use a map to track my process handle variable with each matrix job -- the only thing I can think of that would sort-of work? Thanks, zoran -- Human by day user by night
