How many of you do Continuous Integration and Unit Testing?
Which tools do you use?
#continuousintegration #unittesting
How many of you do Continuous Integration and Unit Testing?
Published
I rant, therefore I am.
I rant, therefore I am.
How many of you do Continuous Integration and Unit Testing?
Which tools do you use?
#continuousintegration #unittesting
Continua/FinalBuilder/DUnit/DSharp (DUnit attributes and mocks)/selfmade DUnit like framework for integration tests
Jenkins/DUnit/delphi-oop (DUnit extensions)
DUnit, Finalbuilder, Jenkins
DUnit, psake/TeamCity
Jenkins/DUnit/DUnitX
CC.Net/FinalBuilder/DUnit
I should add that I am pushing to get FinalBuilder.
Bamboo, DUnit and in-house software to emulate an user
Jenkins/DUnit/DUnitX
Continua CI/FinalBuilder/DUnitX/Delphi-Mocks 😉
Jenkins/FinalBuilder/DUnit/DUnitX
Jenkins & DUnit
Continua CI, Finalbuilder, DUnitX
just about to purchase Continua CI and Finalbuilder.
so currently just DUnit and hand cranked build scripts.
FinalBuilder, Continua CI, DUnitX (Disclaimer I am a developer on all of these).
Jason Duffy Smith Ah and Vincent is just the front man… 🙂
Jason Duffy Smith any chance you guys run a survey of version control systems in use among your customers again? It’s been a while (;
Off the top of my head based on recent interactions with customers, in this order (don’t shoot the messenger), TFS, Git, Svn, Mercurial, Perforce – no prizes for guessing which one is the most problematic (for us and our customers). IMHO, TFS is a steaming pile of poo, I struggle to understand why people would chose to use it. I dread seeing support cases that mention TFS, because I know it’s going to suck up so much time figuring out wtf TFS is doing.
Interestingly, it’s much more common these days to hear that customers are using multiple systems. We use hg in house, but Git for our open source stuff (mostly because of github though), and still have some older stuff in Surround SCM. That sort of thing used to be unheard of, changing version control was harder than changing compilers!
It’s still hard to change if you need to maintain change history – unless you commit every branch or tag sequentially – which may be doable, depending on how you organized it. Even then you prolly lose the commit comments.
Git-SVN is of great help to finally move away from SVN. One of then git/TFS bridges is crazy, the other OK.
Vincent Parrett tanks for the update.
I think the design goals for TFS were to fix the shortcomings of VSS (data corruption, endless maintenance tasks) while making it even more frustating to use. If that’s the case then I would call it a resounding success.