[p4] Trigger to limit size of files being added
sjamison at ciena.com
Fri Oct 10 06:31:55 PDT 2008
It is plain ignorance.
The pendulum of acceptance swings from "not going to use version
control" to "let put everything in there". The challenge is to keep it
in the middle and spend as little time as possible in either extreme.
I spend more time doing marketing, sales and training than actually
maintaining the CM system itself.
From: Stephen Vance [mailto:steve at vance.com]
Sent: Thursday, October 09, 2008 6:35 PM
To: Jamison, Shawn
Cc: perforce-user at perforce.com
Subject: Re: [p4] Trigger to limit size of files being added
A change-content trigger should be able to inspect the size of the file.
Or you could just use protections to block zips for all but a select
handful of users. Another alternative is to give all zips, or maybe all
zips in particular locations, the +S modifier so that no more than a
revision (or more if you use the argument) are stored. What are the
reasons people are checking these in? Ignorance? Process optimization?
Jamison, Shawn wrote:
> I recently had a years worth of disk space vanish in 2 months and
> while investigating I found users were checking in 100 MB to 300 MB
> Some of these had 20 revisions.
> I also had a user place a 600 MB ISO image into perforce.
> Does anyone know of a way to prevent large binary files from being
> added or checked in to Perforce?
> -Shawn Jamison>
> Ciena Corp.
> Perforce Admin
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user