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

PDF Books
Show collection (0 pages)
Collections help


Projects:Retail Backward Compatibility Tests


In multi-server environments it is quite possible that different systems are updated at different points in time. This means that our solution should be able to handle a situation where different versions are running together and interacting with eachother.

After internal design discussions (see documentation) the consensus is that we should follow the approach:

To support this approach we need to check and validate that the following architecture runs without problems:

The goal of this project is to result in an automated test build task which checks a webpos client of a previous release against a server from a newer release. This automated test build task does something like this:

The project will be done in 2 phases:

  1. in the first phase the idea is to prototype the approach and see what obstacles we encounter. The result of the first phase should be a document describing the steps to create the test environment and run the previous version of the tests. Also we need to know the interval of the build job (daily probably). This phase will be executed in the 16Q4 dev cycle.
  2. in the second phase the idea is to implement the ideas in a real build task which is integrated/run as part of the OB Commerce ci environment. This phase will be executed in the 17Q1 dev cycle.

The role of release management in the first phase is to discuss and give feedback. In the second phase the role of release management is larger as the new build has to be setup and run as part of the rest of the ci-jobs.


Tracking Issue

Retrieved from ""

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