[p4] Efficiency of protect

jan-ake.olsson@uiq.com jan-ake.olsson at uiq.com
Tue Feb 27 04:23:39 PST 2007


Hi Sushree!!

We have a solution that works for us, that all our Offshore developers 
have their own Depot, then we have a team that integrate forward and back 
to the nessecary branches.
Your offshore team will never see your product line complete, and you can 
controll the protection table smoothly.

//EXT_DEPOT/your_ODC1/Code/...
//EXT_DEPOT/your_ODC2/Code/...
etc.

You take their code and place it where you need it, depending how your 
test policy are.

Maybe it works for you to..... or not :)

/Janne.

 



Sushree Tripathy <sushreetripathy at yahoo.com> 
Sent by: perforce-user-bounces at perforce.com
2007-02-27 06:08

To
perforce-user at perforce.com
cc

Subject
Re: [p4] Efficiency of protect






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


**************************************************
UIQ Technology AB, a company registered in Sweden with company number 556566-7911
and registered office at Softcenter 8, 372 25 Ronneby, Sweden. The information in this e-mail,
and attachment(s) thereto, is strictly confidential and may be legally privileged. It is intended
solely for the named recipient(s), and access to this e-mail, or any attachment(s) thereto, by
anyone else is unauthorized. Violations hereof may result in legal actions. Any attachment(s)
to this e-mail has been checked for malicious code, but please rely on your own virus-checker
and procedures. If you contact us by e-mail, we will store your name and address to facilitate
communications in the matter concerned. If you do not consent to us storing your name and
address for above stated purpose, please notify the sender promptly. Also, if you are not the
intended recipient please inform the sender by replying to this trans-mission, and delete the
e-mail, its attachment(s), and any copies of it without disclosing it.
**************************************************


More information about the perforce-user mailing list