[p4] Efficiency of protect

[Chuck Karish]

Can you run separate servers for the Bangalore and New York teams?

We run triggers to control write permissions.  The trigger file is
generated from an m4 source file, using macros that can include
wildcards that affect a particular file name or directory name
anywhere in the source tree.

  Chuck

On 2/26/07, Sushree Tripathy <sushreetripathy at yahoo.com> wrote:
> Thanks Robert for your suggestion.
>
> Thanks Stephen,
>
> But my intention is that bangalore_users do not get
> any access to the //depot/main/dev/... codeline at all
> since it is a restricted one.
> So even seeing a copy is voilating the rights and I
> need a work around.
>
> I also saw the undoc =rights, i.e =branch restriction.
> So using that in protections as :
>
> =branch group newyork_user * -//depot/main/dev/...
>
> would restrict them to do any integ operation using
> the codeline as the source I guess.
>
> Again this puts a restriction that they cannot integ
> the above codeline to their personal/team branches to
> carry out some work.
>
> So again I need a work around... :(
>
> To this I think there are two options left with me:
>
> 1)Considering Robert's suggestion we can create
> awareness that such an operation will be considered as
> an offence.
>
> OR
>
> 2)Write trigger to prevent the operation
>
> Please correct me if I am wrong and give suggestions
> if any...
>
> -Sushree.
>
>
>
> --- Stephen Vance <steve at vance.com> wrote:
>
> > Sushree --
> >
> > In your branching example, if the newyork_users
> > branch
> > //depot/main/dev/... to //depot/main/jam/dev/... the
> > bangalore_users can
> > only operate on the copy under
> > //depot/main/jam/dev/.... If your purpose
> > is to completely hide the contents of that source,
> > you have an issue to
> > overcome. If you just want to protect the copy under
> >
> > //depot/main/dev/... then you don't have a problem.
> >
> > You may also want to look at the "branch" protection
> > level. You can find
> > it as an undocumented feature under 'p4 help undoc'.
> >
> > Steve
> >
> > Sushree Tripathy wrote:
> > > Hi All,
> > >
> > > I have two groups say
> > >
> > > bangalore_users
> > > newyork_users
> > >
> > > I have the following protections:
> > > read group bangalore_users * //depot/main/...
> > > write group bangalore_users * //depot/main/jam/...
> > > read group bangalore_users * -//depot/main/dev/...
> > > wirte group newyork_users * //depot/main/...
> > >
> > > But what if someone from newyork_users group
> > branches
> > > the files under //depot/main/dev/... to
> > > //depot/main/jam/dev/...
> > >
> > > Then bangalore_users get write access to files
> > under
> > > //depot/main/dev/... which they should not have
> > > access.
> > >
> > > I do understand that the above example can be
> > stated
> > > as a mischief but my point is that are the
> > protections
> > > that efficient w.r.t files/folders?
> > >
> > > Also can we implement some triggers so that we
> > > restrict branching paths by which files become
> > visible
> > > to restricted users?
> > >
> > > Please suggest....
> > >
> > >
> > > Regards,
> > > Sushree.
> > >
> > >
> > >
> > >
> > >
> >
> ____________________________________________________________________________________
> > > Now that's room service!  Choose from over 150,000
> > hotels
> > > in 45,000 destinations on Yahoo! Travel to find
> > your fit.
> > > http://farechase.yahoo.com/promo-generic-14795097
> > > _______________________________________________
> > > perforce-user mailing list  -
> > perforce-user at perforce.com
> > >
> >
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> > >
> > >
> >
>
>
>
>
> ____________________________________________________________________________________
> Do you Yahoo!?
> Everyone is raving about the all-new Yahoo! Mail beta.
> http://new.mail.yahoo.com
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>


-- 
Chuck Karish   karish at well.com   (415) 317-0182