Specifically, the Text-finder plugin, a post-build task, executes before the build actions are complete.

Unfortunately, this is not always the case, which makes it difficult to diagnose and debug.

Given a simple job that does a wget -O - and a post build task that checks for DOCTYPE in the console output.

Under a simple Hudson instance with one slave running the above job runs without error.

Under a more complex Hudson instance with 34 slaves, doing the same simple job, can run perfectly for 24 hours every 3 minutes, and then suddenly fail 10 to 20 times in a row, and then start running again.

In the case where the job fails, the output from the text finder plugin is inserted into the middle of the output from the WGET and before the DOCTYPE is displayed.

Because the plugin executes before it should, it does not find what is (/will be) there, and fails.