[JIRA] (JENKINS-48430) Provided config file is sometimes not complete
Title: Message Title Dominik Bartholdi commented on JENKINS-48430 Re: Provided config file is sometimes not complete Aviad M can you provide some more background? so far I was not able to reproduce this issue, even with 10'000 executions of a job. e.g. how does your environment look like? master only? or slaves? what OS? size of files? config file type? ... 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort closed an issue as Fixed Mitch McLaughlin I can guarantee this particular deadlock is resolved. If you're seeing a new deadlock, please open a ticket and include the thread dump in it. Thanks Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Status: Reopened Closed Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54215) NullPointerException when the build result is null
Title: Message Title
Allan BURDAJEWICZ created an issue
Jenkins / JENKINS-54215
NullPointerException when the build result is null
Issue Type:
Bug
Assignee:
Kanstantsin Shautsou
Components:
block-queued-job-plugin
Created:
2018-10-24 06:24
Priority:
Major
Reporter:
Allan BURDAJEWICZ
If the last build is a job that is currently building but has a null build result, the JobResultBlockQueueCondition throws a NullPointerException:
Oct 24, 2018 4:21:46 PM jenkins.util.AtmostOneTaskExecutor$1 call
WARNING: null
java.lang.NullPointerException
at org.jenkinsci.plugins.blockqueuedjob.condition.JobResultBlockQueueCondition.isBlocked(JobResultBlockQueueCondition.java:70)
at org.jenkinsci.plugins.blockqueuedjob.BlockItemQueueTaskDispatcher.canRun(BlockItemQueueTaskDispatcher.java:35)
at hudson.model.Queue.getCauseOfBlockageForItem(Queue.java:1196)
at hudson.model.Queue.maintain(Queue.java:1553)
at hudson.model.Queue$1.call(Queue.java:324)
at hudson.model.Queue$1.call(Queue.java:321)
at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:108)
at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:98)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:112)
at java.lang.Thread.run(Thread.java:748)
How to reproduce Create 2 pipeline job `node {sleep 10} ` and one of those pipeline should be configured to block the build depending on the other one: "Block/Unblock task in queue > Block when last build result" with status UNSTABLE.
[JIRA] (JENKINS-51124) Trust Server Certificate not honoured for build failure messages
Title: Message Title Lasse Lindqvist commented on JENKINS-51124 Re: Trust Server Certificate not honoured for build failure messages Sorry, I was a bit unclear. What I meant was that for example https://github.com/jenkinsci/rocketchatnotifier-plugin/blob/master/src/main/java/jenkins/plugins/rocketchatnotifier/rocket/RocketChatClientCallBuilder.java#L89 Unirest.setHttpClient(clientBuilder.build()); does not seem to be using the parameter. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53930) Health Check Analyzer build step
Title: Message Title Daniel Gront updated JENKINS-53930 Jenkins / JENKINS-53930 Health Check Analyzer build step Change By: Daniel Gront Status: Open Fixed but Unreleased Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title Danny commented on JENKINS-54187 Re: EC2 Plugin deadlock leaving Jenkins unresponsive I'm facing the same behavior, running on Jenkins ver. 2.138.2 In fact, our ec2 plugin is old and rusty, 1.37. Jenkins goes AWOL jenkins.log 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title Danny updated an issue Jenkins / JENKINS-54187 EC2 Plugin deadlock leaving Jenkins unresponsive Change By: Danny Attachment: jenkins.log 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze edited a comment on JENKINS-54209 Re: Can't read file: Can't access the file Same here after update from jenkins 2.107.3 to 2.138.2 and cppcheck plugin update from 1.21 to 1.24! * jenkins 2.138.2 * cppcheck plugin 1.24 * cppcheck 1.85Report not located in subdirectory. Downgrade the cppcheck plugin to 1.21 is not a solution, because the plugin can't render the diff html file. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze edited a comment on JENKINS-54209 Re: Can't read file: Can't access the file Same here after update from jenkins 2.107.3 to 2.138.2 and cppcheck plugin update from 1.21 to 1.24! * jenkins 2.138.2 * cppcheck plugin 1.24 * cppcheck 1.85 Report not located in subdirectory. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze edited a comment on JENKINS-54209 Re: Can't read file: Can't access the file Same here after update from jenkins 2.107.3 to 2.138.2 and cppcheck plugin update from 1.21 to 1.24 ! * jenkins 2.138.2 * cppcheck plugin 1.24 * cppcheck 1.85 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Mike Scholze commented on JENKINS-54209 Re: Can't read file: Can't access the file Same here! jenkins 2.138.2 cppcheck plugin 1.24 cppcheck 1.85 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54093) Jenkins Jira Plugin sets connection timeout to default = 10 after Jenkins restart
Title: Message Title Torsten Boelting updated an issue Jenkins / JENKINS-54093 Jenkins Jira Plugin sets connection timeout to default = 10 after Jenkins restart Change By: Torsten Boelting We have following problem with the connection timeout parameter. We can change the parameter in the Jenkins-UI or in hudson.plugins.jira.JiraProjectProperty.xml, but after every restart of Jenkins it is set back in the UI to the default = 10. Value in the xml stays correct until we save the Jenkins configuration over UI.There are no additional informations in the log.To replicate:Change default connection timeout parameter for JIRA-Plugin in the Jenkins-UI oder or in the xml-file. Restart Jenkins. Lookup connection timeout parameter in the Jenkins-UI. 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. For more options, visit https://groups.google.com/d/optout.
jenkinsci-issues@googlegroups.com
Title: Message Title shama sagar commented on JENKINS-53203 Re: java.net.MalformedURLException: no protocol: updates.jenkins.io/update-center.json?id=default&version=2.121.2 Having similar issue, unable to update or install plugins: java.net.MalformedURLException: no protocol: ?id=default&version=2.107.3 at java.net.URL.(URL.java:593) at java.net.URL.(URL.java:490) at java.net.URL.(URL.java:439) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:190) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1640) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:186) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServlet
[JIRA] (JENKINS-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title Michal Matyjek commented on JENKINS-53920 Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again Started seeing the same on 1.40.1. Downgrading to 1.39 for now. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51124) Trust Server Certificate not honoured for build failure messages
Title: Message Title Martin Reinhardt commented on JENKINS-51124 Re: Trust Server Certificate not honoured for build failure messages that's wrong, it's also in the master: https://github.com/jenkinsci/rocketchatnotifier-plugin/blob/master/src/main/java/jenkins/plugins/rocketchatnotifier/rocket/RocketChatClientCallBuilder.java#L96 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Also, I can probably try to use the Jenkins version that was the last to use JNA 4.2.1. I think that is jenkins-2.135-1.1.noarch.rpm. I would like to at least go to Jenkins version 2.125 which fixes this issue: "Do not remove workspaces for projects with builds in progress. (issue 27329)". However, I was hoping to use a stable version. The first stable version at 2.125 or higher is 2.138 which is the one I originally tried to use that has JNA 4.5.2 and is missing the libjnidispatch.so that I need. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I was about to open a ticket at https://github.com/java-native-access/jna/issues/new, but the template comments in bug said to go to https://groups.google.com/forum/#!forum/jna-users first. I went there and started a discussion with subject "The libjnidispatch.so file is missing for Linux ppc64 from JNA 4.5.2 which is used with Jenkins 2.138+" 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Craig Rodrigues commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Yes you should ask on that project's site. In addition, I would recommend that you try to build the jna jar file from scratch on your ppc64 hardware and see if you can build the ppc64 library you need. ppc64 is not so commonly available hardware these days, so could be that the project maintainers don't have access to hardware to build the library you need. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path I looked at jna 4.2.1, 4.5.2, and 5.0.0 from https://github.com/java-native-access/jna/releases. In each tar.gz file I found a lib/native/linux-ppc64.jar file. When I unjarred these from each one, the jna 4.2.1 version contained a libjnidispatch.so. However, the others contained a file named "OUT_OF_DATE" with contents "This file is out of date and needs to be rebuilt". I wonder what that means. I wonder if that means that this version is no longer supported or that there build process is broken. I guess I will try to post something on the github link to try to figure out what is going on. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Craig Rodrigues commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path You are asking in the wrong place https://github.com/java-native-access/jna is a project separate from Jenkins, so you need to ask there about changes to the library. Also, does JNA 5.0.0 have the ppc64 library you need? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54214) NPE when no credentials provided on Gerrit SCM URL for Declarative Pipeline
Title: Message Title lucamilanesio created an issue Jenkins / JENKINS-54214 NPE when no credentials provided on Gerrit SCM URL for Declarative Pipeline Issue Type: Improvement Assignee: lucamilanesio Components: gerrit-code-review-plugin Created: 2018-10-23 23:42 Priority: Major Reporter: lucamilanesio When using the gerritReview task in a declarative pipeline without a valid credentials on the SCM side, instead of ignoring the task an NPE is raised. Add Comment This message was sent by Atlassi
[JIRA] (JENKINS-54213) MAC OS linked clone
Title: Message Title babak khoueinia created an issue Jenkins / JENKINS-54213 MAC OS linked clone Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2018-10-23 at 4.37.40 PM.png Components: vsphere-cloud-plugin Created: 2018-10-23 23:40 Priority: Major Reporter: babak khoueinia I am using the Vsphere plugin to implement linked clones on Windows, MAC and linux. For Windows and linux I was able to implement them successfully. However for MAC there is an issue. On configure system I set the "host key verification strategy" to "Non verifying verification strategy" but when a new build is triggered and the label clones a new VM along with the corresponding node, that node has "known hosts verification strategy" on configuration which in our case will not let the node connect to the VM. Has anyone else faced this issue before. Is there a fix to this? Add Comment
[JIRA] (JENKINS-54212) Jenkins Gerrit webhook not working for refUpdated events
Title: Message Title lucamilanesio created an issue Jenkins / JENKINS-54212 Jenkins Gerrit webhook not working for refUpdated events Issue Type: Improvement Assignee: lucamilanesio Components: gerrit-code-review-plugin Created: 2018-10-23 23:33 Priority: Major Reporter: lucamilanesio When a Gerrit refUpdated event is triggered through webhooks, the relevant jenkins job isn't rescanned. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Mitch McLaughlin reopened an issue I just encountered this issue again with a client using workflow-cps:2.53. Let me know what information I can supply to help look into this. Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Mitch McLaughlin Resolution: Done Status: Closed Reopened 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem in multi module projects
Title: Message Title Cyrille Le Clerc commented on JENKINS-54139 Re: Jacoco report rendering problem in multi module projects Here is the right version https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.5.15-beta-4/pipeline-maven-3.5.15-beta-4.hpi 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54196) Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path
Title: Message Title Peter Toennies commented on JENKINS-54196 Re: Regression: jnidispatch (/com/sun/jna/linux-ppc64/libjnidispatch.so) not found in resource path Was the ppc64 support removed in the more recent JNA versions intentionally or was this an oversight? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48430) Provided config file is sometimes not complete
Title: Message Title Aviad M edited a comment on JENKINS-48430 Re: Provided config file is sometimes not complete For some reason my thread has been closed. We suffer from this a lot. Plugin version: 2.18Jenkins version: 2.89 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48430) Provided config file is sometimes not complete
Title: Message Title Aviad M commented on JENKINS-48430 Re: Provided config file is sometimes not complete For some reason my thread has been closed. We suffer from this a lot. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54193) Ability to limit number of pipelines shown in Jenkins pipeline based views
Title: Message Title Tommy Tynjä updated JENKINS-54193 Proposed solution merged to master. Will be featured in the next release of the Delivery Pipeline plugin. Jenkins / JENKINS-54193 Ability to limit number of pipelines shown in Jenkins pipeline based views Change By: Tommy Tynjä Status: In Progress Fixed but Unreleased Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53888) Batch step running on a node other than the master fails
Title: Message Title mishal shah edited a comment on JENKINS-53888 Re: Batch step running on a node other than the master fails Started seeing this after updating Pipeline: Nodes and Processes (2.22 -> 2.24) and Durable Task Plugin (1.25 -> 1.26). ERROR: script apparently exited with code 0 but asynchronous notification was lost 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53888) Batch step running on a node other than the master fails
Title: Message Title mishal shah commented on JENKINS-53888 Re: Batch step running on a node other than the master fails Started seeing this after updating Pipeline: Nodes and Processes (2.22 -> 2.24) and Durable Task Plugin (1.25 -> 1.26). 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35359) Limit concurrent builds for 1 MultiBranch project
Title: Message Title Quentin Hartman commented on JENKINS-35359 Re: Limit concurrent builds for 1 MultiBranch project I agree that the lock, even outside the context of node isn't really a solution here. I have two builds, A and B. Build A requires that it is build one at a time on a node. Build B does not. If what I've seen is correct, a resource locked by build A will prevent build B from running on that resource as well. This is not what I want. Am I missing something? There's no reason to waste the time waiting for A to finish when I have B builds waiting to go. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem in multi module projects
Title: Message Title Cyrille Le Clerc commented on JENKINS-54139 Re: Jacoco report rendering problem in multi module projects there is a glitch in the beta-3 release, the fix is missing. Please wait for the beta-4 release 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title lucamilanesio closed an issue as Fixed Jenkins / JENKINS-49692 Could not update folder level actions from source Change By: lucamilanesio Status: Resolved Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49692) Could not update folder level actions from source
Title: Message Title lucamilanesio updated an issue Jenkins / JENKINS-49692 Could not update folder level actions from source Change By: lucamilanesio Released As: gerrit-code-review-0.2 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49985) hudson.remoting.ProxyException: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object '{"labels":{"Verified":1}}' with class 'com.google.gson.JsonObje
Title: Message Title
lucamilanesio updated JENKINS-49985
Jenkins / JENKINS-49985
hudson.remoting.ProxyException: org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object '{"labels":{"Verified":1}}' with class 'com.google.gson.JsonObject' to class 'com.google.gson.JsonElement'
Change By:
lucamilanesio
Status:
Fixed but Unreleased Closed
Released As:
gerrit-code-review-0.2
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49695) Could not fetch branches from source while using Discover open changes
Title: Message Title lucamilanesio updated JENKINS-49695 Jenkins / JENKINS-49695 Could not fetch branches from source while using Discover open changes Change By: lucamilanesio Status: Fixed but Unreleased Closed Released As: gerrit-code-review-0.2 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49713) gerrit-plugin exposes change-requests as normal branches instead of pull-requests
Title: Message Title lucamilanesio updated JENKINS-49713 Jenkins / JENKINS-49713 gerrit-plugin exposes change-requests as normal branches instead of pull-requests Change By: lucamilanesio Status: In Review Closed Resolution: Fixed Released As: gerrit-code-review-0.2 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49983) NullPointerException from gerrit plugin due to lack of configuration
Title: Message Title lucamilanesio updated JENKINS-49983 Jenkins / JENKINS-49983 NullPointerException from gerrit plugin due to lack of configuration Change By: lucamilanesio Status: In Review Closed Resolution: Fixed Released As: gerrit-code-review-0.2 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50783) Support file based comments
Title: Message Title lucamilanesio updated JENKINS-50783 Jenkins / JENKINS-50783 Support file based comments Change By: lucamilanesio Status: In Review Closed Resolution: Fixed Released As: gerrit-code-review-0.2 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54070) Support for Jenkinsfile declarative pipelines
Title: Message Title lucamilanesio updated an issue Jenkins / JENKINS-54070 Support for Jenkinsfile declarative pipelines Change By: lucamilanesio Released As: gerrit-code-review-0.2 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50930) Multibranch fails if gerrit lives at a subdirectory
Title: Message Title lucamilanesio updated JENKINS-50930 Jenkins / JENKINS-50930 Multibranch fails if gerrit lives at a subdirectory Change By: lucamilanesio Status: Fixed but Unreleased Closed Released As: gerrit-code-review-0.2 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54070) Support for Jenkinsfile declarative pipelines
Title: Message Title lucamilanesio closed an issue as Fixed Jenkins / JENKINS-54070 Support for Jenkinsfile declarative pipelines Change By: lucamilanesio Status: Resolved Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53888) Batch step running on a node other than the master fails
Title: Message Title Oleg Nenashev commented on JENKINS-53888 Re: Batch step running on a node other than the master fails CC Sam Van Oort Jesse Glick . Could it be related to the recent regression in Pipeline? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54070) Support for Jenkinsfile declarative pipelines
Title: Message Title lucamilanesio updated JENKINS-54070 Jenkins / JENKINS-54070 Support for Jenkinsfile declarative pipelines Change By: lucamilanesio Status: In Review Resolved Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54211) List all available apis in the app
Title: Message Title Ben Creasy created an issue Jenkins / JENKINS-54211 List all available apis in the app Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-10-23 18:57 Priority: Minor Reporter: Ben Creasy I did a search in the issues on things like api all api endpoints, api public and didn't see anything. Jenkins has APIs under some of the objects exposed as URLs, but it's not clear how to get a list of all the endpoints. This is a somewhat common question that has never gone well-answered, for example: https://stackoverflow.com/questions/49074011/how-to-get-a-list-of-all-available-jenkin-apis?noredirect=1&lq=1 points to http://localhost:8080/api/ - but this does not provide a complete list according to https://stackoverflow.com/a/18349385 - "To find which objects expose APIs, search for _api.jelly in https://github.com/jenkinsci/jenkins/find/master (press 't' then type '_api.jelly')" - not sure if this is 100% reliable
[JIRA] (JENKINS-54211) List all available apis in the app
Title: Message Title Ben Creasy updated an issue Jenkins / JENKINS-54211 List all available apis in the app Change By: Ben Creasy I did a search in the issues on things like _api all_ , _api endpoints_, _api public_ and didn't see anything.Jenkins has APIs under some of the objects exposed as URLs, but it's not clear how to get a list of all the endpoints.This is a somewhat common question that has never gone well-answered, for example: * [https://stackoverflow.com/questions/49074011/how-to-get-a-list-of-all-available-jenkin-apis?noredirect=1&lq=1] ** points to [http://localhost:8080/api/] - but this does not provide a complete list * according to [https://stackoverflow.com/a/18349385] - "To find which objects expose APIs, search for _api.jelly in [https://github.com/jenkinsci/jenkins/find/master] (press 't' then type '_api.jelly')" - not sure if this is 100% reliable 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54210) Jenkins integration with load runner
Title: Message Title mohan jayaram created an issue Jenkins / JENKINS-54210 Jenkins integration with load runner Issue Type: Task Assignee: Steven Hermans Components: microdocs-integration-plugin Created: 2018-10-23 18:42 Environment: version:-jenkins ver 2.138.2 loadrunner version :-12.57 microfocus :5.5 Priority: Major Reporter: mohan jayaram Hi, i am trying to run my loadrunner script from jenkins . it is executing my script fine but it is throwing below error when recording the error .ERROR: Step 'Publish Micro Focus tests result' aborted due to exception: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 12:45:58 Cleaning up the environment...12:45:58 12:45:58 Run status: Job unstable (Passed with failed tests), total tests: 1, succeeded: 0, failures: 1, errors: 0*12:45:58* Failed : C:\Jenkins\Scenario1.lrs*12:45:58* 12:45:58 Build step 'Execute Micro Focus tests from file system' changed build result to UNSTABLE*12:45:58* FATAL: Remote call on JNLP4-connect connection from crwsa/162.123.119.166:5053 failed*12:45:58* Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from /162.123.119.166:5053*12:45:58* at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)12:45:58 at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)12:45:58 at hudson.remoting.Channel.call(Channel.java:955)12:45:58 at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1084)12:45:58 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:510)12:45:58 at hudson.model.Run.execute(Run.java:1819)12:45:58 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)12:4
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Devin Nusbaum commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException For anyone still seeing the original exception in the description, try adding a custom logger (Manage Jenkins -> System Log -> Add new log recorder) at FINE level for org.jenkinsci.plugins.workflow.support.concurrent.Timeout, so that we see these log messages, and then next time you see the issue, add the output of the custom logger here, which will tell us if my hypothesis is correct, and if so, it will tell us what code was actually running at the time of the issue. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53689) Unity3d Failed To Build due to mergeReleaseResources FAILED error
Title: Message Title Dogukan Erkut resolved as Fixed It seems that the issue was caused due to being a SYSTEM user rather than my own admin user. Follow this link, instead of "Team City Build Agent", look for "Jenkins" service and Log on with your own user, then the build can proceed without any problems. Jenkins / JENKINS-53689 Unity3d Failed To Build due to mergeReleaseResources FAILED error Change By: Dogukan Erkut Status: Open Resolved Assignee: lacostej Dogukan Erkut Resolution: Fixed 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-i
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Devin Nusbaum commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Andrew a The exception in your most recent build looks like a networking issue after you manually aborted the build. Here is the stack trace: org.jenkinsci.plugins.workflow.steps.FlowInterruptedException at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.interrupt(CpsFlowExecution.java:1125) at org.jenkinsci.plugins.workflow.job.WorkflowRun$2$1.run(WorkflowRun.java:378) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Suppressed: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.Channel.call(Channel.java:954) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1084) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.stop(FileMonitoringTask.java:304) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.stop(DurableTaskStep.java:258) at org.jenkinsci.plugins.workflow.cps.CpsThread.stop(CpsThread.java:296) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$6.onSuccess(CpsFlowExecution.java:1139) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$6.onSuccess(CpsFlowExecution.java:1128) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:906) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ... Suppressed exception repeated for each parallel block And the serialized FlowInterruptedException has: andrianov
[JIRA] (JENKINS-51716) Blueocean stuck in loading
Title: Message Title Mark Bretl commented on JENKINS-51716 Re: Blueocean stuck in loading I see this same JS stacktrace with Jenkins 2.138.2 and BlueOcean 1.9.0 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54209) Can't read file: Can't access the file
Title: Message Title Amo Mamo created an issue Jenkins / JENKINS-54209 Can't read file: Can't access the file Issue Type: Bug Assignee: Marco Steffan Attachments: 1.png Components: cppcheck-plugin Created: 2018-10-23 17:56 Priority: Major Reporter: Amo Mamo Hello I have: Jenkins ver. 2.138.2 for NAT. Cppcheck 1.85 Cppcheck Plugin 1.24 When I try to view a detailed scan result (example: https://wiki.jenkins.io/download/attachments/37749668/1.15_code.png?version=1&modificationDate=139526094&api=v2) I get the error "Can't read file: Can ' t access the file: file: ". Inside the local network everything is allowed. Connection to the node via SSH. Jenkins on Linux, node on Linux. What should I do? Add Comment
[JIRA] (JENKINS-15445) DefaultBuilderDescriptorLister should not check buildstep class for @DataBoundConstructor
Title: Message Title Alex Taylor commented on JENKINS-15445 Re: DefaultBuilderDescriptorLister should not check buildstep class for @DataBoundConstructor Nicolas De Loof This PR does not seem to cause issues with the latest version of Jenkins anymore. Can we get it re-attempted or am I just missing something? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51124) Trust Server Certificate not honoured for build failure messages
Title: Message Title Lasse Lindqvist commented on JENKINS-51124 Re: Trust Server Certificate not honoured for build failure messages Maybe because trustSSL is used only in one branch here? https://github.com/jenkinsci/rocketchatnotifier-plugin/blob/develop/src/main/java/jenkins/plugins/rocketchatnotifier/rocket/RocketChatClientCallBuilder.java#L95 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Nick Jones commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Thanks palfrey – I downgraded workflow-cps (aka Pipeline: Groovy) plugin to 2.58 and the exceptions have stopped. I've updated the component here accordingly. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Nick Jones Component/s: workflow-cps-plugin Component/s: disable-github-multibranch-status-plugin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Nick Jones Environment: Jenkins 2.138.2 LTS, Git 3.9.1, Disable GitHub Multibranch Status 1 Pipeline Groovy 2 . 1 59 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54208) Groovy compilation error in Splunk Plugin Extension
Title: Message Title
Pushpendra Raghav created an issue
Jenkins / JENKINS-54208
Groovy compilation error in Splunk Plugin Extension
Issue Type:
New Feature
Assignee:
Ted
Components:
splunk-devops-plugin
Created:
2018-10-23 16:44
Environment:
Installed Plugins - com.splunk.splunkins:splunk-devops-extend:1.7.0 https://wiki.jenkins.io/display/JENKINS/Splunk+Plugin+for+Pipeline+Job+Support Jenkins 2.89
Labels:
plugin
Priority:
Minor
Reporter:
Pushpendra Raghav
We are using Splunk Plugin Extension so that we can send Console output logs of a Pipeline job to Splunk. Here is one such sample pipeline job which is working fine but as soon as I add sendSplunkConsoleLog { } to it then it starts throwing Groovy Compilation errors. pipeline{ agent{ node { label 'testnode' } } sendSplunkConsoleLog { // some block stages { stage ('Checkout') { steps { git 'http://abc@xyz:7990/scm/prot/apitestautomation_postman_newman.git' } } } } } Console output log Started by user Raghav, Pushpendra Running in Durability level: MAX_SURVIVABILITY org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 4: Undefined section "sendSplunkConsoleLog" @ line 4, column 6. sendSplunkConsoleLog { ^ WorkflowScript: 1: Missing required section "stages" @ line 1, column 1. pipeline{ ^ 2 errors at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNode
[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-54187 Re: EC2 Plugin deadlock leaving Jenkins unresponsive Are you using the spot instance ? the 1.40 and the 1.41 use the same algorithm for calculate the nodes that is needed. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title palfrey commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults I downgraded workflow-cps to 2.58 (from https://updates.jenkins.io/download/plugins/workflow-cps/) and it all appears to be working again 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-54207 Update delete plugin flow to error out for anything other than file not found Change By: Baptiste Mathus Assignee: R. Tyler Croy 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Pod name is detected as `localhost` in Bluemix IKS
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Pod name is detected as `localhost` in Bluemix IKS
I have build the pull request, it works!finally able to execute commands in a container with a simple jenkinsfile like: {code:java}// Developers input is required here.def appname = "AddressManagement"def jarname = "AddressManagement.jar"// Jenkins Deployment Variables and Credentialsdef cloud = env.CLOUD ?: "kubernetes"def registryCredsID = env.REGISTRY_CREDENTIALS ?: "registry-credentials-id"def camundaRepoID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-repo-id"def camundaLicenseID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-lic-id"def serviceAccount = env.SERVICE_ACCOUNT ?: "default"def sonarCredsID = "sonarID"appname = appname.toLowerCase()// Pod Environment Variablesdef kubenamespace = "default"def regnamespace = "blw-msa"def registry = env.REGISTRY ?: "registry.eu-de.bluemix.net"podTemplate(label: 'mypod', cloud: cloud, serviceAccount: serviceAccount, kubenamespace: kubenamespace, envVars: [envVar(key: 'NAMESPACE', value: kubenamespace),envVar(key: 'REGNAMESPACE', value: regnamespace), envVar(key: 'JARNAME', value: jarname),envVar(key: 'APPNAME', value: appname),envVar(key: 'REGISTRY', value: registry)],volumes: [//hostPathVolume(hostPath: '/etc/docker/certs.d', mountPath: '/etc/docker/certs.d'),//hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock') //hostPathVolume(hostPath: '/tmp/gradle', mountPath: '/root/.gradle/caches/')],containers: [// In Theory, java container is not needed as the normal jenkins jnlp slave would be capable of executing gradle. // But as we mount the cache from host, we need a root user running inside the build container, otherwise gradle wont be able to write to .gradlecontainerTemplate(name: 'java', image: 'openjdk:8-jdk', ttyEnabled: true, command: 'cat') ]) {node('mypod') {stage('Checkout') { echo "test" }container('java') { stage('Static Code Analysis') { sh "java -version"}}}}{code} Strangely enough, the following Jenkinsfile does not run: Is always waiting for executor: {code:java}// Developers input is required here.def appname = "AddressManagement"def jarname = "AddressManagement.jar"// Jenkins Deployment Variables and Credentialsdef cloud = env.CLOUD ?: "kubernetes"def registryCredsID = env.REGISTRY_CREDENTIALS ?: "registry-credentials-id"def camundaRepoID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-repo-id"def camundaLicenseID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-lic-id"def serviceAccount = env.SERVICE_ACCOUNT ?: "jenkins"def sonarCredsID = "sonarID"appname = appname.toLowerCase()// Pod Environment Variablesdef kubenamespace = "default"def regnamespace = "blw-msa"def registry = env.REGISTRY ?: "registry.eu-de.bluemix.net"podTemplate(label: 'mypod', cloud: cloud, serviceAccount: serviceAccount, kubenamespace: kubenamespace, envVars: [envVar(key: 'NAMESPACE', value: kubenamespace),envVar(key: 'REGNAMESPACE', value: regnamespace), envVar(key: 'JARNAME', value: jarname),envVar(key: 'APPNAME', value: appname),envVar(key: 'REGISTRY', value: registry)],containers: [// In Theory, java container is not needed as the normal jenkins jnlp slave would be capable of executing gradle. // But as we mount the cache from host, we need a root user running inside the build container, otherwise gradle wont be able to write to .gradle containerTemplate(name: 'helm', image: 'lachlanevenson/k8s-helm:v2.9.1', ttyEnabled: true, command: 'cat'),containerTemplate(name: 'ja
[JIRA] (JENKINS-53297) Pod name is detected as `localhost` in Bluemix IKS
Title: Message Title
leon gregori commented on JENKINS-53297
Re: Pod name is detected as `localhost` in Bluemix IKS
I have build the pull request, it works! finally able to execute commands in a container with a simple jenkinsfile like:
// Developers input is required here.
def appname = "AddressManagement"
def jarname = "AddressManagement.jar"// Jenkins Deployment Variables and Credentials
def cloud = env.CLOUD ?: "kubernetes"
def registryCredsID = env.REGISTRY_CREDENTIALS ?: "registry-credentials-id"
def camundaRepoID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-repo-id"
def camundaLicenseID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-lic-id"
def serviceAccount = env.SERVICE_ACCOUNT ?: "default"
def sonarCredsID = "sonarID"
appname = appname.toLowerCase()
// Pod Environment Variables
def kubenamespace = "default"
def regnamespace = "blw-msa"
def registry = env.REGISTRY ?: "registry.eu-de.bluemix.net"podTemplate(label: 'mypod', cloud: cloud, serviceAccount: serviceAccount, kubenamespace: kubenamespace, envVars: [
envVar(key: 'NAMESPACE', value: kubenamespace),
envVar(key: 'REGNAMESPACE', value: regnamespace),
envVar(key: 'JARNAME', value: jarname),
envVar(key: 'APPNAME', value: appname),
envVar(key: 'REGISTRY', value: registry)
],
volumes: [
//hostPathVolume(hostPath: '/etc/docker/certs.d', mountPath: '/etc/docker/certs.d'),
//hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock')
//hostPathVolume(hostPath: '/tmp/gradle', mountPath: '/root/.gradle/caches/')
],
containers: [
// In Theory, java container is not needed as the normal jenkins jnlp slave would be capable of executing gradle.
// But as we mount the cache from host, we need a root user running inside the build container, otherwise gradle wont be able to write to .gradle
containerTemplate(name: 'java', image: 'openjdk:8-jdk', ttyEnabled: true, command: 'cat')
]) {node('mypod') {
stage('Checkout') {
echo "test"
}
container('java') {
stage('Static Code Analysis') {
sh "java -version"}
}
}
}
Strangely enough, the following Jenkinsfile does not run:
// Developers input is required here.
def appname = "AddressManagement"
def jarname = "AddressManagement.jar"// Jenkins Deployment Variables and Credentials
def cloud = env.CLOUD ?: "kubernetes"
def registryCredsID = env.REGISTRY_CREDENTIALS ?: "registry-credentials-id"
def camundaRepoID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-repo-id"
def camundaLicenseID = env.CAMUNDA_REPO_CREDENTIALS ?: "camunda-lic-id"
def serviceAccount = env.SERVICE_ACCOUNT ?: "jenkins"
def sonarCredsID = "sonarID"
appname = appname.toLowerCase()// Pod Environment Variables
def kubenamespace = "default"
def regnamespace = "blw-msa"
def registry = env.REGISTRY ?: "registry.eu-de.bluemix.net"podTemplate(label: 'mypod', cloud: cloud, serviceAccount: serviceAccount, kubenamespace: kubenamespace, envVars: [
envVar(key: 'NAMESPACE', value: kubenamespace),
envVar(key: 'REGNAMESPACE', value: regnamespace),
envVar(key: 'JARNAME', value: jarname),
envVar(key: 'APPNAME', value: appname),
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title palfrey commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Judging from the call changes, it might be the work in https://github.com/jenkinsci/workflow-cps-plugin/pull/257 that did this? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title Renzo Crisóstomo commented on JENKINS-54187 Re: EC2 Plugin deadlock leaving Jenkins unresponsive We've downgraded the plugin to a version build on top of revision 67aba04d0c60e8db1134d068ea2c10bc3e961c90 (1.40.0) today, which was stable for us prior our upgrade to the latest LTS (2.138.2). So far we haven't experience any deadlocks, but it might be related to the fact that this version is more conservative when spinning up new build nodes therefore less need to handle concurrency. We are back to the same amount of build nodes we used to have. I'll report back if this changes. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46119) Use the job name in context string
Title: Message Title Fabian Holler commented on JENKINS-46119 Re: Use the job name in context string When you run multiple Jenkins job per Github PR you currently end up with having several "continuous-integration/jenkins/" status messages. It's unclear which status refers to which CI job (build, test, etc). Alternatively being able to disable posting the status to github from the plugin at all would help. Then I could post the status myself with a script with the information I want. When I currently do this, I end up with multiple status messages for the same job run in github. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title Mandie Smith created an issue Jenkins / JENKINS-54207 Update delete plugin flow to error out for anything other than file not found Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-23 14:39 Labels: evergreen newbie-friendly Priority: Minor Reporter: Mandie Smith This is in reference to this comment The error handling for plugin and directory deletions should fail silently if file or directory not found. However, if we get any other error when attempting deletions, then the method should return an error. Add Comment
[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Title: Message Title Paul Allen updated JENKINS-50975 Ready for release. Jenkins / JENKINS-50975 Concurrent Groovy Shared Library syncs on different jobs use same workspace root Change By: Paul Allen Status: Reopened Fixed but Unreleased Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-50975 Concurrent Groovy Shared Library syncs on different jobs use same workspace root Change By: Paul Allen Labels: P4_A root shared-groovy-libraries sync 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53149) GitHubCommitStatusSetter is not reading proper commit id from a shared library
Title: Message Title Manuel de la Peña resolved as Fixed Jenkins / JENKINS-53149 GitHubCommitStatusSetter is not reading proper commit id from a shared library Change By: Manuel de la Peña Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/github-plugin/releases/tag/v1.29.3 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54142) Refusing to marshal jenkins.plugins.publish_over.BPInstanceConfig for security reasons
Title: Message Title Oleg Nenashev resolved as Cannot Reproduce No response from the requester Jenkins / JENKINS-54142 Refusing to marshal jenkins.plugins.publish_over.BPInstanceConfig for security reasons Change By: Oleg Nenashev Status: Open Resolved Resolution: Cannot Reproduce 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Gavin Williams edited a comment on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults [~markewaite] So I'm playing whack-a-mole with Plugins atm, to try and identify which plugin upgrade broke things for us... So far, I've ruled out: * scm-api * workflow-scm-step * github-branch-source * github Edit: So after downgrading the _github_ plugin, the exceptions are _still_ being logged, however the Commit status' are now being updated correctly... So I'm not sure on the cause and effect there... 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Pascal Laporte commented on JENKINS-50429 Re: Shell command are really slower than before We have already try to send a single WatchExec that combine all the env variable. It didn't changed much the resulting elapse on the total job. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser hello, is it normal that using new plugin, I don't find anymore the choice to parse directly the console output instead of a specific report file ? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Carlos Sanchez commented on JENKINS-50429 Re: Shell command are really slower than before the cause is all the environment variables being sent in https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/ContainerExecDecorator.java#L398 but it doesn't matter if all of them get sent together or separately to the container, same times. I'm not sure if we can avoid sending them or send them once 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Gavin Williams edited a comment on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults [~markewaite] So I'm playing whack-a-mole with Plugins atm, to try and identify which plugin upgrade broke things for us... So far, I've ruled out: * scm-api * workflow-scm-step * github-branch-source * github 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35124) Allow limiting by domain without google apps
Title: Message Title Ryan Campbell closed an issue as Fixed Please just open a new issue rather than reopening one which has been completed for ages. Jenkins / JENKINS-35124 Allow limiting by domain without google apps Change By: Ryan Campbell Status: Reopened Closed Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Gavin Williams commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Mark Waite So I'm playing whack-a-mole with Plugins atm, to try and identify which plugin upgrade broke things for us... So far, I've ruled out: scm-api workflow-scm-step github-branch-source 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title ASHOK MOHANTY commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container Thanks, able to catch the user code issue. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
Ruslan Zenin edited a comment on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Hi [~jglick] . would it be possible to provide a sample pipeline script how we can accomplish _"git push withCredentials or sshagent"_? There is a use case for my team to build projects and change some of the artifacts and then push back to the SCM.Thank you in advance! Note: I found this example: [https://jenkins.io/doc/pipeline/examples/#push-git-repo]withCredentials([usernamePassword(credentialsId: 'git-pass-credentials-ID', passwordVariable: 'GIT_PASSWORD', usernameVariable: 'GIT_USERNAME')]) \{ sh("git tag -a some_tag -m 'Jenkins'") sh('git push https://${GIT_USERNAME}:${GIT_PASSWORD}@ --tags') }
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54206) Merged PRs not being removed from multibranch
Title: Message Title Gunter Grodotzki created an issue Jenkins / JENKINS-54206 Merged PRs not being removed from multibranch Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2018-10-23 at 15.31.49.png Components: github-branch-source-plugin Created: 2018-10-23 13:33 Priority: Minor Reporter: Gunter Grodotzki When a PR gets merged in, it is still active in Jenkins. Merged in PRs or deleted PRs/branches should be removed. Add Comment
[JIRA] (JENKINS-54102) Endless builds with local branch checked out
Title: Message Title
Joachim Haga commented on JENKINS-54102
Re: Endless builds with local branch checked out
A workaround is to add a shell (or batch) build step,
git checkout ${GIT_COMMIT} # to detach, otherwise the delete below fails
git branch -D ${GIT_LOCAL_BRANCH}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54205) Blue Ocean Editor modifies a declarative Jenkinsfile without warning
Title: Message Title
Manuel Cardenas created an issue
Jenkins / JENKINS-54205
Blue Ocean Editor modifies a declarative Jenkinsfile without warning
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-pipeline-editor-plugin
Created:
2018-10-23 13:18
Priority:
Major
Reporter:
Manuel Cardenas
@Library('bitwiseman-shared@blog/declarative/notifications') _
pipeline {
...
If you open a BO editor page or you modify the pipeline using BO interface, the annotation gets removed. Is this an expected behavior? Interestingly, if you put that code directly in the GitHub repo, it will work, but if you edit the code using the BO UI the code gets removed. https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-pipeline-editor/src/main/js/services/PipelineValidator.js#L83 We should be able to warn users about this modification. That would happen not only with shared libraries but with anything outside the pipeline block.
[JIRA] (JENKINS-22954) Setting Label String in Groovy Appears to only have a Delayed Effect.
Title: Message Title Daniel Beck commented on JENKINS-22954 Re: Setting Label String in Groovy Appears to only have a Delayed Effect. As I was asked about this issue at JW, to clarify: My first comment recommends calling Label#reset() for any affected labels. In https://groups.google.com/d/msg/jenkinsci-users/-4S9VYbocyA/4qFFs45tKRcJ I posted the script to reset all labels, but it can be more targeted to one or few labels rather than resetting all. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Manish Jawarilal commented on JENKINS-34758 Re: Parameters are not passed to child jobs in multi-configuration projects Hi Team, Any update on this issue. Am stuck with the same problem. Jenkins version: Jenkins ver. 1.651.3 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35124) Allow limiting by domain without google apps
Title: Message Title Sébastien OUDRY reopened an issue Jenkins / JENKINS-35124 Allow limiting by domain without google apps Change By: Sébastien OUDRY Resolution: Fixed Status: Closed Reopened Assignee: Ryan Campbell 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35124) Allow limiting by domain without google apps
Title: Message Title Sébastien OUDRY commented on JENKINS-35124 Re: Allow limiting by domain without google apps Hi! I don't think this issue is closed as I have the same mentioned problem. The configuration field "Google Apps Domain" only accepts domains on G Suite. We can't use it with "personal" Google accounts created with corporate email address. In Grafana, allowed domains accept not only G Suite ones. The hd field used in GoogleOAuth2SecurityRealm and returned by Google OAuth token correspond actually to a G Suite Hosted Domain. So I believe, if I log in with an email address ending with "littlecompany.com" and it don't belong to a G Suite domain, the hd will be empty. Maybe the code have to check email address domain if hd is not defined. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Ruslan Zenin commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) Hi Jesse Glick . would it be possible to provide a sample pipeline script how we can accomplish "git push withCredentials or sshagent"? There is a use case for my team to build projects and change some of the artifacts and then push back to the SCM. Thank you in advance! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Nick Jones commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Mark Waite, I removed the Disable GitHub Multibranch Status configuration from this multibranch job (but left the plugin itself installed in this Jenkins system) and reran it, and still get the same @DataBoundConstructor exception in the logs. Given that, it seems conceivable that that's still the plugin at fault here, but less likely. I'm reluctant to remove the plugin entirely since we leverage it for running builds on this test Jenkins instance (without muddying the notifications in GitHub). I also note that that plugin does have the @DataBoundConstructor on its constructor, unlike the constructor for GitSCMSourceDefaults in the main Git plugin. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Gavin Williams commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults And the plugins that got updated this morning: Plugin Current Version Previous Version github 1.29.3 1.29.2 github-branch-source 2.4.1 2.3.6 htmlpublisher 1.17 1.16 mailer 1.22 1.21 scm-api 2.3.0 2.2.8 script-security 1.47 1.46 structs 1.17 1.15 workflow-aggregator
[JIRA] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Manish Jawarilal assigned an issue to Antonio Muñiz Reassigning, after it got assigned to me by mistake. Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: Manish Jawarilal Assignee: Manish Jawarilal Antonio Muñiz 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects
Title: Message Title Manish Jawarilal assigned an issue to Manish Jawarilal Jenkins / JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects Change By: Manish Jawarilal Assignee: Antonio Muñiz Manish Jawarilal 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54203) Localized Login button: wrong encoding, shows : Iniciar sesión
Title: Message Title Thomas Klambauer commented on JENKINS-54203 Re: Localized Login button: wrong encoding, shows : Iniciar sesión sorry, thanks! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22865) buildWithParameters doesn't redirect to the build page
Title: Message Title Craig Ringer edited a comment on JENKINS-22865 Re: buildWithParameters doesn't redirect to the build page This is puzzling - in `ParametersDefinitionProperty.java` I see the `buildWithParameters` method emitting a redirect to the job if `Queue.schedule2` produces an item. Which AFAICS it should unless there's one already present.https://github.com/jenkinsci/jenkins/blob/0795e89b308ec7fcbda097858d58763d8531be8c/core/src/main/java/hudson/model/ParametersDefinitionProperty.java#L179Nonetheless, it doesn't seem to, even if I pass `delay` of `0sec`. It looks like that's because the HTTP status code is SC_CREATED, which is a 200-series code, not a 300-series redirect. Sensible for an xmlhttprequest-style _javascript_ submit, not helpful for a form submit.The json-blob approach has other issues. You need to produce a suitable runId. You need to deal with the XSRF protection crumbs. It looks messy.Seems to me that /build should just accept a POST with the same format as buildWithParameters and an optional "useAsDefaults" that displays the UI and lets the user confirm. Either way, redirecting to the submitted job after. I'll see if I can hack together a patch for that but I'm still having a hard time getting my head around the inner workings of Jenkins. See also https://wiki.jenkins.io/display/JENKINS/Structured+Form+Submission for an explanation of why Jenkins does things this way, and see hudson-behaviour.js buildFormTree(). 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54204) Building / Checking evergreen modify the npm dependencies
Title: Message Title Adrien Lecharpentier created an issue Jenkins / JENKINS-54204 Building / Checking evergreen modify the npm dependencies Issue Type: Task Assignee: R. Tyler Croy Attachments: evergreen.patch Components: evergreen Created: 2018-10-23 12:15 Priority: Minor Reporter: Adrien Lecharpentier When running make check on a fresh clone of Evergreen, it is possible to see modifications on package-lock.json files. I could see that on distribution/client/package-lock.json. See the patch attached. Modifications were minor but it could lead to more issues when transitive dependencies are upgraded or such. Making sure to use the correct dependencies could prevent "invalid" development or not intended dependencies modifications in the project. Add Comment
[JIRA] (JENKINS-49588) java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)
Title: Message Title
Torsten Reinhard edited a comment on JENKINS-49588
Re: java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)
I had the same issue when loading my pipeline library, Jenkins 2.138.2. It occured after installing "custom-tool" plugin.{code:java}Loading library workflowLibs@masterAttempting to resolve master from remote references... > git --version # timeout=10using GIT_SSH to set credentials Bitbucket_Access (ssh://git@git. bmwgroup mycompany .net: 7999 port ) > git ls-remote -h ssh://git@git. bmwgroup mycompany .net: 7999 port /scopecom/workflowlibs.git # timeout=10Found match: refs/heads/master revision d61d4cd5c6b3383722cc6b47b3d1ef9571803e3fjava.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1033) at hudson.model.Fingerprint.add(Fingerprint.java:1028) at hudson.model.Fingerprint.addFor(Fingerprint.java:1021) at com.cloudbees.plugins.credentials.CredentialsProvider.trackAll(CredentialsProvider.java:1457) at com.cloudbees.plugins.credentials.CredentialsProvider.track(CredentialsProvider.java:1421) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:844) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:812) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1180) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:116) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:86) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:138) at org.jenkinsci.plugins.workflow.libs.LibraryDecorator$1.call(LibraryDecorator.java:125) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) {code}in the /fingerprints directory I found 2 files, one of them seems to be truncated (closing xml tags missing):{code:java} 2018-10-19 12:31:24.262 UTC 1f14c21f4332acaf8c1bad991f7b0f14 Credential id=Bitbucket_Access name=myuser (Bitbucket_Access (ssh://g...@git.mycompany.net:port))SeedJob-Generator-ofco-TEST4 1-3... SeedJob-Generator-dcom-aws-prod-preprod{code}
Add Comment
[JIRA] (JENKINS-49588) java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035)
Title: Message Title Torsten Reinhard commented on JENKINS-49588 Re: java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1035) I had the same issue when loading my pipeline library, Jenkins 2.138.2. It occured after installing "custom-tool" plugin. Loading library workflowLibs@master Attempting to resolve master from remote references... > git --version # timeout=10 using GIT_SSH to set credentials Bitbucket_Access (ssh://g...@git.bmwgroup.net:7999) > git ls-remote -h ssh://g...@git.bmwgroup.net:7999/scopecom/workflowlibs.git # timeout=10 Found match: refs/heads/master revision d61d4cd5c6b3383722cc6b47b3d1ef9571803e3f java.lang.NullPointerException at hudson.model.Fingerprint.addWithoutSaving(Fingerprint.java:1033) at hudson.model.Fingerprint.add(Fingerprint.java:1028) at hudson.model.Fingerprint.addFor(Fingerprint.java:1021) at com.cloudbees.plugins.credentials.CredentialsProvider.trackAll(CredentialsProvider.java:1457) at com.cloudbees.plugins.credentials.CredentialsProvider.track(CredentialsProvider.java:1421) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:844) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:812) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1180) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:116) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:86) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:138) at org.jenkinsci.plugins.workflow.libs.LibraryDecorator$1.call(LibraryDecorator.java:125) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) in the /fingerprints directory I found 2 files, one of them seems to be truncated (closing xml tags missing): '1.1' encoding='UTF-8'?> 2018-10-19 12:31:24.262 UTC 1f14c21f4332acaf8c1bad991f7b0f14 Credential id=Bitbucket_Access name=myuser (Bitbucket_Access (ssh://g...@git.mycompany.net:port)) SeedJob-Generator-ofco-TEST4 1-3 ... SeedJob-Generator-dcom-aws-prod-preprod
[JIRA] (JENKINS-54203) Localized Login button: wrong encoding, shows : Iniciar sesión
Title: Message Title Olivier Vernin moved an issue Jenkins / JENKINS-54203 Localized Login button: wrong encoding, shows : Iniciar sesión Change By: Olivier Vernin Project: Infrastructure Jenkins Key: INFRA JENKINS - 1819 54203 Workflow: classic default workflow JNJira + In-Review Component/s: core Component/s: core 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Gavin Williams commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults We've just updated one of our Jenkins installations with the latest plugins, and are now observing the same error in the logs, and the following Job failures: ERROR: [GitHub Commit Status Setter] - Cannot retrieve Git metadata for the build, setting build result to UNSTABLE A list of installed plugins is as follows: Plugins Name ↓ Version Enabled ace-editor 1.1 true ansicolor 0.5.2 true ant 1.8 true antisamy-markup-formatter 1.5 true apache-httpcomponents-client-4-api 4.5.5-3.0 true authentication-tokens 1.3 true
