Thanks, Chad.
What I am really after is the feature in TeamCity that allows you to
have different "configurations" of each project. Each configuration is
basically a sub-project under the main project, and can call a different
script or target in a script. But they share the same source code
checkout and are logically grouped. So for example you might have
Project Foo with Release and Debug configurations that are all grouped
together on the console screen.
I can of course achieve the same thing using separate projects, which is
what I am doing, and that works fine.
Ben
Chad Woolley wrote:
On Tue, Oct 21, 2008 at 9:49 PM, Ben Greenberg
<[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I am wondering if there is a way to have more than one build
possibility for a single code base without having to set up a
second project. The manual hints at this with the
"MyProject.Quick" and "MyProject.BigBertha" examples when showing
how to use case project.name <http://project.name>, but the only
way I have gotten this to work is to set up a separate project
using the same source repo.
First, I would ask why you don't want to set up a second project?
That's definitely the easiest way.
If you want to use the same project, you could switch on some other
variable besides project name (time of day, day of week, phase of the
moon). However, that would be kind of wierd, from the standpoint of
having a consistent build. The specific downside is if a build is
green then goes red, you don't know if something broke in your smaller
suite, or if something broke in your bigger suite - at least not
without looking at the build output.
-- Chad
------------------------------------------------------------------------
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
