Update cookies preferences

E-book: Practical Perforce: Channeling the Flow of Change in Software Development Collaboration

3.41/5 (54 ratings by Goodreads)
  • Format: 256 pages
  • Series: Practical Ser.
  • Pub. Date: 18-Nov-2005
  • Publisher: O'Reilly Media
  • Language: eng
  • ISBN-13: 9780596518073
Other books in subject:
  • Format - PDF+DRM
  • Price: 26,90 €*
  • * the price is final i.e. no additional discount will apply
  • Add to basket
  • Add to Wishlist
  • This ebook is for personal use only. E-Books are non-refundable.
Practical Perforce: Channeling the Flow of Change in Software Development CollaborationLarger Image
  • Format: 256 pages
  • Series: Practical Ser.
  • Pub. Date: 18-Nov-2005
  • Publisher: O'Reilly Media
  • Language: eng
  • ISBN-13: 9780596518073
Other books in subject:

DRM restrictions

  • Copying (copy/paste):

    not allowed

  • Printing:

    not allowed

  • Usage:

    Digital Rights Management (DRM)
    The publisher has supplied this book in encrypted form, which means that you need to install free software in order to unlock and read it.  To read this e-book you have to create Adobe ID More info here. Ebook can be read and downloaded up to 6 devices (single user with the same Adobe ID).

    Required software
    To read this ebook on a mobile device (phone or tablet) you'll need to install this free app: PocketBook Reader (iOS / Android)

    To download and read this eBook on a PC or Mac you need Adobe Digital Editions (This is a free app specially developed for eBooks. It's not the same as Adobe Reader, which you probably already have on your computer.)

    You can't read this ebook with Amazon Kindle

This reference explains the Perforce commands and features for tracking software versions and all the components that go into them during a product life cycle. The vice-president of product technology at Perforce Software also identifies the codelines that form the mainline model, describes the rules for change flowing between them, and demonstrates how to manage codelines of a particular type. Annotation ©2006 Book News, Inc., Portland, OR (booknews.com)

An engaging read, this text imparts best practices for using the Perforce Software Configuration Management system--written by a Perforce insider.

When developers build software, they're able to keep track of all the different versions and all the components they use with software configuration management (SCM) systems. One of the more popular SCM products is Perforce.

Authored by Perforce's own VP of product technology, Practical Perforce is the ideal complement to the existing product manual, focusing less on the 'how" and more on the "why" and "when." The book is not only a helpful introduction to Perforce, it's an enlightening resource for those already familiar with this versatile SCM product. Whether you're a programmer, product manager, or build engineer, you stand to benefit from the many insider tips and ideas presented in this convenient guide.

Practical Perforce is divided into two main parts. Part I offers a whirlwind technical tour, complete with careful descriptions of basic and advanced Perforce commands designed to give you a baseline knowledge. Part II describes the big picture-using Perforce in a collaborative software development. It outlines recommended best practices and quickly shows how to implement them with the Perforce operations introduced in Part I. Throughout the book, you'll learn how to maximize Perforce so it completes tasks like these in the most efficient manner possible:

  • Keep track of changes as you conduct concurrent parallel work on files
  • Log activity
  • Generate reports on who did what when
  • Compare, merge and branch files
  • Store files and file configurations
  • Restore lost bug fixes

Recognizing the pitfalls and practices of an SCM system like Perforce is absolutely essential to producing good software. Now, with Practical Perforce, you have the edge you need to ensure success.



An engaging read, this text imparts best practices for using the Perforce Software Configuration Management system--written by a Perforce insider.

Reviews

"It is an indispensable companion for any Perforce user who wants to get it right. Highly recommended." - Mike James, - VSJ, September 2006

Preface vii
Files in the Depot
1(16)
The Perforce Filespec Syntax
1(6)
Browsing Depot Files
7(8)
File Types at a Glance
15(2)
Working with Files
17(32)
An Overview
17(3)
Creating a Workspace
20(6)
Synchronizing a Workspace
26(3)
Local Syntax, Wildcard Expansion, and Special Characters
29(2)
Working with Local Files
31(8)
Working with Pending Changelists and Submitting Files
39(5)
Removing and Restoring Files
44(2)
Useful Recipes
46(3)
Resolving and Merging Files
49(38)
Resolving: When, What, and How
49(13)
How Perforce Merges Text Files
62(4)
Reconciling Structural Changes
66(8)
Tips for Smoother Collaboration
74(4)
The Arcana of Merging
78(9)
Branching and Integration
87(40)
The Classic Case for a Branch
88(1)
Creating Branches
89(7)
Integrating Changes from Branch to Branch
96(16)
Reconciling Structural Changes
112(6)
The Arcana of Integration
118(9)
Labels and Jobs
127(17)
Saving Important Configurations
127(2)
Using Labels
129(8)
Using Jobs
137(5)
Jobs as Changelist Markers
142(2)
Controlling and Automating Activity
144(23)
Depot and File Access
144(2)
Accessing Files in Other Domains
146(4)
Saving and Restoring Specs
150(2)
Change Notification and Change Monitoring
152(5)
Scripting Tips
157(6)
Behind-the-Scenes Version Control
163(4)
How Software Evolves
167(22)
The Story of Ace Engineering
167(2)
The Mainline Model
169(14)
Ace Engineering Revisited
183(3)
Containerizing
186(3)
Basic Codeline Management
189(27)
Organizing Your Depot
189(10)
General Care and Feeding of Codelines
199(6)
Nightly Builds
205(3)
Is Bug X Fixed in Codeline Y?
208(8)
Release Codelines
216(33)
Creating a Release Codeline
216(6)
Working in a Release Codeline
222(5)
Integrating Changes into the Mainline
227(4)
Making a Release
231(4)
Distributing Releases
235(2)
Breaking the Rules
237(3)
Retiring a Release Codeline
240(2)
Task Branches and Patch Branches
242(7)
Development Codelines
249(33)
Creating a Development Codeline
249(6)
Working in a Development Codeline
255(3)
Keeping a Development Codeline Up to Date
258(5)
Working with Third-Party Software
263(4)
Delivering Completed Development Work
267(8)
The Soft Codelines
275(7)
Staging Streams and Web Content
282(23)
Staging Web Content
282(6)
Visual Content Development
288(9)
Bug Fixes and Staging Streams
297(5)
Major Web Development
302(3)
A. Setting Up a Perforce Test Environment 305(6)
B. Perforce Terminology and P4 Commands 311(4)
Bibliography 315(2)
Glossary 317(4)
Index 321


Laura Wingerd formed her early opinions of software configuration management during a decade of wrangling builds and source code for the Sybase and Ingres database products. She joined Perforce Software the day the company moved out of its founder's garage and has since acquired quite a bit of SCM expertise from the very Perforce customers she purports to advise. Every now and then, she comes up with an idea of her own and spews forth in a white paper or a speaking engagement. Laura is currently vice president of product technology at Perforce Software, dividing her time between promoting sound SCM practices and investigating new and better ways to put Perforce to use.
More information about ebooks More information about ebooks
Permanent link: https://www.kriso.ee/db/97805965180732e.html
Keywords: