It shows 404 error of JiraTestResultReporter configuration in Jenkins when I added the Jira URL "http://localhost:8080" which is hosted locally and clicked validation button.
My Jenkins server is also hosted locally and URL is "http://localhost:9091" which is run from blue-ocean docker file.
I tried a few ways as per below. But still has a problem.
Changing port for Jira
Restarting both Jira and Jenkins
My expected result would be a successful validation for this Jira URL when I do the validation.
I would very much appreciate if someone suggests upon this problem.
Related
I am trying to trigger a build in Jenkins directly from Xray. I have been successfully able to create a trigger in jira and has provided the webhook url and other information needed to run the build. But on triggering the build from any Test Plan, I am getting the following error:
Error publishing web request. Response HTTP status:503
ERROR: The requested URL could not be retrieved.
When i'm hitting the same webhook url in any browser, then the build is getting triggered in jenkins, hence it seems there's no issue with the provided webhook url.
One thing to note is that our Xray is in Jira cloud whereas the Jenkins is running behind a VPN. Can anyone help me in resolving the above issue?
If your Xray on Jira Cloud is trying to acess Jenkins, the Jenkins server needs to have a public URL. If you have it behind the firewall then it's not possible for Xray or any other tool to trigger it directly.
You can call the Jenkins URL from your browser because you are probably with your vpn connected.
The possible workaround would be to use a tool such as ngrok, as mentioned in the docs, to make a tunnel, but beware with the security implications of exposing your Jenkins url to the world.
For reference, Xray cloud provides documentation/examples showcasing how to take advantage of Jira Cloud automation capabilities to trigger jobs, for example in Jenkins.
Im having issue with gitlab plugin test connection on jenkins. it gives error when I hit the "test connection" button with the given values.
GitLab user is maintainer and has full access on it. GitLab API token belongs to this user.
unfortunately it seems no way to track this error. I checked the logs files in jenkins machine as well.
GitLab Plugin Version is -> 1.5.27
you may see screenshot of the page here
alternative link:
https://gyazo.com/2b81c4310c7a144651fda54c6b1462c1
I'm trying to use JIRA Trigger Jenkins plugin. I've read maybe all similar issues but can't understand why it doesn't work.
I want to build when an issue status changed. I troubleshooted but it didn't help me. My web hook works I checked it as it shows in documentation, the plugin for Jenkins is installed, firewall checked (I have whitelisted 3 Jira cloud IPs for Jenkins instance on AWS), ssl checks on Jenkins passes. Also I configured logs on Jenkins from Jira, but can't get anything.
In trigger configuration I inserted my Jira user's email (my-email#gmail.com) as user and password. The user has administrator privileges. What else can be wrong? Please any idea.
As i am trying to install Jenkins on cloud server and i installed that but after installation when it is asking for the /var/lib/jenkins/secrets/initialAdminPassword i am providing that also but after that i should get a plugin page but i am directly coming into Jenkins home page.
I have tried the installing jenkins again but still i am getting this below error.
Jenkins root URL is empty but is required for the proper operation of many Jenkins features like email notifications, PR status update, and environment variables such as BUILD_URL.
Please provide an accurate value in Jenkins configuration.
can any one tell me why this happening.enter image description here
I am getting error while integrating jenkins with JIRA.
Both JIRA and jenkins are hosted on same server.
Provided application URL in JIRA is my-ip:8080
error: No response was received from the URL you entered - it may not be valid. Please fix the URL below, if needed, and click Continue.
What ports are JIRA & Jenkins running on? Usually JIRA and Jenkins like to run on the same port (8080) by default. You can change the default port for starting Jenkins as ala something like java -jar jenkins.war --httpPort=9090
Did you see this link: Configuring the Atlassian JIRA plugin to work with Jenkins CI system