Hi Tatu,

I have actually made the changes to allow you to have the view without a specific depot defined (i.e. //tatula-client/... will now work) . I have also improved the on-screen help, documentation and validation to make this all a little clearer. The changes will be included in the next release.

Apologies for the confusion,
Brydie

Hi Tatu,

Thanks a lot for your help. I agree with the messages not being very helpful. Unforunately at this point we can't actually change Bamboo to work on your original format for the client view, however, I will update the error messages and documentation to help avoid this confusion in the future.

Cheers
Brydie

The p4 client:

$ p4 client -o

1. A Perforce Client Specification.
   #
2. Client: The client name.
3. Update: The date this specification was last modified.
4. Access: The date this client was last used in any way.
5. Owner: The user who created this client.
6. Host: If set, restricts access to the named host.
7. Description: A short description of the client (optional).
8. Root: The base directory of the client workspace.
9. AltRoots: Up to two alternate client workspace roots.
10. Options: Client options:
11. [no]allwrite [no]clobber [no]compress
12. [un]locked [no]modtime [no]rmdir
13. LineEnd: Text file line endings on client: local/unix/mac/win/share.
14. View: Lines to map depot files into the client workspace.
    #
15. Use 'p4 help client' to see more about client views and options.

Client: tatula-client

Update: 2006/11/07 12:10:27

Access: 2007/06/01 09:50:42

Owner: tatula

Host: comp

Description:
Created by tatula.

Root: /home/tatula/Work/Perforce

Options: noallwrite noclobber nocompress unlocked nomodtime normdir

LineEnd: local

View:
//depot/... //tatula-client/...

So if I understood correctly, the "//tatula-client/..." goes to the Depot configuration of the bamboo build plan and that does not work. So as I described before, changing the View from "//depot/... //tatula-client/..." to
"//depot/... //tatula-client/depot/..." and setting "//tatula-client/depot/..." as the depot will make the configuration work.

Unfortunately I don't have log available any more but I think you can replicate the issue with that.

Not a big issue, but the error message was not all that helpful when I tried to figure out why my normal configuration did not work..

Hi Tatu,

Apologies, but I am not exactly clear on what you mean.

The error you have received is usually because the depot format is incorrect. Bamboo is currently set up to have the depot in the format //<clientname>/<depotname>/... where depot name can contain anything that you want to identify the depot. (For example the view definition would be //myDepot/... //myClient/myDepot/... )
Perhaps the configuration you have is another case which we need to handle.

I guess what I need to know is how your configuration differs from the one i have described above. Perhaps you could provide what the actual View of the depot is as specified in the client specification (with dummy names is fine).

Also could you please attach your atlassian-bamboo.log. If you wish I can make this issue private.

Thanks,
Brydie