If you ever tried to do an integration activity in Perforce and have gotten a similar error message such as “no permission for operation on files(s)” then these are the steps you can do to resolve the problem:

1. Check to make sure your branch spec or the source/target does not have any typo.
2. Check to make sure you are branching within a source tree such as //softwareX/branches/1.0/… //softwareX/branches/1.1/… and NOT //softwareX/branches/1.0/… to //softwareY/branches/1.1/…
3. Check p4 protect to make sure your account has write permission within that code line.

If you ever wanted to evaluate Hudson CI tool, and ran into a problem while loading any plugin and you get the following error messages:

No ‘Plugin-Class’ entry in the manifest of …/path/to/plugin.hpi

Then you’re experiencing a problem I just experienced. The problem lies in the particular version of the hudson.war file. Like me, you probably retrieve an unofficial or out-dated version of the hudson.war.

If you have gotten “Perforce password (P4PASSWD) invalid or unset” error message when you’ve switched to the ticket based authentication, here’s what you can do to fix the problem:

p4 login -p -a

Simple. Straight forward.