View source | View content page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

Projects:Retail Automation Quarantine

Contents

Introduction

The goal of this project is to improve the quality of the results given by the Retail Continuous Integration and Retail Try

To achieve this goal, one of the proposed actions, is to create a Quarantine group of jobs in which new tests are verified to be stable before they are added to the final automation executions

Reasons to have a Quarantine Automation Integration:

There are still some other reasons why the Integration could fail, being the main one, that the changesets added to the final repositories, do not pass the integration with the final repository status. This flaw in our flow, allows different changesets that individually have passed try, to break the application when pushed together.

New tests can break existing tests

There are some reasons why new tests can make existing tests to fail

Tasks

Flow chart

QuarantineFlow.png

Fulfilled tasks

Sorted tasks todo

Stage 1:

Stage 2:

Required from the RM team

Required from the Retail team

Caveats


Issue

https://issues.openbravo.com/view.php?id=0033365

Anex

Retrieved from "http://wiki.openbravo.com/wiki/Projects:Retail_Automation_Quarantine"

This page has been accessed 575 times. This page was last modified on 13 July 2016, at 17:29. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.