![]() ![]() That’s not as crazy as it seems, as noted by Martin Fowler, a self-described champion of continuous integration: We rarely (if ever) branch our code, instead adding things in a continuous fashion. ![]() Subversion has been a good fit for Backblaze as we are fairly linear in our development practices. Today, our tree manages contributions from engineering, operations, web development, and even marketing. Our Experience Running SubversionĪs Backblaze has grown since 2007, not only have we added more engineers to SVN, but we’ve also had more departments get on board. This allowed him to quickly develop our cross-platform “base” libraries (Rule #5) that we continue to use today. Why? Rule #1 of Brian’s 10 rules for how to write cross-platform code, “Simultaneously develop-don’t port.” He would write code initially on his PC, check it into SVN, and then check it on his Mac to make sure it worked. In hindsight, either choice probably would have worked for Backblaze, but Brian went with SVN and never looked back.īrian installed and used SVN even though at the time he was the only engineer. In mid-2007, SVN was becoming well known in the developer community, while CVS seemed to be languishing. ![]() He asked around and several of his friends suggested SVN. Using Perforce was out because we would have to pay for the licenses and when you are bootstrapping a company from your own pocket, such things are luxuries. Previously he had worked with Perforce and CVS. As a side note, the Dell Optiplex server Brian used was only recently retired from service.īrian chose SVN for Backblaze even though he had not used SVN before. Some of the article specifics are a bit outdated as the server used was running Windows Server 2003, but the overall process still works. On his personal blog, Brian, documented his experience in getting SVN up and running for Backblaze. It was selected and set up by Brian Wilson, our CTO. The longer questions are: why did we pick it, how has it worked out, and should we switch? What Most Companies Use for Version ControlĪccording to the folks at Duck Software Open Hub (formerly ), Backblaze is not alone in using SVN in fact, SVN is still the most popular repository among the registered Open Hub users as you can see in the chart below:īackblaze has used SVN since we started in 2007. Our recent post on Source Code Control led many to ask, what does Backblaze use? The short answer is Subversion (SVN). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |