| [hudson-dev] General newbie question (projects + job executions) |
|
Hi, I am very new to Hudson and as a matter of fact I am new to
using CI. I am looking into setting up Hudson, but have a couple of
general design questions. 1.
I have projects where each project encompass a number
of different components/parts where each part is being developed by a different
set of developers. What is the best way to model that in Hudson? 2.
The "test" job/script that need to be done for
some of these components can be huge tasks and the job need to submit to a
virtual farm for "execution". Is that possible? How do
you approach that? It sounds like I like to install some execution
agent/broker in the server farm side to make this happen. 3.
Do you manage the development + main + release branches
all in the same CI server or do you manage them in separate CI? How do
you model it such that the main is "build" from the development?
How do you make such build that by default it is only on a successful build
(without error) from the development, but allow certain users to override it? Thanks… --Chung |