On Wed, Oct 17, 2012 at 9:44 AM, David Weintraub <[email protected]> wrote: > 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.
I think that's a bug with 1.485, I ran into a similar issue. It seems to be better with 1.486. -Andrew > > -- > David Weintraub > [email protected] -- -- Andrew Melo
