I’m having trouble with JPT (Jira Performance Tests) not recognizing my Jira address. I set up the test following the docs but it’s not working as expected.
Here’s what I did:
Set the Jira URI in the test file:
URI myJira = new URI("http://192.168.1.1:8080");
jiraOnPremiseTest.setAdminLogin("admin");
jiraOnPremiseTest.setAdminPassword("admin");
Ran the verify command in the btf-test folder:
./mvnw verify
But I’m getting errors about failing to run with the Jira address. The build fails with test errors.
My Jira is accessible at http://192.168.1.1:8080. Why can’t JPT recognize it? The repo hasn’t been updated in over a year. Could it be outdated?
Any ideas on how to fix this or what I might be doing wrong? Thanks for any help!
hey, had similar probs. make sure ur jira’s actually running n accessible from the test machine. sometimes it’s just that simple lol. also, try using the full url with context path like ‘http://192.168.1.1:8080/jira’ if u have a custom context. good luck mate!
I’ve run into this exact problem before, and it was a real headache to solve. In my case, the issue turned out to be related to SSL certificates. Even though I was using HTTP, Jira was still trying to redirect to HTTPS behind the scenes.
What worked for me was explicitly disabling SSL verification in the JPT configuration. You can do this by adding the following line to your test setup:
jiraOnPremiseTest.setIgnoreSslErrors(true);
This tells JPT to ignore any SSL-related issues and proceed with the connection anyway. It’s not ideal from a security standpoint, but it can help isolate whether the problem is truly SSL-related or something else.
Also, double-check that your Jira instance is actually running and accessible from the machine where you’re running the tests. Sometimes the simplest explanations are the correct ones - I once spent hours debugging only to realize my Jira instance had crashed!
If none of this helps, you might need to dig into the JPT source code or open an issue on their GitHub repo, even if it’s not actively maintained. Good luck!
I’ve encountered similar issues with JPT in the past. One thing to check is if your Jira instance is using HTTPS instead of HTTP. JPT can be finicky about this. Try changing your URI to ‘https://192.168.1.1:8080’ and see if that resolves the problem.
Another potential issue could be firewall or network settings blocking JPT’s access to your Jira instance. Ensure that there are no restrictions in place.
Regarding the repo being outdated, while that’s a valid concern, JPT should still work with most recent Jira versions. However, you might want to check if your Jira version is compatible with the JPT version you’re using.
If these suggestions don’t help, consider enabling verbose logging in JPT to get more detailed error messages, which might provide additional clues about the connection issue.