tags:

views:

148

answers:

2

Question:

In the path HUDSON_HOME/jobs/<jobname>/builds/<timestamp>/workspace-files, there are a series of .tmp files. What are these files, and what feature of Hudson do they support?

Background

Using Hudson version 1.341, we have a continuous build task that runs on a slave instance. After the build is otherwise complete, including archiving the artifacts, task scanner, etc., the job appears to hang for a long period of time. In monitoring the master node, I noted that many .tmp files were being created and modified under builds//workspace=files, and that some of them were very large. This appears to be causing the delay, as the job completed at the same time that files in this path stopped changing.

Some key configuration points of the job:

  • It is tied to a specific slave node
  • It builds in a 'custom workspace'
  • It runs the Task Scanner plugin on a portion of the workspace to find "todo" items
  • It triggers a downstream job that builds in the same custom workspace on the same slave node
+3  A: 
Tomislav Nakic-Alfirevic
Summarizing that thread in your answer would be useful
Michael Donohue
Nothing in that thread directly applies; however, we are using task scanner. Looking into that now.
Patrick Johnmeyer
Point taken, Michael: I've extended my answer for anyone else who happens to run into the same issue.
Tomislav Nakic-Alfirevic
@Tomislav, I've made my answer community wiki; how would you feel about merging the two? I don't want to take credit away from your answer, but I do think that my answer as it stands is more complete and has room to grow. I would like to mark it as the "accepted" answer rather than leave both answers hanging.
Patrick Johnmeyer
You would like to add what I wrote to your community wiki answer? Sure, by all means.
Tomislav Nakic-Alfirevic
Eh, I couldn't figure out a good way to merge the two beyond my current link.
Patrick Johnmeyer
+3  A: 

In this particular instance, the .tmp files were being created by the Task Scanner plugin. When tasks are found, the files in which they are found are copied back to the master node. This allows the master node to serve those files in the browser interface for Tasks.

Per this answer, it is likely that this same thing occurs with other plug-ins, too.

Plug-ins known to exhibit this behavior (feel free to add to this list)

  1. Task Scanner
  2. Warnings
  3. FindBugs
Patrick Johnmeyer

related questions