History   View   Links to this page Revision from: 2013 November 5 | 05:49 am
This is the revision from 2013 November 5 at 05:49 am   View the current live version of the article.

Introduction

The goal of this effort is to define a common set of resources, formats and RESTful services for Automation (Build/Test/Deploy) tools to interact with other ALM tools.

Approach

The specifications will be developed iteratively by first prioritizing scenarios and focusing on a minimal set of key scenarios. Once these scenarios have been satisfied by specification and proof of implementation, more scenarios will be considered.

Specifications

<

div class=”gutter media”>

Automation 2.0

Final Get started: __Primer__ | Reference: __Specification__ | **All 2.0 documents** | **Version** | **Status for 2.0** | --------------------------------------------------------------------- | ------------ | ------------------------------ | OSLC Automation Specification Version 2.0 | 2.0 | `final` | OSLC Automation Primer | `ALL` | `working draft` | Automation V2 Scenarios and Use Cases | 2.0 | `Note` | Automation Specification Version 2.0 Issues | 2.0 | `ongoing` | OSLC Automation Implementation Reports 2.0 | 2.0 | `ongoing` | RDFS Vocabulary | `ALL` | `final` Current Work ------------

Automation 2.1

Draft Get started: __Primer__ | Reference: __Specification__ | **Document** | **Version** | **Status for 2.1** | ----------------------------------------------------------------------- | ------------ | ------------------------------ | OSLC Automation Specification Version 2.1 | 2.1 | `working draft` | OSLC Automation Primer | `ALL` | `working draft` | Automation V2.1 Scenarios and Use Cases | 2.1 | `Note` | Automation Specification Version 2.1 Issues | 2.1 | `ongoing` | OSLC Automation Implementation Reports 2.1 | 2.1 | `ongoing` | RDFS Vocabulary | `ALL` |

<

div class=”bd”>

<

p class=”mvn pts icon-font-tinted” 4px; font-size: 36px”>Availability

Draft Reference: Specification

This is a thread of work being run in parallel to work on the main Automation specification.

Document Version Status
Availability Scenarios - The goal, scope and scenarios of the availability work unversioned Note
Availability Specification - Proposed changes to existing Automation specification, or new specifications. unversioned working draft

Work for future consideration

This section is to record work that has been identified as potential candidates for future work, such as scenarios deferred from previous versions. However, there is no commitment either to consider or to undertake this work.

Document Version Status
Automation V3 Scenarios and Use Cases 3.0 Note

Milestones

V3 Milestones (TBD):

Scenario Introduce Topic Complete Scenario Create Draft Specs Start Convergence Finalize Specs

Note: iterative specification validation will be occurring as the drafts evolve before finalization. The goal is to have at least 2 implementations of the specification before it is considered finalized.

Historical (completed) Milestones for V2:

Scenario Introduce Topic Complete Scenario Create Draft Specs Start Convergence Finalize Specs
Automation Linking Scenarios 22 Sep 2011 20 Oct 2011 3 April 2012 20 June 2012 V2.0 22 Jan 2013
Generic Automation Execution 20 Oct 2011 3 Nov 2011 3 April 2012 20 June 2012 V2.0 22 Jan 2013
Test Execution Scenarios 3 Nov 2011 10 Nov 2011 3 April 2012 20 June 2012 V2.0 22 Jan 2013
Build Scenarios 10 Nov 2011 18 Nov 2011 3 April 2012 20 June 2012 V2.0 22 Jan 2013
Deployment and DevOps Scenarios 8 Dec 2011 5 Jan 2012 3 April 2012 20 June 2012 V2.0 22 Jan 2013

Status

Meeting Agendas and Minutes

Mailing List

General Open Services
Automation workgroup