Solutions by Distributed Version Control
Intland’s solutions are tightly integrates with Subversion, Git, Mercurial and CVS*, and through its VCS API it can be adapted to any other SCM system.
Which Version Control System is Right for Me?
learn more →
learn more →
Empowering Distributed Teams with Intland Products
codeBeamer Intland’s distributed version control Solutions
Our Agile Application Lifecycle Management (ALM) Solution for distributed software development, supports both Git and Mercurial, the two most widely used Distributed Version Control Systems. Besides version control, codeBeamer provides project management, wikis and knowledge management, document management, task, requirement and defect management, configuration management (ITIL), continuous integration, source code analysis and forums through a single and secure environment.
codeBeamer
Eclipse Studio
codeBeamer Eclipse Studio (CBES) gives reflectivity and mobility to codeBeamer users. You can create and edit tasks, bugs, requirements, edit and commit code quickly without leaving Eclipse. You can do it online and offline. You can also take full advantage of the task-focused work provided by Tasktop, work faster with increased productivity, reduce the information overload, and focus only on what is relevant for your current tasks. CBES’s task list also provides sophisticated task scheduling.
codeBeamer Eclipse Studio is the perfect client-side companion for codeBeamer.
MercurialEclipse
MercurialEclipse is a plugin providing support for the highly popular Mercurial distributed version control system within the Eclipse IDE. MercurialEclipse supports importing repositories as Eclipse projects, convenient syncronization of changes, branching, tagging, histories and patch management.(codeBeamer Eclipse Studio is bundled with MercurialEclipse.)
Learn moreWhat is Distributed Version Control?
According to some, Distributed Version Control (DVCS) is “possibly the biggest advance in software development technology in the past ten years.“
DVCS is a new paradigm in version control, suited primarily for large projects with partly independent developers. As a good engineering practice, developers split their work into chunks, developing and testing in isolation and slowly merging their changes into the main line. As the project grows, the number of branches grow to a level where it becomes unmanageable in a centralized system. Distributed systems make branching and merging painless, make large projects manageable, and make teams productive.
Learn more about Distributed Version Control in Wikipedia.
Why we use and support Distributed Version Control?
DVCS takes a peer-to-peer approach, as opposed to the client-server approach of centralized systems. This results in some major advantages:
- Performance: common operations are amazingly fast.
- Merge: merge is a “dream” comparing to other systems.
- Flexibility: your team members can work anywhere, anytime, including even offline.
- Reliability: there is no single point of failure.
- Scalability: proven on huge open source projects, like the Linux Kernel project for instance.