I didn't have 40 builds -- I only had 5 AFAICT and there is only one good one there. (Oddly they're listed twice.) I had tried wiping out the workspace but to no avail. But deleting the prior (5) builds appears to have taken care of it even though there was only one good build.
On Apr 14, 2010, at 5:26 AM, David Carver wrote:
As I already suggested, the easiest way is to just delete the old
builds, and let it start with the numbers it wants. Also, really, to
help conserve disk space and play friendly with the other builds that
need to use the build machine, you shouldn't be keeping 40 builds and
their artifacts around. At the most 10 should be sufficient and give a
fairly good idea of the quality of the builds.
Dave
On 04/13/2010 11:42 PM, Stéphane Bouchet wrote:
Miles,
i got it too and i build mannually since build number reach the correct
one.
if i remember well, there is also a file that host the buildnumber
inside the job directory in the eclipse server :
sbouchet@build:~> cat
/opt/users/hudsonbuild/.hudson/jobs/cbi-emf-eef-0.7-nightly/nextBuildNumber
378
sbouchet@build:~>
you could try to modify it ( i did not do that myself, so i am not sure
it will work ! )
Miles Parker a écrit :
Hi,
It definitely seems like something is fubar'd with cbi-amp-nightly.
When I trigger a new build it tries to create a build earlier than the
last build, i.e. 371 when the last good build was 413. Is there someway
to reset things or increment the build numbers so that I can get to a
good build number? Short of manually running 40 bad builds that is...
thanks,
Miles_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev
_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev
|
