Given that the timing loops in jenkins put a lower bound of 100ms or so before a build starts, unless you have a very large executor pool and enable concurrent execution I suspect that the build numbers will be safe for us from overflow... unless somebody finds a fountain of youth!
On 29 May 2014 13:30, Daniel Beck <m...@beckweb.net> wrote: > > On 29.05.2014, at 13:37, wak...@comcast.net wrote: > > > would be a build number reset at some point ? > > Well, it's an int. After build number 2.147.483.647 it wraps around to > -2.147.483.648 and Jenkins basically breaks, failing to show these builds > on the UI. > > Not sure this is a relevant limitation though. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
