-
Notifications
You must be signed in to change notification settings - Fork 3
Build
grammarware edited this page Jul 18, 2012
·
1 revision
Nightly/daily build systems have already become a common practice in software development: every once in a while (say, once per day) all tests are run on a snapshot of a software system, which is then compiled and deployed, with an overview of failed elements delivered to its administrators. However, it is not clear how to address build-related issues in a highly heterogeneous environment. What kind of testing is the most reliable and adaptable in the context of nightly builds? What if parts of the system need to be compiled on different architectures (i.e., Windows vs. Linux, Java 5 vs. Java 1, PC vs. Mainframe)? How to resolve dependencies in the case of distributed heterogeneous deployment?
- …
- …
TBA