[Anthill-pro] Stamps & Properties
Eric Minick
etm at urbancode.com
Fri Jan 11 09:40:22 CST 2008
We just have two stamps really. We have a dev stamp that gives a number like
DEV-3200 and then a release stamp where we pull a market friendly number out
of thin air and apply it to an existing release candidate.
-- Eric
On 1/11/08, Yanko, Curtis <curt_yanko at uhc.com> wrote:
>
> Besides, what's the point of having Build life sand then giving it lots
> of different Stamps? What do you guys do?
>
>
> ===
> -Curt
> W: 860.702.9059
> M: 860.881.2050
>
> -----Original Message-----
> From: anthill-pro-bounces at lists.urbancode.com
> [mailto:anthill-pro-bounces at lists.urbancode.com] On Behalf Of Eric
> Minick
> Sent: Thursday, January 10, 2008 6:13 PM
> To: AnthillPro user and support list.
> Subject: Re: [Anthill-pro] Stamps & Properties
>
> Curtis,
>
> Build:
> 1.0.0.${+property:value}
> Dev:
> DEV-${bsh:StampLookup.getLatestStampValueForStyle("BLD")}
> QA:
> QA-${bsh:StampLookup.getLatestStampValueForStyle("BLD")}
>
> Does the perpending of BLD/Dev/QA to the build number actually buy you a
> whole lot though when the status is already there? Is there a lack on
> Anthill's part of making a build's status obvious enough?
>
> -- Eric
>
>
> Yanko, Curtis wrote:
> > All,
> >
> > I am trying to figure out a strategy for my stamping. My intent is to
> > generate stamps that are used as labels and represent the promotion
> > level. So I have something like this:
> >
> > BLD-Major.minior.bug.build
> > DEV-Major.minor.bug.build
> >
> > So I set up in my stamping strategy something like this
> >
> > Build BLD-1.1.0.${+property:BuildNum}
> > Dev DEV-1.1.0.${property:BuildNum} <----- Notice no increment
> >
> > but the problem is I'm still referencig my BuildNum which amy have
> > changed. So I'm considering dropping the BLD or DEV and just
> > pre-pending at Label time or figuring out how to save BuildNum for a
> > particular buildlife and use that.
> >
> > Thoughts?
> >
> > I'dalso be interested in hearing about other strategies people have
> > come up with.
> >
> > ===
> > -Curt
> > W: 860.702.9059
> > M: 860.881.2050
> >
> >
> > 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.
> > ----------------------------------------------------------------------
> > --
> >
> > _______________________________________________
> > Anthill-pro mailing list
> > Anthill-pro at lists.urbancode.com
> > http://lists.urbancode.com/mailman/listinfo/anthill-pro
> >
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
> 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.
>
> _______________________________________________
> Anthill-pro mailing list
> Anthill-pro at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080111/b2904fc4/attachment-0001.htm
More information about the Anthill-pro
mailing list