Modify

Opened 8 years ago

Last modified 3 years ago

#694 new enhancement

View only part of Perforce depot

Reported by: Miki <mtebeka@…> Owned by: ttressieres
Priority: high Component: PerforcePlugin
Severity: major Keywords: MESSAGE
Cc: Porsgrunn Trac Release: 0.10

Description

When multiple projects are using the same Perforce server, they don't want to view other people work in their timeline and changes.

I suggest adding a "deopt_path" configuration option where p4trac will look for changes/history/... only below this path

e.g.

[perforce]
port = perforce:1666
user = p4trac
password = yourpassword
unicode = 0
depot_path = //myproject/main/...

Attachments (1)

api.py.diff (9.0 KB) - added by miki <mtebeka@…> 8 years ago.
Patch for apy.py to handle client spec restriction

Download all attachments as: .zip

Change History (13)

Changed 8 years ago by miki <mtebeka@…>

Patch for apy.py to handle client spec restriction

comment:1 Changed 8 years ago by miki <mtebeka@…>

Thought the best way was to use a client, this way the restriction can be much more flexible.

Hope the patch will make it to the trunk :)

New configuration:

[perforce]
port = localhost:1666
user = duffy
password = duck
client = duffy-trac-client
unicode = 0

comment:2 Changed 8 years ago by anonymous

any idea if this is going to make it into the trunk? it would be really useful for people like me who share a repository with many other people in a large company. Thanks!

comment:3 Changed 7 years ago by anonymous

I would like to see this going into the trunk, too. Especially the client-spec feature, because this is much more powerful then just specifying a single path to the depot. Even large existing client specs can be reused.

comment:4 Changed 7 years ago by hickninja@…

I'd love for this to get into the trunk as well. I manually applied the patch to the current stable version, and it works great. I'm also in a huge company, and our Perforce server serves probably 10 or 20 projects, each of which is enormous. Any one project only needs to see the changes relevant to them. Also, it takes forever to initialize the cache after the patch was applied. Before the patch, it was impossible.

comment:5 follow-up: Changed 7 years ago by enrico.straube@…

this patch dosn't work here... any help?

comment:6 in reply to: ↑ 5 Changed 7 years ago by bw@…

Also does not work for me. It always uses the entire database for me.

comment:7 Changed 6 years ago by WafvaxByday

  • Cc Porsgrunn added
  • Keywords MESSAGE added

comment:8 Changed 5 years ago by anonymous

not working here aswell, any progress on this matter?

comment:9 Changed 4 years ago by anonymous

Hey guys, as most people have pretty big repositories we really need this working - at the very least point me to how to fix it myself please. Having to use the entire depot is a deal breaker in my case. :-(

comment:10 Changed 3 years ago by anonymous

  • Priority changed from normal to high
  • Severity changed from normal to major

comment:11 Changed 3 years ago by anonymous

Can someone give me some info on what needs to changed here so the client mapping fits in? I'd also be happy to just hard code a root path in the depot - no matter what i put in the "repository dir" option it always tries to walk the whole depot. I'm talking a large depot here with millions changelists.

Would appreciate some help!

comment:12 Changed 3 years ago by anonymous

Btw guys I'm having serious issues with the spam filter, i can only submit comments from a specific machine, like 5 others all get spam errors....

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.