Right now, we don't. There was no retention policy before I started. There most likely wouldn't be a collision; I'm assuming (and I'm still researching that) we're adding a digit to the year after 2015 so the build number would become six digits long.
So the last build in 2015 would be like FD313 and Jan 1 2016 would be 101011 I maybe forgot to mention that the day of the month is always 2 digits and is decimal. It's not my system, I just gotta work in it ;). If it were up to me, we'd just use the Jenkins counter and be done with it. Thanks! A Allen Fisher www.helpsystems.com<http://www.helpsystems.com> On Oct 17, 2014, at 11:28 AM, Marc MacIntyre <[email protected]<mailto:[email protected]>> wrote: Out of curiosity, how do you differentiate between build #1 on jan 1, 2017 (11111) and build #1 on jan 11, 2001 (11111)? On Fri, Oct 17, 2014 at 9:23 AM, Allen Fisher <[email protected]<mailto:[email protected]>> wrote: Hi List-- Working on a new project, taking an existing build scheme and rolling it into Jenkins. I have a peculiar build number scheme I need to implement: <Year in Hex><Month in hex><day><builds_today in hex> So a the 10th build on October 29, 2014 would look like: EA29A I'm guessing we add a digit if we go past the single hex digit (if we start over, I'm going to be pretty annoyed). The project moves pretty slow, so the last digit hardly every goes past 6 I've looked at the version number plugin, and it looks like it could do what I want, but it seems that I can't get a format string to do this. I'm fine running a script, but is there a plugin that would let me run a script and set the build number? Allen Fisher www.helpsystems.com<http://www.helpsystems.com/><http://www.helpsystems.com<http://www.helpsystems.com/>> _______________ Confidentiality Notice: This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ________________ -- 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 [email protected]<mailto:jenkinsci-users%[email protected]>. For more options, visit https://groups.google.com/d/optout. -- Marc MacIntyre -- 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 [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/d/optout. _______________ Confidentiality Notice: This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ________________ -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
