Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

To track changes in a Subversion jar repository, I have a Jenkins job that does a checkout, but no build. This way, anytime someone changes a jar, I get notified via the ext-email plugin.

I came in this morning, and only the last build is showing up. I don't have the job deleting the builds, and if I go into the Jenkins directory structure, I see all six build directories, and all the information is in those build directories.

I'm using release 1.485. Why would Jenkins not show the older builds if they're already in that directory? I don't delete old builds, and I can't think of anything else I have configured that might be causing issues. I do have the promotion plugin, but I'm not using that for this particular job.

Any ideas?

share|improve this question
I have the same issue with some of my jobs, unfortunately I don't have a solution. Have you had any progress on your side? –  Kleist Jan 21 '13 at 10:31
@kleist All I can do is a restart when this happens. Sometimes I can just get away with reloading the configuration. –  David W. Jan 21 '13 at 13:07
Thanks for the reply –  Kleist Jan 28 '13 at 13:16

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.