I have a pom only project that is built by Jenkins.  The only thing it 
really does is send it to my repo.  This is used by several other projects. 
 For some reason, Jenkins is not keeping these builds. It even seems to be 
deleting the workspace.  The subversion polling log shows: "No existing 
build. Scheduling a new one."  This triggers a new build, which triggers a 
new build for all downstream projects.  Could this be because there are no 
files generated during the build?  I do NOT have "Delete old builds" 
checked in the project config.  Any ideas?

-- 


Reply via email to