Build multiple branches about bigtuna

[antekpiechnik]

We somehow don't believe that each separate feature branch should be continuously tested. We always create a 'master' (stable) branch for testing and 'development' branch that we continuously test and merge all new features into the latter. If the development branch stays stable and we want the features merged into the master by the end of an iteration, we do it.

Also, the clarity of the project display would be disrupted if you saw the whole project fail even though it's only some small feature branch failing, and not the master.

Comments ?

[benfoxall]

I agree. I see CI as more about checking that code works together - rather than a tool for running tests online.

There is some mention in the wikipedia entry about committing to a baseline branch.

[DouglasMeyer]

I don't want to get into branching strategies or how to display such an approach, but I do see how testing every branch isn't all too practical, and even counter productive as some branches are created knowing that the build doesn't work on them.
It has been my experience that you would want CI running on at least 2 branches of a project. Branches like "master", "development", and any longstanding feature branches. It may not make the most sense to create a new Project in bigtuna, but the workflow makes sense. Would it be possible to clone a project (or a project's configuration) so when you are creating a new Project for one of these branches you can start with the same configuration/builds (as they will probably be mostly the same). I would consider this a separate issue, but I would like to hear what you think. Thanks!

[antekpiechnik]

Hey, I've implemented this functionality in the project_duplicate branch.

It allows you to duplicate a project with all the available configurations, so that you do not need to fill all the fields again.

Let me know if this somehow solves your issue.