Up until about this May, the Jenkins Trigger plugin was writing the "Build is scheduled for" message in Jira comment when the build was scheduled by a Jira webhook. It stopped working since then. I can write the comment to the Jira API so it looks like the issue in on the jira-trigger plugin. Anyone else seeing this?
I believe I found the solution. It looks like we need to login manually to the Jira site as the Jenkins user to clear out dialog boxes that were added when Jira changed licensing models.
I encountered a similar strange problem, the "Build is scheduled for" message and trigger job building work fine yesterday, but not work today. The Jenkins plugin log seem fine "Received Webhook callback from changelog. Event type: jira:issue_updated". But no "Build is scheduled for" message in Jira and no related Jenkins build trigger.
I check the Jira user in Jenkins config, then log in Jira, I find there is a notification about authentication in Jenkins. Bad Requestoauth_problem "timestamp_refused", I will check the time on Jira and Jenkins server.
Related link: oauth-error-oauth_problem-timestamp_refused
Related
I am using this https://python-jenkins.readthedocs.io/en/latest/ python Jenkins API to create a job from XML config. Everything working fine except the webhook for Bitbucket server. I need to hit save/apply button at least once to activate the Webhook. Is there any way to call this Save/apply event through any script or API?
It would be a great help if anyone can suggest a solution.
This Problem is resolved with the latest update of Jenkins - Bitbucket server integration Plug-in
I'm newly implementing TeamCity and earlier was using Jenkins to implement CI. So I'm looking to know if there is any option (preferably inbuilt) to trigger TeamCity jobs by polling my mailbox and trigger when there is some mail with subject ::Ready to START::.
In Jenkins we have some plugin to poll our mail box and trigger the build, couldn't find similar option in TeamCity. Please help.
We have updated our Jenkins CI tool to updated version number is: 1.596.1. The problem is, for some projects, we cannot see the build console log. When we try to see the log, Jenkins responds with 404 error page.
Also, when this problem occurs in a particular job, we have examined that, failed builds are not be shown in the build history list in the job page. Even though we see that there is build from the gerrit history, when I click on the job with the specified ID, I again get the 404 error.
We are using Jenkins with Git/Gerrit, and most builds are triggered from the Gerrit review system.
New information: Jobs that have this problem have also the inconsistent timestamp problem.
It seems that this problem also occurs when Jenkins job is triggered by a patchset creation/merge in Gerrit review system.
What may be the root cause for this problem? Is it the version we're using or some other factor?
This is a persistent problem with Jenkins. A restart, which you can do from the front page when you're authenticated, is the fix. Visit
https://yoursite/jenkins/quietDown
to restart the instance.
I'm currently using Jenkins(1.451) and the Gerrit Trigger(2.3.1) to launch builds from Gerrit in order to verify code.
This is working fine as long as the project in Jenkins is configured as a "Free style" project. However, I'm currently setting up a new build pipeline where I'm using the "Build a maven2/3 project" option in order to take advantage of maven specific properties which I can't get from the "Free style" option. For some reason, Jenkins doesn't seem to trigger builds using this option. Nothing at all happens when I submit code to Gerrit which under normal circumstances should be picked up. I'm actually wondering if the Gerrit trigger is meant to work with Jenkins projects configured as a maven2/3 job or maybe it is the case that I can only use the Free style option in order to do this.ge
Could anyone confirm if this is the case?
Yes this will work. I suspect you might have some authentication issues that causes your jobs not to be triggered.
Check you sshd_log in the gerrit config folder to see if there are any jenkins logins that result in immediate LOGOUT. I my case I forgot to add Stream Events rights to the Non-Interactive Users under All-Projects and this caused some strange behavior.
This was the message I saw 3x per second in my sshd_log:
jenkins a/1000002 gerrit.stream-events 0ms 0ms not-admin
See here for more details
Does anyone know how to setup TeamCity so that it would create a new JIRA issue for each build breakage/failure?
We are trying to categorize/track/get-stats on our build breakages and need some kind of db. JIRA would most likely do the job.
If you can configure TeamCity to emit an email on failure, you can add issues in Jira via email.