Build Manager

With Validata SAS you can manage any number of builds whilst always choosing the right version and release for each component. When creating baselines, you can keep track on the status of the work, requirements coverage and source versions. With a single repository storing the baselines of all development projects, all testing baselines and the production baseline, you have a unique chance to organise all your deployment packages and put order and transparency in uploading process to different environment.

Creating baselines is facilitated by various build checks that ensure the integrity of builds. Baselines can be later used for trial deployment or sharing built components between development teams. Throughout these processes, Validata SAS provides detailed error logs, warning messages and build conflicts information.

Deployment and Rollback

Validata SAS helps you achieve automated and repeatable deployment via a centralised process. You select the build and click your way through a wizard to deploy it on the target environment after making consistency checks for deployment packages. If deployment fails Validata SAS automatically rollbacks the already deployed source components.

Reality is that too often different teams need to share one and the same development environment. Whenever a deployment by one team breaks the system, you select it and perform rollback. The system keeps track of every deployment executed on each environment, the user who executed them and the date.

Impact and Change Analysis

Assessing the impact of change prior to any code development is critical in managing an efficient development process. Within Validata SAS, we provide the following functions:

Impact Analysis

It is very important to know the impact of your decisions and what to include in the product build (Baseline) and what will happen if you exclude the particular piece of work (Task). Validata SAS gives you a detailed report of the exact impact over the product sources not only limiting you to what will enter and what not, but also comparing the versions of the files which will enter.

Change Analysis

Each Product consists of components. In most cases these components are not independent but are related to each other. In Validata SAS you can define the dependencies for each component of your product and see how affecting one of the components will reflect on the others.

Conflict Management

In dynamic development environments, where several teams are working in parallel on the same product, it is inevitable that you will have programming conflicts. A conflict may occur when you merge content from different baselines or when you inherit content from different Streams/Release iterations, or when you use a combination of both.

For situations when Validata SAS cannot automatically determine the right units and unit versions that should be included in the configuration you will be able to reconcile the conflict using the following options:

• Merging the conflicting versions into a new one
• Overwriting one of the files’ source code with the other one
• Excluding one of the versions from the configuration
• Check in the file without merging, which will create a branch of this file.