I'm configuring Jira trigger plugin (https://github.com/jenkinsci/jira-trigger-plugin) in Jenkins:
JIRA Trigger Configuration
We use Jira DC version and already set the webhook up as described in the documentation shared by #ceilfors. The Jenkins job is very simple:
Jenkins Build Triggers configuration
Also configured a Logger to triage any isue:
Configure log recorder
So when I add a comment on a task under project SNDBX I can see Jira is firing the webhook created:
Jira firing the webhook
However in Jenkins nothing happens, I checked "All Jenkins Logs" and I get:
Jenkins logs
And the logger for jira webhook is showing:
Jira Webhook logger
So the we webhook is "reaching" Jenkins somehow.
BTW, I have Jenkins over Java 8 installed:
Jenkins configuration xml file
Already fixed. It was an issue on my Jira server not trusting (SSL cert) Jenkins srvr.
Related
I have set up my Jira plugin within Jenkins with working credentials.
When I run the following script:
jiraComment body: 'Comment test', issueKey: 'CAT-98'
The build is successful but the Jira ticket does not get a new comment
Edit: There was some problem with the credentials. Also in the Jenkins build, the right URL needed to be selected
This is not a solution, but I would start by checking Jenkins logs (http://jenkins-srv:8080/log/all) to see if there's more info when the Jira plugin runs.
Or, even create a new Log Recorder to narrow the logs down to only Jira plugin related logs.
I am trying to trigger jenkins pipeline on gitlab push to branch and tag.
Using Jenkins ver. 2.176.2 and gitlab version 10.7.3-ee.
Although I have supposedly set up the webhooks properly, I do not see the jenkins job being triggered.
I have installed the gitlab plugin for jenkins, and configured the gitlab server, including the Personal Access Token for GitLab APIs access generated in gitlab.
I have defined the webhook (currently requesting trigger on all events). (for testing, ssl verification is off).
When testing the webhook in gitlab, I consistently receive HTTP error 500.
In jenkins pipeline job, I have selected "build when change is pushed to gitlab. gitlab webhook..." - this is the URL I used when defining the webhook in gitlab, under "integrations" section.
When pushing to gitlab, I see no event listed under "integrations -> recent deliveries",
I see no log under jenkins logs "com.dabsquared.gitlabjenkins" logger (set to log level "FINEST".
And lastly, the pipeline job is not triggered as I expected.
Any leads will be very helpful.
Adding printscreen of the Jenkins configuration of the gitlab for reference to the comment I added on possibility this is issue with the personal access token
Jenkins gitlab server configuration
Go to Settings of Gitlab Project -> Integrations and type in the Jenkins Job project url in 'URL'. URL should take either form:
http://JENKINS_URL/project/PROJECT_NAME
http://JENKINS_URL/project/FOLDER/PROJECT_NAME
Notice that the url does not contain "job" within it and instead uses "project".
Make sure under Triggers, you have "Push Events" checked as well if you want the job to trigger whenever someone pushes a commit.
Finally, run a build against your Jenkinsfile first before testing the webhook so Jenkins will pick-up the trigger settings for Gitlab.
Please refer the link for more details.
I have a Jenkins instance available over the internet. I have some jobs which need to be triggered manually (server start/server down). I found this cloudbees plugin which is supposed to work with on-prem Jenkins instance. However, when configuring the plugin it does not work.
Using the URL https://<jenkins_ur>/api/json on browser works, but cloudbess plugin complains about breadcrumb not found when trying to configure from Eclipse.
This question already has answers here:
How to trigger jenkins build upon bitbucket pull request merged
(2 answers)
Closed 5 years ago.
I have a Jenkins job which I want to trigger when I evaluate a pull request on Bitbucket. The Jenkins job is correctly configured (by the looks of it) with the 'Poll SCM' option checked.
I have setup the 'Bitbucket Server Webhook to Jenkins' as follows. When I click on 'Trigger Jenkins' as part of the configuration check, it works well. Corresponding logs on the Jenkins server show up properly.
Now, when I receive a pull request, I would want to trigger the same Jenkins job. However, which I click on the 'Trigger Build' option, nothing happens. The Jenkins job is not triggered. I dont see correspnding logs on the Jenkins server. No logs on the bitbucket server as well.
Where am I going wrong?
I am using an 'Atlassian Bitbucket v4.7.1' evaluation installation and a Jenkins 1.651 installation.
Just tried bitbucket 4.13 with webhook to jenkins for bitbucket 3.0.1 plugin. Follow the instruction on the plugin site, you need to install the git plugin on the jenkins side, enable git checkout and make sure it works, and enable polling of scm. The jenkins version used is pulled from docker hub with tag jenkins/jenkins:lts.
If the above does not work for you, from my reading you can have a few options as of today Nov 12 of 2017:
Use the generic post webhooks plugin that supports pull request trigger. And from jenkins pick it up with the generic webhooks plugin, then maybe do a secondary trigger from jenkins.
Upgrade the bitbucket server and webhooks to jenkins plugin. The server 4.13 does not work well with later webhooks to jenkins plugin. A paid version of the plugin probably is your best choice.
Or try bamboo that comes with the "plan banches" feature.
I cant figure out how to setup gerrit trigger plugin.
Manual build start builds current repo correctly. Test gerrit plugin connection is "Success".
Gerrit is configured according to plugin description article: https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger
Jenkins is 1.635; Gerrit trigger is 2.17.2. Gerrit is v2.11.3
Also tried "Type: plain. Pattern: project1, branches: */base/**" gerrit project settings. didnt work.
Gerrit trigger plugin global config:
Gerrit trigger plugin global config expanded (it has serveradmin user on the picture but i tried user created for jenkins as well):
Job settings:
Probably I'm missing something. Is there a way to figure out what's wrong? Maybe some console commands to figure out if gerrit jenkins user can reach the stream & plugin log?
It seems you need to update Gerrit to the last version and give the good "Access Right" to your Jenkins user.
Follow this set up