RE: [alf-dev] ALF SCM POC

["Tim Buss" <TBuss@xxxxxxxxxx>]

Hi Shalom,

 

I would say that the SCM vocabulary is supposed to embody the concepts that are common to most SCM tools.  It may be that some tools do not support a particular concept and thus may not provide an implementation of the related services

 

Yes an event for "user commit File" raised by SVN might look as you describe.

 

As to the POC, to link a stream with workspace requires some preconfiguration that can be looked up by the service flow.  This is not specific to the SCM vocabulary and is a good candidate for a Common service or perhaps a particular static use of the already proposed 'Relationship Store"

 

I'm a little unclear on the extended use case of multiple workspaces being associated with the stream for the purposes of build. One seems more likely but if there were many there would need to be some external indicator that you could use (eg its Tuesday so we do the full build but on Wednesday we do an incremental build) Such rules would come from some other store or service and are not part of the SCM vocabulary as such. This seems a little beyond what has been proposed of the relationship store. Maybe I'm missing your point? 

 

I'm not familiar enough with ClearCase to know if a view could help in that case but a point here is that an SCM might provide additional service that access concepts that go beyond the vocabulary and can allow for use cases that are beyond capability of the SCM vocabulary.  The idea of the vocabulary is to try to capture the likely use cases (say 80% or better)

 

Tim

---

From: alf-dev-bounces@xxxxxxxxxxx [mailto:alf-dev-bounces@xxxxxxxxxxx] On Behalf Of Shalom Kazaz
Sent: Tuesday, March 20, 2007 1:31 AM
To: alf-dev@xxxxxxxxxxx
Cc: Lior Kanfi
Subject: [alf-dev] ALF SCM POC

Hi Tim

I'm going through the 
vocabularies docs and have some questions, checking if I got it 
right.

For simplicity I will be specific with the SCM 
POC.
 
So, in very simple 
words, SCM vocabularies will be those data elements or information that is common and understandable by all SCM tools ?
For example, 
all SCM tools should know what a 'ChangeSet' vocabulary is.

The docs also mention an Extension section for event which, as I understand, is a tool's specific data, for example data relevant only for SVN. 
?

So a pseudo event for a "user commit file to SVN'" 
would look something like that:


  
<Base>
    
<EventId>EventId</EventId>
    ...     
  </Base>
  <Detail>
    <!—SCM 
Vocabularies -->   
    <CommitLogMsg>commit message</CommitLogMsg>
    <ChangeSet>change set 
id</ChangeSet>
  </Detail>
  <Extension>
    
<!-- Spesific SVN (I have no 
other ideas yet of specific SVN info...)-->
    <SvnUrl>http://some-url</SvnUrl>
  </Extension>



About the 
proposed POC use case 1: Most simple continuous integration 
build:

User checks in a file.
SCM fire a Stream Changed event
…
The service flow should create or update a preconfigured workspace to 
initiate the build.

When the SCM fires the event, it 
only has knowledge about the changed objects, there is no knowledge of a 
workspace.
I assume a "Stream Changed event" will always 
map to the same service flow, but it is not always the same project, or 
workspace to work on.
How can we link a "Stream Changed 
event" to a workspace? 
Maybe with clear case we can use 
the 'view' notion for that.
I hope I am clear with that 
question.


Thanks

Shalom






Shalom Kazaz
Tikal Knowledge
www.tikalk.com



**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.