April 27, 2015by Matt Attaway, Open Source Community Manager (@p4mataway)
On May 1st, 2015, Perforce will officially cease development on P4Web, P4Sandbox, and the review daemon. We will also end support for these products on the same date. The most recent builds of P4Web and P4Sandbox have been archived in the Perforce Workshop for folks who need them. The source code for P4Web is available in the Workshop, and the P4Sandbox source code will be released in the coming weeks. The review daemon source code remains available as before.Posted In:
April 22, 2015by Matt Attaway, Open Source Community Manager (@p4mataway)
The 2015.1 Helix Versioning Engine release brought one of my favorite Git features to P4D; the ability to quickly make disposable branches for experimenting. Today I’m going to walk you through a time where they recently saved my bacon so you can see if they may help with your work.
April 21, 2015
by Steph Turner, Open Source Developer at Perforce Software (@p4vsteph)
Here's a chance for some face time with a Perforce engineer. We're sending a few off the Island for a few days. We're even buying the beer!Posted In:
April 15, 2015Jonathan Thorpe, Technical Marketing Manager at Perforce
I recently had the honor of participating in the Version Control episode of #c9d9, the Continuous Delivery (CD) 'Continuous Discussion' series hosted by Electric Cloud. Along with panelists from Macy's, GoMidjets, Sonatype and Electric Cloud, we asked four questions about version control and CD:
1. Who should use/what should be in version control?
2. How does version control affect your CD pipeline?
3. How will version control evolve?
4. What are your version control horror stories?Posted In:
April 13, 2015
John Williston, Product Marketing Manager at Perforce Software
Remember how the simplest thing we did early in this series of blogs was create a local repository? It’s been a while, so to refresh your memory we initialized a server, created a file, reconciled our work, and submitted it.
April 07, 2015Sven Erik Knop, Technical Marketing Manager at Perforce Software
When I started using Git, I immediately came across the problem that I did not know which branch I was currently in. Using Perforce I do not tend to swap branches that often since I can shelve my changes if I need to swap what I am working on, but in Git I easily work in 3 or 4 branches in parallel. Hence my problem of knowing which branch is currently active.