![]() TestLink is a testing framework, but I personnaly do not really know much about it. An example of feature they need and claim they get with Jenkins and not with QuickBulid is integration with TestLink though a plugin available from the cummunity. But these developpers do not really care for a centralized solution as much as we do (we are in the group that is responsible for these types of tools). ![]() We believe that Jenkins is less suitable than QuickBuild for a large centralized solution. In some of our divisions, a few independent projects have setup private continuous integration systems using other tools such as Jenkins and TeamCity, and some of the developpers in these divisions strongly believe they need a more popular tool such as Jenkins mainly because of the vast community around the product and the large number of plugins that are available. We would of course go with the most recent version of QuickBuild to take advantage of the many improvements that occurred since 2.0. We are starting a major project to setup a centralized (for all of our divisions) released engineering platform around best of breed tools such as Subversion, JIRA, Artifactory, and of course QuickBuild for our build scheduler/manager since we believe that QuickBuild is one of the few tools, if not the only one, that allows managing and organizing a large number of configurations due to its hierarchical configuration organisation and great reuse that this enables. 1 decade ago We are currently using QuickBuild 2.x in one of our division.
0 Comments
Leave a Reply. |