Community
Participate
Working Groups
From "watching" our build logs, it appears to me the main build completes, and then there is at least 20 minutes of waiting for a couple of "post build" steps to complete. So, first of all, I should put in some "timing" points, to measure how long each step takes. The primary candidates for "post-post-build" work are the "API reports" and the "repository reports". That is, in theory, the build could be uploaded, and perhaps the JUnit tests started, while the API Reports and "repository reports" continue to be done on build machine, and then they be uploaded after the main build. There are some debatable cases that will take some investigation. For example, the "comparator reports" and "dirty tree" reports are done in the post-build steps, but there are JUnit tests that depend on them being available. I am not sure if "by the time the tests run" they would be available, or if the tests could be modified to "wait a while" if not available (say, 10 or 20 minutes). Those steps I do not *think* take very long, but, that's why taking some measurements first is important. The whole goal of this enhancement is to main the main build available a little sooner than it otherwise would be. Then again, timing data will be needed to know how much earlier it would be. 10 or 15 minutes probably not worth much effort, but if it would be 20 minutes or more, then probably so.
