build.kde.org and branches

[Torgny Nyblom]

Hi,

I'm having issues with handling different branches for the CI bot at 
build.kde.org.

Hence I'm asking what you think is the correct way of handling them.
As I see it there are some alternatives:
1: One job per project and let that job mix results from all built branches 
(Jenkins style)
2: One job per project/branch combination.
3: Only build one branch per project.
4: Some combination that we define and implement.

What do you think we should aim for?

/Regards
Torgny
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-buildsystem/attachments/20111012/06a42da7/attachment.sig>