[JIRA] (JENKINS-57620) JIRA Trigger not triggering on status change
Title: Message Title Michel Calvin commented on JENKINS-57620 Re: JIRA Trigger not triggering on status change Thanks for the quick response. We have figured out the issue. We have several Jenkins jobs that use the Jira trigger. If one of them has a syntax error in the JQL, this causes all of the jobs not to trigger. We have noticed this on our Windows Jenkins server which has dozens of jobs using the trigger. But on Windows, the Jenkins System Log provides an error message and we can quickly determine that the JQL is causing the issue and what job needs to be fixed. On Linux, no error is given in the logs. We are using the same Jenkins version on Linux and Windows. By chance we decided to verify all of the JQLs were valid and found the error. But we had to investigate every job until we discovered this. Is there a way to make the Jira trigger logs the same as what we see on Windows? Example below: (Windows) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199548.1558551175000.9583.1558563780086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57620) JIRA Trigger not triggering on status change
Title: Message Title Michel Calvin updated an issue Jenkins / JENKINS-57620 JIRA Trigger not triggering on status change Change By: Michel Calvin Attachment: image-2019-05-22-17-20-13-170.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199548.1558551175000.9581.1558563660108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57620) JIRA Trigger not triggering on status change
Title: Message Title
Michel Calvin created an issue
Jenkins / JENKINS-57620
JIRA Trigger not triggering on status change
Issue Type:
Bug
Assignee:
Wisen Tanasa
Attachments:
image-2019-05-22-13-49-33-661.png
Components:
jira-trigger-plugin
Created:
2019-05-22 18:52
Environment:
Jenkins version: 2.164.2 JIRA Trigger version: 1.0.0 JIRA Plugin: 3.0.6 Jenkins install on Linux
Priority:
Critical
Reporter:
Michel Calvin
The Jira Trigger in Jenkins is no longer working in our job. Jenkins job is setup to trigger when an issue is updated in JIRA. JQL is very simple and does show the item in Jira when placed in "Search Issues". If Jira issue is edited, the trigger executes and Jenkins job starts. If the status of the Jira issue is changed, the trigger does NOT execute. Even though the Post condition is set to trigger an issue updated event when the issue transition is done. Jenkins System log also shows Webhook is received as an issue_updated event. But the job never starts. Webhook event body: May 22, 2019 2:50:41 PM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook { "timestamp": 1558551041306, "webhookEvent": "jira:issue_updated", "issue_event_type_name": "issue_updated", } } May 22, 2019 2:50:41 PM FINE org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrap invoke Received Webhook callback from changelog. Event type: jira:issue_updated
[JIRA] (JENKINS-57288) NoClassDefFoundError on SingleConditionalBuilder
Title: Message Title Michel Calvin created an issue Jenkins / JENKINS-57288 NoClassDefFoundError on SingleConditionalBuilder Issue Type: Bug Assignee: Dominik Bartholdi Components: conditional-buildstep-plugin Created: 2019-05-01 21:27 Environment: Jenkins 2.164.2 Conditional Build Step 1.3.5 Token Macro 2.3 Priority: Major Reporter: Michel Calvin After upgrading Jenkins from 2.89.3 to 2.164.2 and then upgrading the Conditional Build step plugin to 1.3.6, we started seeing the following error whenever a Jenkins job is triggered using "Poll SCM". FATAL: org/jenkinsci/plugins/conditionalbuildstep/singlestep/SingleConditionalBuilder java.lang.NoClassDefFoundError: org/jenkinsci/plugins/conditionalbuildstep/singlestep/SingleConditionalBuilder at com.microfocus.application.automation.tools.octane.model.processors.projects.AbstractProjectProcessor.builderClassValidator(AbstractProjectProcessor.java:189) at com.microfocus.application.automation.tools.octane.model.processors.projects.AbstractProjectProcessor.processBuilders(AbstractProjectProcessor.java:145) at com.microfocus.application.automation.tools.octane.model.processors.projects.AbstractProjectProcessor.processBuilders(AbstractProjectProcessor.java:131) at com.microfocus.application.automation.tools.octane.model.processors.projects.FreeStyleProjectProcessor.(FreeStyleProjectProcessor.java:40) at com.microfocus.application.automation.tools.octane.model.processors.projects.JobProcessorFactory.getFlowProcessor(JobProcessorFactory.java:68) at com.microfocus.application.automation.tools.octane.model.processors.projects.JobProcessorFactory.getFlowProcessor(JobProcessorFactory.java:60) at com.microfocus.application.automation.tools.octane.tests.build.BuildHandlerUtils.getJobCiId(BuildHandlerUtils.java:138) at com.microfo
[JIRA] (JENKINS-50267) Trigger release in TFS failing with TF400813
Title: Message Title Michel Calvin updated an issue Jenkins / JENKINS-50267 Trigger release in TFS failing with TF400813 Change By: Michel Calvin Attachment: Release.zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50267) Trigger release in TFS failing with TF400813
Title: Message Title Michel Calvin commented on JENKINS-50267 Re: Trigger release in TFS failing with TF400813 Logs attached.Release.zipJenkinsLogs.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50267) Trigger release in TFS failing with TF400813
Title: Message Title Michel Calvin updated an issue Jenkins / JENKINS-50267 Trigger release in TFS failing with TF400813 Change By: Michel Calvin Attachment: JenkinsLogs.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50267) Trigger release in TFS failing with TF400813
Title: Message Title Michel Calvin commented on JENKINS-50267 Re: Trigger release in TFS failing with TF400813 Yes, that is correct. On successful completion of the Jenkins build, the TFS release definition is created and based on the conditions of the release a deploy is executed after the release is successfully created. The release definition tries to download the artifacts (Jenkins is primary) and fails with the error I provided previously. When I create the release from TFS, just to see if the error happens from Microsoft, I am prompted for the Jenkins build I want to pull artifacts from, the release is created and the deploy executes and completes successfully. The artifacts from Jenkins and TFS are downloaded with no errors and the remaining steps complete. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50267) Trigger release in TFS failing with TF400813
Title: Message Title Michel Calvin commented on JENKINS-50267 Re: Trigger release in TFS failing with TF400813 Thank you. That fixed the access issue and the Release is kicking off. Not sure if you can help with this, but when the release job tries to download the Jenkins artifact I get an error (see below). Creating and deploying the release manually from TFS works successfully. The download of the artifact only fails when it is kicked off by the Jenkins job. 2018-03-28T23:09:45.6989288Z Received Jenkins Artifact Details 2018-03-28T23:09:45.6989288Z Job Name: TFS Request Automation Test 2018-03-28T23:09:45.6989288Z BuildId: 457 2018-03-28T23:09:45.9284470Z An error occurred during download: Microsoft.VisualStudio.Services.Agent.Worker.Release.Artifacts.ArtifactDownloadException: Jenkins build 457 is invalid. at Microsoft.VisualStudio.Services.Agent.Worker.Release.Artifacts.JenkinsArtifact.d__6.MoveNext() — End of stack trace from previous location where exception was thrown — at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Services.Agent.Worker.Release.ReleaseJobExtension.<>c_DisplayClass29_2.d.MoveNext() — End of stack trace from previous location where exception was thrown — at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.VisualStudio.Services.Agent.Worker.Release.RetryExecutor.d__20.MoveNext() 2018-03-28T23:09:45.9374489Z ##[error]Jenkins build 457 is invalid. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50267) Trigger release in TFS failing with TF400813
Title: Message Title Michel Calvin created an issue Jenkins / JENKINS-50267 Trigger release in TFS failing with TF400813 Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2018-03-19 21:51 Environment: Jenkins 2.89.3; TFS 2017 on premise Priority: Major Reporter: Michel Calvin I have setup a TFS release job that has two artifacts - one from Jenkins and one from TFS Build. In the Jenkins "release" job, I have a post-build action to Trigger release in TFS. The userid is set to DOMAIN\userid (substituting the actual userid and Domain) and the correct password. This user has admin rights in TFS and for the TFS Release job. I get the below error. ERROR: Failed to trigger release.%n hudson.plugins.tfs.rm.ReleaseManagementException: hudson.plugins.tfs.rm.ReleaseManagementException: Error occurred.%nStatus: 401%nResponse: TF400813: Resource not available for anonymous access. Client authentication required. - Microsoft Team Foundation Server Add Comment
[JIRA] (JENKINS-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title Michel Calvin commented on JENKINS-50125 Re: Jenkins parameters missing in build when using jira trigger The project has parameters that are used in the build steps and are constant for each build run. No manual intervention is needed when the JIRA trigger kicks off the build. It uses the values from the parameters to tell the job where to pick up certain files, which dependent git repositories to use in the build, etc. I wasn't expecting the parameter mapping from the jira-trigger to replace the parameters from the Jenkins job. I can setup two jobs if that is the only workaround. Is it possible to consider an enhancement to the trigger that any parameter mapped with your trigger is "added" to the list of Jenkins parameters already defined in the job? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title Michel Calvin commented on JENKINS-50125 Re: Jenkins parameters missing in build when using jira trigger They are constant values set as read-only string parameters in the build job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title Michel Calvin created an issue Jenkins / JENKINS-50125 Jenkins parameters missing in build when using jira trigger Issue Type: Bug Assignee: Wisen Tanasa Attachments: jenkins parameters.PNG, JIRA Trigger parameter.PNG Components: jira-trigger-plugin Created: 2018-03-12 17:06 Environment: Jenkins 2.89.3, JIRA Trigger plugin 0.5.1, JIRA Plugin 2.5.1 Priority: Major Reporter: Michel Calvin I have several parameters defined for a Jenkins build through "The project is parameterized". I created a JIRA trigger with a changelog matcher and also added parameter mapping for a custom field to be used in a later build step. When I execute the build manually, the Jenkins parameters show up and the build runs. When it executes via the trigger, the only parameter available is the parameter mapped in the JIRA Trigger. The other parameters from "The project is parameterized" are not available in the build any longer.
