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

selvakumarGit Subversion TeamForge
Posted by selvakumar
February 13, 2014
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

jlibandGit Subversion
Posted by jliband
January 22, 2014
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

C. Michael PilatoSubversion
Posted by C. Michael Pilato
June 28, 2013
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

Paul Burba Subversion
Posted by pburba
June 26, 2013
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 »

Repository Dictated Configuration — Part 2 of 3: Autoprops

Paul Burba Subversion
Posted by pburba
June 25, 2013
iprops

Automatic Properties In part 1 I talked about the new inheritable properties feature in Subversion 1.8.  I promised that this feature would pave the way for repository dictated configuration (RDC).  Today I’ll show you the first part of 1.8′s RDC related features, the new svn:auto-props property. Wait…What is RDC Exactly? Subversion provides an extensive set of user configurable options which control various aspects of a Subversion client’s operations.  For repositories with only a small handful of committers in the same location, manually synchronizing these configurations is probably not too difficult.  For larger and/or distributed groups however, ensuring that everyone has … LEARN MORE »

Subversion Hackathon Berlin 2013 Wrap-up

C. Michael PilatoSubversion
Posted by C. Michael Pilato
June 24, 2013
SAMSUNG

The jetlag has worn off; the clothes have been unpacked from suitcases, washed, and restored to their proper places in my closet and drawers; the AC converters stuffed back into one of the many miscellaneous electronics bins in my office; and life has resumed for me on my typical side of the Atlantic Ocean.  After flying back from the Subversion Hackathon in Berlin, breezing through uncharacteristically fast Passport Control and Customs lines at Charlotte-Douglas International Airport, arriving in my hometown of Harrisburg, NC, and enjoying a lovely Father’s Day weekend with my immediate and extended families, last Monday began a … LEARN MORE »

Repository Dictated Configuration — Part 1 of 3: Inheritable Properties

Paul Burba Subversion
Posted by pburba
June 24, 2013
iprops

Bait-and-switch warning: Despite the title, I won’t talk about repository dictated configuration (RDC) today at any great length.  Rather, I’ll talk about the new inherited properties feature, which RDC is built upon, in the hope that it will provide a more complete understanding.  In part 2, I’ll move on to the details of RDC proper. Property Inheritance Even the most casual user of Subversion is likely familiar with versioned properties.  These name:value pairs of metadata are assigned to files or directories.  Some (those properties whose names begin with “svn:“) are attributed special meaning by, and trigger specific behaviors in, Subversion … LEARN MORE »