- This topic has 9 replies, 7 voices, and was last updated 11 years, 10 months ago by Anonymous.
July 23, 2008 at 7:35 am #6857AnonymousInactive
I’m trying to piece together "the greatest build system in the world ever – tribute" and wondering if anyone can give me a +2.
I’ve running Subversion for source control, Mantis for bug tracking, and CPPUnit for Unit Testing.
I’ve just started looking at CruiseControl to move towards a "Continuous Build" environment.
But before I do, I just thought I’d see if I’m heading down the wrong road.
Anyone in a position to discuss how they do it?
(Running XP/Vista boxes, with VC8/VC9, Subversion SVN, AnkhSVN (http://ankhsvn.open.collab.net/) )
July 23, 2008 at 10:16 am #41844AnonymousInactive
If there are a number of developers – 3+ – CruiseControl is a a great addition to your development process. Be prepared for a lot of broken builds while your bedded down (hoping your not in crunch mode at the moment, if you are maybe its best postponed until the next lean time). You can run a build every few minutes (depending on a build cycle times ) so its a balance between build cycle time + test harness run cycle times. If you have a well developed automated test harness then it will help a lot and you should continuously to update these test harnesses. If you don’t have an well developed extensive test harness, you may drive your integration/QA team nuts.
Hope that’s a help
July 23, 2008 at 1:20 pm #41845AnonymousInactive
Perforce for source control, because IMO its miles ahead of the competition. Got usual features of a SCM, branching, merging\diff etc.
The UI is intuitive, makes everything simple (built using QT I think), so its cross platform and a huge user install base. Therefore its pretty stable and regulaly updated. Only down side is I think is Perforce can be a bit pricey for small development teams. In terms of the games industry, a huge majority of studios use it, but outside a large amount do too. Theres actually a review on http://www.gamedev.net of the most recent version.
Cruise control for continuous builds. This program is awesome, really does what it says on the tin. As for lots of broken builds I’m not sure about that one. It usually breaks when a programmer has been careless;) But with installing all new programs theres a learning curve to get it working the way you want it and goes without saying dont integrate during a crunch period, although on the flip side it might help productivity, as your not afraid of getting latest, which is pretty unacceptable in my opinion. People should be afraid when checking in that they will break a build and therefore be very careful.
(Also you can should be able to get CC to rebuild all your assets via your tool pipeline, so artists can be blamed too for bust builds ;)).
Test Track Po for bug tracking. This program seems pretty stable. Petty intuitive UI and gets the job done.
July 24, 2008 at 8:54 am #41854AnonymousInactive
There’s got to be better bug tracking software than TTP and Mantis…please god there’s got to be something better than those 2!
July 24, 2008 at 9:52 am #41856AnonymousInactive
Mantis is ok – try using filemaker!
July 24, 2008 at 12:43 pm #41858AnonymousInactive
There’s got to be better bug tracking software than TTP and Mantis…please god there’s got to be something better than those 2![/quote:d3bca56376]
Why? A bug tracker isnt exactly a complicated program. Besides most ppl dont get around to using them until beta. ;)
Bug Tracking features required:
1: Ability to edit\add\assign bugs (with descriptions and screenshot, core dump).
2: Ability to check them off.
3: Database to store the lot.
4: Some sort of UI that works and ties it all together.
Reckon a 3rd/4th year college student could take a good stab at one as a FYP. (although they’d need another bug tracker to track the bugs in their program until they are done ;) Maybe pencil and paper!)
July 24, 2008 at 3:21 pm #41860AnonymousInactive
Reckon a 3rd/4th year college student could take a good stab at one as a FYP. (although they’d need another bug tracker to track the bugs in their program until they are done Wink Maybe pencil and paper!)[/quote:d590dc6619]
Self hosting ;) Another approach you could take is Trac, it integrates with svn, git, and probably a number of other SCMs too, and it has a wiki, ticket system etc. The interface isn’t spectacular but it’s very usable
August 29, 2008 at 10:52 am #42139AnonymousInactive
Have any of you guys used Visual Build Pro, Scons, or Ant?
I’m looking at trying to streamline my builds (XP, VC8, DirectX9) with debug, profiler, and release profiles.
From what I’m reading, Scons seems to be the way to go.
Just thought I’d ask the locals for their 2 cents…
Reading an article here: http://www.codeguru.com/cpp/v-s/tips/customizingtheide/print.php/c9757 which is pretty informative, and has put me on to a few possibles.
MSBuild / vc build has somehow slipped under my radar, in the transition from 2002 to 2005. I guess it will be my first port of call…
August 29, 2008 at 10:50 pm #42143AnonymousInactive
Reckon a 3rd/4th year college student could take a good stab at one as a FYP. (although they’d need another bug tracker to track the bugs in their program until they are done ;) Maybe pencil and paper!)[/quote:cd04a9b4bb]
yeah, i reckon i could build one (based on what project studio can do) in php in something less than a week.
I used perforce on dare, it had a free version for a small number of users (can’t remember i think one account with up to five logins) was fairly nice.
some people disagree of course (http://video.google.com/videoplay?docid=-2199332044603874737&ei=B3-4SJ2RKoycigLt6oXhDA&q=google+tech+talk&vt=lf)
August 30, 2008 at 9:27 am #42144AnonymousInactive
Perforce is what the industry use the majority of time ;)
- The forum ‘Programming’ is closed to new topics and replies.