RE: [alf-dev] RE: ALFSource Code Mangement Vocabulary

["Scott McGrath" <smcgrath@xxxxxxxxxxx>]

Mark writes:
<<< Imagine an event that comes in to do a build.  The service flow might
ask  the SCM tool to check something out to some location, and perhaps
produce  some kind of change log using a history method.  Then, assuming
success,  it moves on and asks the build tool to build what is in that
location  etc...  So the build tool did not have to communicate with the SCM
tool, but there is still some shared information that the user provides like

where to do the build from, the build script, where to look for the change 
log etc...

ALF provides the automation and it reduces the needs for the various tools 
to directly integrate with each other. >>>



This is an interesting case because there are properties and values that
tools should and will exchange but there are also dependencies, as when the
SCM tool might detect conditions that should prevent a build from executing.
A common case we see is where a trigger or other SCM process from a
developer workspace "pre-builds" a change package and if the result does not
meet build criteria, a promotion, update, what have you, should fail until
the issue is resolved. There's probably quite a bit of messenging to take
place between the SCM tool and the build environment in that instance and a
lot of potential for vendor specific application logic on both sides. 

The cases do run the gamut from a simple "share these properties and data"
to "evaluate and start/stop this dependent event from occuring".  Both types
of event transactions need to be supported, and I agree they're different
from a "level of integration" point of view. It seems like the tricky part
of vocabulary production is determining how deep the event management
extends into this kind of integration space. The goal seems to be to
insulate vocabularies from one another's domain expertise, but we do need to
enable the interoperabilities that matter to the overall workbench. 

Scott


Scott McGrath | Senior Product Manager 
AccuRev, Inc. | www.accurev.com
781.325.0652w | 617.834.2339m 
 
 
-----Original Message-----
From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx] On
Behalf Of Mark Phippard
Sent: Wednesday, May 03, 2006 5:16 PM
To: ALF Developer Mailing List
Subject: Re: [alf-dev] RE: ALFSource Code Mangement Vocabulary
Meeting+1-303-928-3232id 6053141# Wednesday 10:00AM PDT - meeting minutes