Hi,
I have a compile job that runs continuously triggered by SCM which starts
about 40 or 50 test jobs after successful compilation.
I am printing the changes since last success (coming from the upstream
compile job) of a test job which is run after a compile job like this:
${CHANGES_SINCE_LAST_SUCCESS, showPaths=true, pathformat="%p"}
This has worked until I began to allow the compile job to run concurrently
because the feedback cycle was getting too long recently with compile times
of 6 minutes and test times up to more than 20 minutes and changes of more
than one developer getting mixed up into one build. Now it can happen that
I have several compiles before a special test is running again. Looking at
the build of the test Jenkins handles this correctly because it says:
No changes from last build. Changes in dependency
1. JobContinuous [image: Success]#9601 → [image: Success]#9605 (detail)
Clicking on details I get all changes summarized for those 5 builds.
The email only prints nothing. If there is a 1 to 1 relation between
compile and test, emailing the changes works.
Is this a bug/feature request? Am I doing something wrong there?
BR
Dirk
