At work we use Surround SCM for versioning and Test Track Pro as our ticketing solution. Because of some of the limitations of these tools, I am writing a business case to transition to other tools and build processes. What I'd like is to hear how other folks out there are setup. If you have a few moments, I'd love it if you jotted down answers to the following:
- What is your source control management server?
- What is your ticketing system?
- Provide a high level overview of your build process
- How do you push from testing to staging to production, ensuring your build is consistent?
- What other tools do you use in your process to assist in the build, or make things easier?
- How large is your team?
- What types of projects do you work on?
- Does your development staff work on multiple projects at the same time?
- Do you enforce unit and integration testing?
- What project management process is your company using (agile, waterfall, etc)?
- What challenges have you encountered, and how have you overcome them?
If you have any other thoughts I'd love to hear them. Although I am biased (because I've used JIRA, SVN and Mylyn in the past), I am still trying to provide an objective and unbiased business case. I've jotted down some of the issues we've encountered using Surround SCM. If you use Surround and are aware of how to overcome the limitations we have experienced, please let me know!
- No automated changelists
- No workflow/IDE integration that is reliable or performant. The Eclipse plugins provided by SeaPine are notably pretty bad and this is the general consensus in our shop.
- Surround cannot move/delete files on check-in/checkout/promote
- Surround is terrible at merging changes for XML files
- Merging requires a lot of time if there are other developers working with the same codebase
- The automated merging process is inaccurate, and requires more hands-on work than other common tools
- Using Surround remotely is clunky and slow.
Tags: Process & Tooling