no I tried that it just injects a lot of zeroes somewhere in the label but (now I am just guessing a bit here because I fiddled with this before christmas and has had other things on my mind since) I got this feeling it was caching the setting somehow - so if I changed from 6 to 10 chars and tested it failed when using 8 chars - then I decreased to 9 then it worked with 8 but not 9 - baffling :) .
On Jan 30, 6:59 am, Ruben Willems <[email protected]> wrote: > Hi > > does adjusting the labelformat help? > setting it to 000000000 or something? > > with kind regards > Ruben Willems > > 2010/12/20 östen petersson <[email protected]> > > > i don´t get the defaultlabeller - is there someone who could shed some > > light? > > > <labeller type="defaultlabeller"> > > <prefix>$[sprintnumber|00].</prefix> > > <initialBuildLabel>0001</initialBuildLabel> > > <incrementOnFailure>false</incrementOnFailure> > > <labelFormat>00000</labelFormat> > > </labeller> > > > so I use a dynamic parameter to enable my team to set a tag on the > > build if it is a patch or so - but the labeller fails. > > > It accepts 6 chars but no more - and I can´t seem to find any setting > > that says this is the limit?? and when the input is not ok - it uses > > its internal buildnumber not the defaultlabel ie 27 instead of > > 00.0027 > > > or wait does this mean the parameter input fails for some reason? > > > <parameters> > > <textParameter name="sprintnumber"> > > <display>ange sprintnummer som prefix max 10 tecken</ > > display> > > <maximum>10</maximum> > > <required>true</required> > > </textParameter> > > </parameters> > > > anyone with a clue?
