[alf-dev] Build Vocabulary Meeting Minutes

[alf-dev] Build Vocabulary Meeting Minutes

Title: Build Vocabulary Meeting Minutes

Below are the combined minutes for the 6/12 and 6/19 meetings.

Attendees:

Steve Taylor

Jim Graham

Tim Buss

Doug Fierro

Brian Carroll

Eric Minick

1. Scope of a Build

We agreed that a Build is the compile and link process, even if there is some minor

processing done such a file copies. Actions like the check-out from SCM or Testing

are outside of the Build itself. Those Actions are part of the Build Service Flow but not part

of the Build.

2. Reviewed the initial Build Use Cases. See http://wiki.eclipse.org/index.php/ALF/Build_Use_Cases for details.

3. Need to add the following use cases to the Wiki:

- Approved for Build

- Human Interaction (ie. log review before service flow continues)

- Dependency Management

- Impact Analysis

- Bill of Material Reporting

- Continuos Build

4. Identified the need for persisting state related information in the service flow.

5. Identified the need for Logging/Reporting mechanism to deal with consolidating the

Build Logs and Reports for the End User. The information itself may not need to be persisted but

links to it should be.

6. End User construction of Service Flows:

a. Small number of Service Flows that can be reused by passing parameters to them.

i. Outstanding issue - What interface would be used to fill in the parameters.

b. Specific Service Flow for each Project, location and type of build

i. Many service flows

ii. Hard to change items in common.

Conclusion:

Parameterized Service Flow would be best for the End Users but the End Users can create

specific Service Flows if they choose to do so.

Next Call:

6/26 - 1PM CDT

Teleconference: 913-227-1219
Code: 176934

Agenda:

Drill down into the Build a Change Request Use Case

--

Catalyst Systems Corporation

Ph: 800-359-8049 x114
505-424-6439
Fax: 505-424-6438