Cannot Edit Perforce Job Integration Settings After Migrating a JIRA Instance From One Server to Another

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

  1. Upon modifying the Perforce Job Integration (via Administration > Plugins > Enable Perforce Job Integration), a java.lang.RuntimeException is thrown.
  2. When JIRA starts up and attempts to load the Perforce properties, a java.lang.RuntimeException is thrown.
In Linux you should see:
Cause:
java.lang.RuntimeException: invalid perforce executable detected:[c:\Perforce\p4.exe]


Stack Trace:
java.lang.RuntimeException: invalid perforce executable detected:[/tools/dev/bin/p4]
at com.atlassian.jirafisheyeplugin.perforce.ValidEnv.ensurePathIsValid(ValidEnv.java:49)
at com.atlassian.jirafisheyeplugin.perforce.ValidEnv.getExecutable(ValidEnv.java:56)
at com.perforce.api.P4Process.pure_exec(P4Process.java:290)
at com.perforce.api.P4Process.exec(P4Process.java:266)
at com.atlassian.jirafisheyeplugin.perforce.PerforceConfigImpl.resolveServerAddress(PerforceConfigImpl.java:199)
at com.atlassian.jirafisheyeplugin.perforce.PerforceConfigImpl.createEnvironment(PerforceConfigImpl.java:129)
In Windows you should see:
Cause:
java.lang.RuntimeException: invalid perforce executable detected:[/tools/dev/bin/p4]


Stack Trace:
java.lang.RuntimeException: invalid perforce executable detected:[/tools/dev/bin/p4]
at com.atlassian.jirafisheyeplugin.perforce.ValidEnv.ensurePathIsValid(ValidEnv.java:49)
at com.atlassian.jirafisheyeplugin.perforce.ValidEnv.getExecutable(ValidEnv.java:56)
at com.perforce.api.P4Process.pure_exec(P4Process.java:290)
at com.perforce.api.P4Process.exec(P4Process.java:266)
at com.atlassian.jirafisheyeplugin.perforce.PerforceConfigImpl.resolveServerAddress(PerforceConfigImpl.java:199)
at com.atlassian.jirafisheyeplugin.perforce.PerforceConfigImpl.createEnvironment(PerforceConfigImpl.java:129)

Cause

The incorrect path is being used for the operating system. This bug is being tracked at FISH-431.

Workaround

Unable to render {include} The included page could not be found.

  1. Shutdown the JIRA instance.

  2. Run the following queries to remove any traces of perforce Job Integration on the database level:

    DELETE FROM propertytext WHERE id in (SELECT id FROM propertyentry WHERE PROPERTY_KEY LIKE 'fisheye.p4%');
DELETE FROM propertystring WHERE id in (SELECT id FROM propertyentry WHERE PROPERTY_KEY LIKE 'fisheye.p4%');
DELETE FROM propertyentry WHERE PROPERTY_KEY LIKE 'fisheye.p4%';

    (info) The above SQL may need to be changed depending on the DBMS used.

  3. Start JIRA again.

  4. Re-configure the Perforce Job Integration and verify it is correct.
Last modified on Feb 21, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.