[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [alf-dev] ALF SCM Vocabulary and SCM events
|
Hi Tim,
thanks for your tips.
For your questions:
- What we are trying to achieve is to capture the commit
action in an SCM system. We have done this for SVN on the server side by
implementing SVN repository hooks. It is more comfortable capturing events from
a single point rather than capturing from clients. But I am not sure if it works
for all SCM tools. So in my case the events would be coming from
ALFSCMServer.
- As I mentioned earlier, we are currently using ALF
seriously. We are also in progress of integrating build and test tools. But I am
not sure if we can make formal vocabulary proposal at this phase. What we are
currently doing is: we use the types which exists in ALF vocabulary schemas but
we use the custom extension element in the event. Maybe in the coming weeks, we
can discuss more about the vocabularies when we get some more
experience.
Y.
Hi Yetkin,
Note: even though the ALF doesn't say so, I recommned
using XML NCNames for the Event values such as EventType and ObjectType
(basically alfa-numeric - no spaces or punctuation
marks)
There are two ways to proceed.
1. propose the event for the vocabualry. If you
are serious about this then probably it should be a bit more
formal.
2. use a custom extension than may be specific to your
solution. Custom solutions should use the <Extension> element rather
than the <Detail> element
I'm not quite clear what you are trying to achieve
and whether this event would come from the ALFSCMServer or the
ALFSCMWorkspace.
Conceptually a "commit" comes from a workspace but
actually changes the server.
I might expect the event from the server to
be be
Event type: ElementsCommitted
Object Type: Branch
The workspace could raise a commit event also but I
think the event name might be more specific to the action. Logically it is
same "eventType", just from a different source. So rather then the genric
WorkspaceChanged I suggest the following.
Event type: ElementsCommitted
Object Type: Workspace
In either case it seems
reasonable that the Detail (if you are going to propose this as the SCM
vocabuarly and follow that) or Extension (if you are not) would contain a
ChangeSet element as you describe.
Let me know if you want to
propose the event definition for the vocabulary.
Tim
I assume you are refering to these
types
<xsd:complexType
name="ElementVersionType">
<xsd:sequence>
<xsd:element
name="ElementVersionID" type="xsd:string"/>
<xsd:element
name="ElementVersionName" type="xsd:string"/>
<xsd:element
name="ParentElementID" type="xsd:string"/>
<xsd:element
name="AuthorUser" type="UserIDType"/>
<xsd:element name="Content"
type="ContentType"/>
<xsd:element name="VersionTimestamp"
type="TimestampType"/>
<xsd:element name="VersionComment"
type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType
name="ElementVersionCollectionType">
<xsd:sequence>
<xsd:element
name="ElementVersion" type="ElementVersionType" minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType
name="VersionCollectionType">
<xsd:sequence>
<xsd:element
name="VersionCollectionID" type="xsd:string"/>
<xsd:element
name="VersionCollectionName" type="xsd:string"/>
<xsd:element
name="OwnerUser" type="UserIDType"/>
<xsd:element
name="CreationTimestamp" type="TimestampType"/>
<xsd:element
name="CreationComment" type="xsd:string"/>
<xsd:element name="Versions"
type="ElementVersionCollectionType"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType
name="ChangeSetType">
<xsd:complexContent>
<xsd:extension
base="VersionCollectionType"/>
</xsd:complexContent>
</xsd:complexType>
Hi,
thank you for your response.
As I mentioned earlier in my mail, we are currently in
progress of integrating SVN. The only event that we are now interested in is the
SVN commit event. The event contains basically the following
data:
Event type: Changed Workspace
Object Type: Workspace
The <detail> element of the event contains a single
"ChangeSetType" complex type (inherited from the SCM XSD).
I am not sure if this was a good idea, so I wanted to ask
your opinion:
we have mapped the following information the fields of the
ChangeSetType type
OwnerUser -> user which performs the
commit operation (SVN author)
VersionCollectionID -> Revision
ID
CreationComment -> Commit comment
CreationTimeStamp-> Time of the commit
ElementVersionType[] -> an array of commited files. where
Content
-> Path to the resource
??? -> action mode. E.g.: U: Update, A:Added,
D:Removed
So, once we are sure about the contents of the event and
you agree, we can create a custom event schema based on this
information.
Regards,
Yetkin
Hello Yetkin,
The SCM vocabulary is preliminary
and so far does not explicitly define its
events. Probably the best way forward would be for you to propose the
event data a bit more formally for the events you are
interested in. Generally you should follow the types defined in the
SCM vocabualry as far as is practical. With that data I should be
able to work up an example and with your help we can extend the SCM proposal to
include events.
As a
brief guide, generally data that may be available from any tool
supporting the vocabulary would be sent inside the <Detail> element and data that may be specifc to a
particular tool would be sent in the <Extension> element. The vocabulary elements contained in the Details
element can also be designed to be extensible allowing tools to pass additional
related data that is not defined by the
vocabualry.
Event
declaration is described more fully in the wiki
here
Looking forward to
hearing from you.
Tim
Buss
Hello Yetkin,
Glad to hear of your interest. You are generally
looking in the right areas on the ALF WIKI. I've asked Tim Buss,
the ALF Lead Architect, to respond since he has been driving the work with ALF
Events.
Regards,
Brian
Brian
Carroll | Eclipse ALF Project Lead | Serena Fellow
(O)
(503) 617-2436 (C) (503) 318-2017
Hi,
I am new to this
group but not to ALF. We have been trying to integrate our tools with ALF since
more than 6 months. We are using the ALF event manager with BPEL support to
configure our workflows.
As a next step, we
want to comply with the existing ALF vocabularies especially with the SCM
vocabulary. I have looked at the SCM schema. But the schema is not as I
expected. I was expecting to see something similiar to the sample in the
"Event Decleration Schema" article (http://wiki.eclipse.org/ALF/Vocabularies/Event_Declaration_Schema)
where the event type, object type, extension fields of the event would be
restricted. But the SCM schema defines some elements but does not attach them
with the event base schema. I am a little bit confused here. Is it expected
that, I create an event schema based on the SCM vocabulary by following the
instructions in the "Event Decleration Schema" article or do you already have
something for that, which I could not find.
To make it more
clear, I want to emit an ALF event when a commit operation occurs in SVN. The
event should contain information like the author, log (comment), changed files
and timestamp etc. I want this event to comply with the ALF SCM vocabulary.
I would
appriciate if you can send me some sample events.
PS: I am sending
this mail in the mailgroup instead of the newsgroup, because I have a feeling
that the alf newsgorups are not active. Just tell me if I should send somewhere
else.
Regards,
Yetkin Oezkucur
Sr. Software Engineer
yetkin.oezkucur@xxxxxxx
Strassburger
Str. 34
09120 Chemnitz
Germany
Tel:
+49(0)371.523.02.12
Fax: +49(0)371.523.02.11
Registergericht/Registered
Office: Amtsgericht München HRA 72107 Geschäftsführer/General Manager: Arthur
Allen Umsatzsteuernummer/VAT No.: DE 192144187
ASG
| www.asg.com
Beyond
BSM
P
Please consider the environment before printing this
email.
**********************************************************************
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.
**********************************************************************
