[Anthill-pro] Stamp Style Script

[Steve Boone]

An example of when you might script the stamping step could be when on some
builds, you want to manually specify the stamp.

So, you might have a build workflow that has a workflow property, and the
person who starts the build inputer "FINAL 3.14.6"  The script would know to
take that property as-is and make the stamp.

If nothing, was entered for the workflow property, the script would take the
previous value if the stamp, and increment it.

Scripting just adds a little more flexibility to the stamp step.  It all
depends on how you want to label your builds.

If you would like to see an example of one, let me know.

Cheers,
Steve

On 1/31/08, Mathew Joseph <mjoseph at bravurasolutions.com> wrote:
>
> Steve,
>   I managed to find a temporary solution to the problem..
>
> In the library workflow I stamp it against a constant stamp, say Prod.
>
> In each of the workflows, I have the Prod stamp referring to a different
> property depending on what kind of build it is..
>
> So I have a Branch Stamp property and a Trunk Stamp property
>
> I make prod point to Branch Stamp property in Build Branch and so on.
>
> This does work for me adequately, although I am wondering when I would
> require a script at the apply stamp step..
>
>
> -----Original Message-----
> From: Steve Boone <sbb at urbancode.com>
> To: mjoseph at bravurasolutions.com, AnthillPro user and support list.
> <anthill-pro at lists.urbancode.com>
> Subject: Re: [Anthill-pro] Stamp Style Script
> Date: Mon, 28 Jan 2008 11:22:47 -0500
>
> Mathew,
>
> Can you pass along your script?
>
> It sounds like your script should check to see what environment  the
> workflow is using, and then apply the correct stamp based on that
> environment.
>
> I do not know what you are using the active Stamp for?  Does this just
> get the Dev or Prod stamp, and obtain its value?
>
> Regards,
> Steve Boone
>
> On 1/23/08, Mathew Joseph <mjoseph at bravurasolutions.com> wrote:
>         I have just begun to start using libraries and reusing jobs. I
>         have
>         setup a build job in a library and this build job has a step
>         which
>         stamps the build.
>
>         the workflows that use this job however need to put different
>         stamps. So
>         if i run a build dev workflow, it should stamp with the dev
>         stamp and
>         when i run the build prod workflow it should stamp with the prod
>         stamp.
>
>         i have defined both prod stamp and dev stamp as properties in
>         the
>         project.
>
>         and i have another property called activeStamp which i have set
>         to Prod
>         or Dev from within the workflow properties as the case may be.
>
>         In the build job, i use a script to select the stamp style
>
>         return PropertyEvaluator .resolve ( "activeStamp" );
>
>         Should I be returning an object of type StampStyle for this to
>         work?
>
>         is there any other way to do this?
>
>         --
>         Regards,
>         Mathew Joseph
>         Build & Release Engineer
>         Bravura Solutions
>         _______________________________________________
>         Anthill-pro mailing list
>         Anthill-pro at lists.urbancode.com
>         http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
> --
> Regards,
> Mathew Joseph
> Build & Release Engineer
> Bravura Solutions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080131/6bdfeec1/attachment-0001.htm