Automated testing and continuous integration are established
concepts in today´s software engineering landscape,
but they work in a kind of isolated environment as they do
not fully take into consideration the complexity of dependencies
between code artifacts in different projects. In this paper,
we demonstrate the Continuous Change Impact Analysis
Process (CCIP) that breaks up the isolation by actively
taking into account project dependencies. The implemented
CCIP approach extends the traditional continuous integration
(CI) process by enforcing communication between CI
servers whenever new artifact updates are available. We
show that the exchange of CI process results contribute to
improving effectiveness of automated testing.