[Anthill-pro] Anthill3 rc1.b6 - notification & stamping
Eric Minick
etm at urbancode.com
Tue Oct 3 14:26:41 CDT 2006
Hi Patrick, I've included my answers inline.
> 1. I am getting this message in an email from the notification I set
> up, in the subject line: Workflow: FRED-Client-Server-GRP -
> BUILD-FRED-GRP ($workflow.BuildLife.LatestStamp.StampValue): Success
>
> How do I correct this?
>
It looks like the stamp might not exist. Has this build life ever been
stamped?
> 2. How do I set up a group of recipients for email notification?
> Would I create a new user generator and create a new script within
> it? If so, how would I code this script?
>
Exactly right. This is actually the example covered in the built in
apps. From the application, there's a 'help' option in the upper right
hand corner. Open that link into a new window. The item you're
interested in is "Configure Notifications" under the Tutorials category.
There's a User Generators subsection with an example script. The key is
that you can only email Anthill Pro 3 users, so you'll need to make sure
everyone is in the system with their email addresses set.
> 3. I would like to add a few items to the email notification, I
> am passing in two properties; release and level, I also use version in
> my ant script, I would like all of these in the email notification. How?
>
If stamping was happening properly, I would think that this would be the
same value as the stamp applied by the build workflow:
$workflow.BuildLife.LatestStamp.StampValue
> 4. I have a project with one originating workflow and 6
> non-originating workflows, the originating workflow has a stamp
> assigned to it. The non-originating workflows do not have the option
> of assigning a stamp to them, is there another way to do this? Future
> release? Or work around?
>
A generic workflow can have a 'Create Stamp Step'. This will let you
pick an appropriate stamp style (probably one for each workflow) to
apply at the end of the non-originating workflow. The mapping between
the stamping style and a stamping strategyh (which holds the current
build number / stamp) is done on the originating workflow and should be
inherited down the build life.
>
> Thanks for your help,
>
> Pat Curley
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Anthill-pro mailing list
>Anthill-pro at lists.urbancode.com
>http://lists.urbancode.com/mailman/listinfo/anthill-pro
>
>
More information about the Anthill-pro
mailing list