[Owncloud] Continuous Integration Server for ownCloud projects

[Florian Hülsmann]

Hi Thomas,

I'm not familiar with CI yet, but would it be possible to let developers 
select any branch when running tests? Or do they have to be explicitly 
integrated with the system..?

I.e., I'm developing the notifications app in user_notifications branch 
but couldn't test it with PgSQL yet, which is possible with your CI 
system AFAIK.

Florian

Am 19.07.2012 22:28, schrieb Thomas Müller:
> Hi,
>
> the basic idea is to have one (or multiple) dedicated machines, which sole responsibility is to
> monitor source code repositories and in case of change perform build actions, run unit tests,
> prepare installer packages, generate nice reports and many more.
>
> What is the goal of this all:
> As soon as the code has been changed the ci-server ensures that it still compiles, no test
> case was broken in order to detect regressions as soon as possible and notify the developer(s).
>
> The ci-server for ownCloud is polling the git repos every 10 minutes to detect changes and triggers
> the action described in my previous email. All jobs are currently running on git master - other
> branches will follow once the job configurations are finalized.
> I'm using Jenkins (meanwhile the most common tools for the job I guess), because I know it for many years now.
> Currently there is one server taking care about all jobs but Jenkins allows a distributed setup, which is necessary
> as soon as cross platform compilations are necessary (e.g. Mac build for mirall) or simply there is too much.
>
> I decided to push the notifications to #owncloud-dev as we usually hang around there.
> If you see a message from the user owncloud-jenkins - ci is talking to you. ;-)
>
> As of today:
> [18:16:54] <owncloud-jenkins> Project ownCloud-Server(master) build #358: STILL FAILING in 5 min 37 sec: http://ci.tmit.eu/job/ownCloud-Server(master)/358/
> [18:16:54] <owncloud-jenkins> *  Robin Appelman: fix running test cases from browser
> [18:16:55] <owncloud-jenkins> *  Robin Appelman: allow a more flexible way of using user backends
>
> Together with the commit messages and the committers you see which project/job just finished, the duration,
> its status and a link to jump directly into the job.
>
> In case you see a job failing, jump in and try to find the solution and get in contact with the committers involved in this build!
> Currently the build for 'ownCloud-Server(master)' is failing due to a unit test within the zip file storage and some troubles I have with the code analysis tools.
>
> How can you contribute:
> Write unit test for the code at your hands!
> Fixing a bug? -> First write a failing test case, fix the bug and have a successful unit test. This will ensure, that the bug
> *most probably* will not a pear again.
> This approach will step by step increase the value of the test suite and increase the value of the ci-process.
>
> I hope this all made it a little bit clearer from the overall perspective.
>
> Still question - suggestions: hit reply - I'll do my best to dive deeper into explanations.
>
> Good night,
>
>
> Tom
>

-- 
Florian Hülsmann
<fh at cbix.de>
http://cbix.de