CloudForge’s Improved Subversion Service

The Backstory Since joining the CloudForge Development team within CollabNet nearly a year ago, several of my colleagues and I have been primarily focused on delivering improvements to the scalability and reliability of the CloudForge improved Subversion service.  With tens of terabytes of live Subversion repository data being generated and used by tens of thousands of our customers, even the smallest improvements we make to the service have a pretty big impact. CloudForge was built on a strong Subversion architecture, but over the years the ever-growing number of customers put a strain on the platform.  In the original architecture, customers (organizations) were … LEARN MORE »

Linking TeamForge Commits and Artifacts

teamforge agile software development

TeamForge- Enabling Collaboration CollabNet TeamForge provides not only the tools that are necessary to manage and .  It is this tight integration between all the important application lifecycle stages that enables your teams to collaborate most effectively. In this blog I am going to focus on the linkage between your Git or Subversion code commits and your work items, such as requirements, user stories, tasks, issues and bugs. Associations To provide some context, let’s look at how TeamForge implements an association between two items or events, such as a work item and an SCM code commit. Almost every type of TeamForge … LEARN MORE »

Subversion and Heartbleed — Are you vulnerable?

Heartbleed

You have probably already heard about the OpenSSL vulnerability, named Heartbleed, that is getting so much attention in the press. This is a significant vulnerability that can expose data in memory on your server. Making matters worse is that this vulnerability leaves absolutely no trace on the server. You will not see this in your logs no matter how detailed your logging level and it also does not require any authentication with the server. This bug impacts the current Subversion binaries we were providing so we have updated those binaries to include the fixed version of OpenSSL – 1.0.1g and those … LEARN MORE »

How to Get Started with CloudForge Development Platform in Pivotal CloudFoundry PaaS

CollabNet’s CloudForge is a collaborative software development platform providing source code management (version control), issue tracking, and agile planning for all personal and professional projects. Full role-based user administration and directory-level access controls allow you to easily manage your development process across distributed teams, both large and small. CloudForge’s inclusion in the CloudFoundry marketplace allows you to quickly set up your projects and teams, leaving more time to focus on developing, building, and testing your applications in a collaborative SDLC framework before deploying them to CloudFoundry. CloudForge is available in all CloudFoundry marketplaces among the various applications you might want to … LEARN MORE »

CloudForge Joins Pivotal CloudFoundry PaaS Ecosystem

CloudForge in CloudFoundry Ecosystem

CloudForge and CloudFoundry Accelerate Application Development Great news for cloud developers! CloudForge joins Pivotal CloudFoundry PaaS Ecosystem.  Have you heard of Pivotal’s CloudFoundry? In a short amount of time, Cloud Foundry has become a leader among all the open source platform as a service (PaaS) initiatives. Cloud Foundry is an open platform-as-a-service, providing a choice of clouds, developer frameworks and application services. It makes it faster and easier to build, test, deploy and scale web and mobile applications. Cloud Foundry is available through a variety of private cloud distributions and public cloud instances, including Vmware’s vSphere, Amazon Web Services, Open … LEARN MORE »

Migrating Subversion Repositories to Git – The definitive Guide for TeamForge Users

gerritcollabnet

  Many software projects are moving from a centralized version control system (CVCS) to a distributed version control system (DVCS). Undoubtedly, the most used DVCS is Git. My team at CollabNet recently migrated one of our flagship Open Source projects, the CollabNet Connector Framework, from Subversion to Git. This blog shares the step by step guide to migrate SVN repositories  to Git repositories using git svn while maintaining all version history. This blog will cover two use cases: 1) Migration of a single project SVN repository to a single Git repository 2) Migration of a multi-project SVN repository to multiple Git repositories … LEARN MORE »

CloudForge Security Is Rated Enterprise Ready by Skyhigh CloudTrust™ Program

CloudTrust Program

Experts following cloud adoption confirm that security remains the single biggest barrier to cloud adoption. This puts the burden on developers and engineering management to evaluate the security capabilities and practices of their cloud partners which can be an expensive, and time-consuming effort. CloudForge Architecture Built to Take Security Seriously Security is a critical factor when selecting a cloud development platform, and every day, the CloudForge team is asked by prospective customers if CloudForge security can keep their customers’ data private and protected.   The answer is a resounding YES!  CloudForge takes security seriously and has built a robust enterprise-ready architecture … LEARN MORE »

Why compete? Embrace Git and Subversion in the Enterprise

Git and Subversion

I read a blog post this week in ReadWrite about how Git is giving Subversion a run for its money. The author states, “It has taken a long time for Git to push Subversion aside, despite clearly being better for developers.” My question is this…why does Git need to push Subversion aside and declare to be better? Comparing Git and Subversion is like comparing apples and oranges. Yes, they are both in the fruit family, but one is not better than the other. Git and Subversion are both version control systems (VCS) which allow developers to manage changes to documents, … LEARN MORE »

Foreign Repository Copies

SAMSUNG

Some time ago, I wrote in this space about some new functionality that I had managed to work into Subversion — the ability to merge changes into a working copy from a so-called “foreign repository” (that is, a different repository than the one reflected by the working copy).  I touted the feature as a lovely alternative way to manage vendor branches.  I admit that I may have glossed over the details a bit in that post, but the idea seemed simple enough:  import a baseline copy of the third-party codebase into your repository, and thereafter merge the changes made by … LEARN MORE »

Repository Dictated Configuration — Part 3 of 3: Global Ignores

iprops

Global Ignores Welcome to the last topic in my three part series on repository dictated configuration (RDC).  In part 2 we talked about the new svn:auto-props property.  Today we’ll discuss the other new inherited property that involves RDC, svn:global-ignores. Ignoring Unversioned Items Before 1.8 Once again, this is just a quick refresher, if none of this sounds familiar, then give this section of the Version Control with Subversion book a quick read. Up until 1.7 there were two ways to prevent the svn add and import subcommands from adding certain items we didn’t want to place under version control (as … LEARN MORE »