Ticket #2376 (assigned defect)

Opened 10 months ago

Last modified 8 months ago

Strange behaviour when using p4 workspace

Reported by: Nounours Assigned to: ttressieres (accepted)
Priority: normal Component: PerforcePlugin
Severity: normal Keywords: 0.5dev
Cc: krr Trac Release: 0.11

Description

On a Trac v0.11 running the 0.5dev version of the Perforce Plugin :

We have one repository for all our projects, then we restrict the views with workspaces.

Setting the workspace value in the [perforce] section from trac.ini doesn't seem to restrict the contents of the cached repository (I assume it's normal because p4 changesets aren't workspace-bound).

But when i'm trying to browse the repository from Trac web UI, the plugin raises a NoSuchNode? exception (maybe because the generated nodePath //workspace_name/etc.... isn't stored inside the cached repository). I can browse the repository by entering a real repository path in the URL, as http://trac.site.url/browse/repos/real/path/. Alas that's not the behaviour I was expecting for.

Is there an easy way to enable repository browsing from //workspace_name/ ? Do I need to store the workspace mapped pathes in the cached repository instead of the real pathes ?

Attachments

Change History

01/11/08 14:31:03 changed by ttressieres

  • owner changed from lewisbaker to ttressieres.
  • status changed from new to assigned.

03/31/08 02:15:40 changed by krr

  • cc set to krr.

03/31/08 02:29:32 changed by krr

I have the same problem. To reproduce, I create a new client specification TEST containing a view sections as follows 

View:
    //misc/... //whatever/misc/...

Then I set the workspace argument in the [perforce] section to TEST, and issue a resync.

If I then go to the Browse Source section I get a: 

Error: No such node

No node //whatever/misc at revision @962

Add/Change #2376 (Strange behaviour when using p4 workspace)




Change Properties
Action