P4 Blog

  • January 06, 2015

    2015 predictions about the world of software

    Over the last five years, DevOps has successfully brought Development and Operations teams together to meet the common goal of releasing better quality software faster. In 2015, the rest of the enterprise will follow in DevOps’ footsteps with cross-functional teams—like design and development—working together more closely. To successfully foster this next-generation collaboration, tools will be consolidated to create a “single source of truth” for all assets—borrowing a fundamental principle of DevOps and Continuous Delivery. Software developers have used version control software to manage source code repositories as long as software has been developed. And as businesses embrace DevOps practices across their organizations, they will similarly make broader use of version control.

  • December 31, 2014

    git vulnerability

    The Git v2.2.1 release of December 18, 2014, patches a vulnerability as described in the announcement on the official Git mailing list. The purpose of this blog post is to (1) explain briefly what the vulnerability is, (2) assess the threat, and (3) explain how it affects users of Perforce Git Fusion.

    Posted In:
  • December 19, 2014

    Silvia Gheorghita

    This is part of a blog series designed to explore the stories of our Women in Tech at Perforce. It's been fun and inspiring talking to each one of these women. As they share where they've been and how they came to where they are now, it is my hope that others will be encouraged and inspired too.

    Silvia Gheorghita is our second Hackbright Academy hire. She's been at Perforce for just under a year and has already made impressive contributions to the company including adding tests to our automation suite. When she's not heads down testing, she loves photography, running and blogging about food.

    Posted In:
  • December 18, 2014

    perforce swarm commons inights

    Here's what's new from Perforce in December.

    Posted In:
  • December 18, 2014

    This is part 6 of a 6-part series on Git commands.

    git beyond the basics using shallow clones

    One problem commonly encountered when using Git in the context of Continuous Integration (CI) and Continuous Delivery (CD) is server load. Because Git’s design includes everything in each copy of a repository, every clone gets not only the files but every revision of every file ever committed. It isn’t hard to imagine how that can quickly become a bottleneck with expanding numbers of build, test and deployment pipelines.

    Posted In:
  • December 17, 2014

    Continuous Delivery (CD) has been an interest of mine for many years. It has been a pleasure to organize the resources and links below.

    Continuous Delivery Books and Resources

    1. Agile Manifesto

    Going back to the beginning, the term CD arises in the first principle of the Agile Manifesto which was developed at a meeting of software development luminaries in February 2001:

    Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

    Those luminaries were steeped in practices ranging from Extreme Programming, SCRUM, DSDM to Feature Driven Development.