This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
AutomationHome
>
AutomationMeetings
>
AutomationMeetings2010Mar05
(19 Mar 2010,
LeighWilliamson
)
(raw view)
<h3 style="border-style: solid; border-color: #e2e2e2; border-width: 0px 0px 1px; margin: 1.25em -10px 0.35em; padding: 0.25em 10px; font-weight: bold; line-height: 1em; font-size: 18px; display: block; height: auto; background-color: transparent; color: #630000"> </h3> ---++ Date: 5 March 2010 ---+++ <a name="Agenda"></a><a name="Agenda_"></a>Agenda: * Review Action Items from Previous Meeting * *Robert* to update the Mylyn Scenario to use the Automation terminology * *Robert* to create a Google Spreadsheet to share attributes of the different resource definitions * *Leigh/David* to update the IBM Scenario to use the Automation terminology * *ALL* take the scenarios to the next level of detail... understanding roles of consumer/providers * Agree on scenarios * Start to identify the roles of the consumers/providers in each of the use cases * Identify how the different known products align with the resource definitions initial thoughts (Build Forge and Jazz Team Build at a minimum) ---+++ <a name="Minutes"></a><a name="Minutes_"></a>Minutes: <u>Attendance:</u> Dave Johnson (IBM), Leigh Williamson (IBM), Nick Crossley (IBM), Peter Birk (IBM), Robert Elves (Tasktop), Scott Bosworth (IBM), Jeff Turnham (IBM), Marcelo Paternostro (IBM) <u>Regrets:</u> David Brauneis (IBM-Lead), Jean-Michel Lemieux (IBM), Paul Tasillo (IBM) * Review Action Items from Previous Meeting * *Robert* to update the Mylyn Scenario to use the Automation terminology * *Robert* to create a Google Spreadsheet to share attributes of the different resource definitions * *Leigh/David* to update the IBM Scenario to use the Automation terminology * *ALL* take the scenarios to the next level of detail... understanding roles of consumer/providers * Workgroup reviewed proposed resource definitions using Google spreadsheet provided by Robert Elves. * Resource attributes need additional meta-data such as whether the attribute is required or optional, unique or non-unique, and so forth * Notes on specific attributes: * Applies to most(all?) resources: * Id : "ugly" identifier for resource - usually a UUID or similar (required, unique) * key : user friendly identifier (optional but must be unique if present) * summary : text label for resource (required, but can be non-unique) * web url : link to browseable GUI for resource (optional ?) * Applies to AutomationPlan resource: * dependent plans : list of automation plans that this one is linked with (chained plans, child plans, etc.) * Applies to AutomationResult resource: * automationPlan : link to plan that was executed in order to produce this Automation Result - the idea is that a query can be defined to return the list of all AutomationResults produced by executing a given AutomationPlan * reason : why was this execution of the plan triggered? Enum values: scheduled, manual, etc. * state : what is the current running lifecycle state of this execution? Enum values: pending, started, complete, etc. * verdict : what is the status of the execution? Enum values: failed, successful, etc. * Question was raised about how to handle the concept of versions of the Automation Plan * Action items for next meeting: * Nick Edgar to update the spreadsheet with resource equivalents for RTC that map to proposed resource definitions (DONE) * Leigh Williamson to update the spreadsheet for Build Forge (not done due to lack of edit permission on spreadsheet)
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r4 - 19 Mar 2010 - 11:34:41 -
LeighWilliamson
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback