Skip to main content

Advances, Systems and Applications

Table 8 Comparison of different aspects in which the Cases are alike

From: Degrees of tenant isolation for cloud-hosted software services: a cross-case analysis

Aspects

Case 1- Continuous integration

Case 2 – Version control

Case 3 – Bug tracking system

Generation of additional data

Archives the results of all the builds it performs, by default

Creates additional copies of files which occupies space

No additional copies created except bug attachments

Use of Locking

Used to block builds dependencies from starting if an upstream/downstream project is in the build queue

Used to prevent clashes between multiple tenants operating on the same working copy

Used to prevent clashes between multiple tenants trying to access the bug database

Use of back-end Storage

stored data native OS Filesystem directly

Mostly stores data on native OS File system directly (occasionally on database)

DBMS or database library

Use of disk saving strategies

Configure system to discard old builds

Transfer differences between versions instead of complete copies; concatenate files into a single pack

Purge error files and log files

Use of Web Server and Runtime Library

Java Runtime Environment (JRE) and JVM

Apache Portable Runtime (APR)

Mod_perl and mod_cgi

Size of users and project

Multiple developers triggering multiple concurrent builds

Multiple developers access working copy of a project

Multiple developers and testers submitting and corrects bugs

System Load and CPU

Low consumption

low consumption (could be high during delification, data compression)

Average consumption (could be high depending on runtime library used)