[JIRA] (JENKINS-41459) Loading never finishes on blue ocean dashboard when clicked show more button.
Title: Message Title James Dumay updated JENKINS-41459 There will be a release of the p4 plugin shortly with this patch accepted Jenkins / JENKINS-41459 Loading never finishes on blue ocean dashboard when clicked show more button. Change By: James Dumay Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title john little commented on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install Thanks Brian. I found a solution in case anyone else has the problem: cd /var/lib/jenkins/plugins touch scm-sync-configuration.jpi.disabled Now I get the web UI, and can build the projects again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38860) Git plugin using local config to update submodules
Title: Message Title Pierre Larsson updated an issue Jenkins / JENKINS-38860 Git plugin using local config to update submodules Change By: Pierre Larsson Environment: Jenkins v2.6, Git plugin version 3.0.0, git-client 2. 0 2 . 0 1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38860) Git plugin using local config to update submodules
Title: Message Title Pierre Larsson reopened an issue Happening again in 2.2.1. I downgraded all the plugins and now it's working again. Try cloning g...@github.com:bbcarchdev/acropolis.git with enabled recursive in jenkins. Error message > git config --get submodule.twine-anansi-bridge/m4.url # timeout=10 FATAL: Command "git config --get submodule.twine-anansi-bridge/m4.url" returned status code 1: stdout: stderr: hudson.plugins.git.GitException: Command "git config --get submodule.twine-anansi-bridge/m4.url" returned status code 1: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1784) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1757) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1753) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1409) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1421) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getSubmoduleUrl(CliGitAPIImpl.java:1091) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1017) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to centos7_slave (i-0c8cc1000943d412e)(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537) at hudson.remoting.UserResponse.retrieve(UserRequest.java:253) at hudson.remoting.Channel.call(Channel.java:822) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at sun.reflect.GeneratedMethodAccessor151.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) at com.sun.proxy.$Proxy65.execute(Unknown Source) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:90) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1141) at hudson.scm.SCM.checkout(SCM.java:496) at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:405) Finished: FAILURE
[JIRA] (JENKINS-40606) Add ability to perform actions on branch removal
Title: Message Title Grzegorz Poznachowski edited a comment on JENKINS-40606 Re: Add ability to perform actions on branch removal I assume that would require writing a separate Jenkins plugin for that (like [here|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/listeners/ItemListener.java])? Or, could I use it in Jenkinsfile? And yes, I was asking if there is any posibility to achieve that (i.e. via script) beside coding a dedicated plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40606) Add ability to perform actions on branch removal
Title: Message Title Grzegorz Poznachowski commented on JENKINS-40606 Re: Add ability to perform actions on branch removal I assume that would require writing a separate Jenkins plugin for that (like here)? Or, could I use it in Jenkinsfile? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40907) Can't save jenkins system config
Title: Message Title Trent Dailey commented on JENKINS-40907 Re: Can't save jenkins system config After upgrading Artifactory plugin to 2.9.0 and 2.9.1 I now get the below error when testing a connection from Jenkins to artifactory. Resolving one issue caused another. javax.servlet.ServletException: java.lang.LinkageError: loader constraint violation: when resolving method "org.apache.http.impl.client.HttpClientBuilder.setDefaultCredentialsProvider(Lorg/apache/http/client/CredentialsProvider;)Lorg/apache/http/impl/client/HttpClientBuilder;" the class loader (instance of hudson/ClassicPluginStrategy$AntClassLoader2) of the current class, org/jfrog/build/client/PreemptiveHttpClient, and the class loader (instance of hudson/ClassicPluginStrategy$AntClassLoader2) for the method's defining class, org/apache/http/impl/client/HttpClientBuilder, have different Class objects for the type org/apache/http/client/CredentialsProvider used in the signature at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:236) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) 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:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:102) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) 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.ja
[JIRA] (JENKINS-39159) SecureGroovyScript.classpath does not support modifying jar while Jenkins is running
Title: Message Title Jesse Glick updated JENKINS-39159 Jenkins / JENKINS-39159 SecureGroovyScript.classpath does not support modifying jar while Jenkins is running Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41774) Pipeline executes "retry" when pipeline is aborted
Title: Message Title Joe Harte created an issue Jenkins / JENKINS-41774 Pipeline executes "retry" when pipeline is aborted Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2017/Feb/06 8:03 PM Environment: Jenkins 2.7.1 Pipeline 2.4 Labels: retry Jenkinsfile abort exception pipeline Priority: Major Reporter: Joe Harte With a "retry" block defined inside the Jenkinsfile, aborting a pipeline build does not abort the pipeline. Instead, the "retry" block will catch the abort and the Jenkinsfile still executes. Essentially, the meaning and control behind the Jenkins "abort" feature is completely lost. Add Comment
[JIRA] (JENKINS-39159) SecureGroovyScript.classpath does not support modifying jar while Jenkins is running
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-39159 SecureGroovyScript.classpath does not support modifying jar while Jenkins is running Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39159) SecureGroovyScript.classpath does not support modifying jar while Jenkins is running
Title: Message Title Jesse Glick started work on JENKINS-39159 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40521) Orphaned branch projects should not be considered buildable
Title: Message Title Jesse Glick updated JENKINS-40521 Jenkins / JENKINS-40521 Orphaned branch projects should not be considered buildable Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41773) Copy Artifact missing dependency on Run Selector
Title: Message Title Christopher Head created an issue Jenkins / JENKINS-41773 Copy Artifact missing dependency on Run Selector Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 2017/Feb/06 7:53 PM Environment: openjdk 1.8.0_121 Jenkins 2.45 Copy Artifact 1.38.1 Priority: Minor Reporter: Christopher Head Until very recently, I never had Run Selector installed, and Copy Artifact worked just fine. Today, I updated a bunch of plugins (especially the SCM API 2 stuff) and Jenkins core, and suddenly Copy Artifact failed to initalize with an NPE: java.lang.NullPointerException at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:156) at hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) at hudson.PluginManager$2$1$2.run(PluginManager.java:543) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1064) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Installing the Run Selector plugin fixed this problem. I never needed that plugin before, and Copy Artifact doesn’t have a dependency on it. There was no mention made in any release notes that I would need to add Run Selector, either.
[JIRA] (JENKINS-41772) Json syntax error when selecting Release Number
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-41772 Json syntax error when selecting Release Number Issue Type: Bug Assignee: Andrew Sumner Components: inedo-buildmaster-plugin Created: 2017/Feb/06 7:50 PM Environment: Jenkins - 2.23.1 Inedo BuildMaster plugin - 1.6 BuildMaster - 5.6.6 Priority: Major Reporter: Jon Starbird If selecting a Specific Release Number from the generated drop down of the Select Application function there is a error thrown: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected STRING but was BEGIN_OBJECT The Release Number is in the form of 1.0.0. All the drop downs are showing the proper content so the connection to BuildMaster is fine. Add Comment
[JIRA] (JENKINS-40579) Email Extension Plugin not allowing to change job configuration
Title: Message Title yashwanth kandepaneni commented on JENKINS-40579 Re: Email Extension Plugin not allowing to change job configuration So what is the solution to resolve issue. Why only if E-mail Extension plugin is configured for job its unable to save job config. For remaining jobs without these plugin everything is working fine. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Brian Wilson edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install You are experiencing the dreaded "White Screen of Death" (WSoD). Some plugins will do this to you, most won't.To answer your question, the simple way is:Go to the https:///pluginManager/.Find the scm-sync plugin.Select the button to downgrade.If you don't have that choice, go to the scm-sync web page (link provided later in this messsage).Find the archive link near top left hand side of the page.Download the 0.0.8 version of the plugin.Stop the Jenkins instance.Install the plugin file in the plugin subdirectory.Restart jenkins.If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments. Near the bottom, that brilliant, devastatingly handsome, and amazingly humble Jenkins Admin, Brian Wilson, has written some very detailed instructions that should let you get back to what you need.Hope this helpsBrian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Brian Wilson edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install You are experiencing the dreaded "White Screen of Death" (WSoD). Some plugins will do this to you, most won't.To answer your question, the simple way is:Go to the https:///pluginManager/.Find the scm-sync plugin.Select the button to downgrade.If you don't have that choice , go to the scm-sync web page (link provided later in this messsage) . find Find the archive link near top left hand side of the page. download Download the 0.0.8 version of the plugin.Stop the Jenkins instance. install Install the plugin file in the plugin subdirectory. restart Restart jenkins.If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments. Near the bottom, that brilliant, devastatingly handsome, and amazingly humble Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need.Hope this helpsBrian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40521) Orphaned branch projects should not be considered buildable
Title: Message Title Jesse Glick started work on JENKINS-40521 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Stefan Walter commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Jesse Glick, thanks for your suggestion, but everything is configured right. If I re-run the job then it works just fine. There is somehow an issue with externals. Jenkins seems to stop providing the configured credentials at some point. The issue is not the configuration, otherwise, it would always fail. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40521) Orphaned branch projects should not be considered buildable
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-40521 Orphaned branch projects should not be considered buildable Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Brian Wilson edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install You are experiencing the dreaded "White Screen of Death" (WSoD). Some plugins will do this to you, some most won't.To answer your question, the simple way is:Go to the https:///pluginManager/.Find the scm-sync plugin.Select the button to downgrade.If you don't have that choice go to the scm-sync web page.find the archive link near top left hand side of the page.download the 0.0.8 version of the plugin.Stop the Jenkins instance.install the plugin file in the plugin subdirectory.restart jenkins.If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments. Near the bottom, that brilliant, devastatingly handsome, and amazingly humble Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need.Hope this helpsBrian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Brian Wilson edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install You are experiencing the dreaded "White Screen of Death" (WSoD). Some plugins will do this to you, some won't.To answer your question, the simple way is: Go to the https:///pluginManager/.Find the scm-sync plugin.Select the button to downgrade.If you don't have that choice go to the scm-sync web page.find the archive link near top left hand side of the page.download the 0.0.8 version of the plugin.Stop the Jenkins instance.install the plugin file in the plugin subdirectory.restart jenkins.If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments. Near the bottom, that brilliant, devastatingly handsome, and amazingly humble Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need.Hope this helpsBrian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Brian Wilson edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install Go to the https:///pluginManager/.Find the scm-sync plugin.Select the button to downgrade.If you don't have that choice go to the scm-sync web page.find the archive link near top left hand side of the page.download the 0.0.8 version of the plugin.Stop the Jenkins instance.install the plugin file in the plugin subdirectory.restart jenkins.If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments. Near the bottom, that brilliant and , devastatingly handsome , and amazingly humble Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need.Hope this helpsBrian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Brian Wilson commented on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install Go to the https:///pluginManager/. Find the scm-sync plugin. Select the button to downgrade. If you don't have that choice go to the scm-sync web page. find the archive link near top left hand side of the page. download the 0.0.8 version of the plugin. Stop the Jenkins instance. install the plugin file in the plugin subdirectory. restart jenkins. If this isn't enough information, go to the https://wiki.jenkins-ci.org/display/JENKINS/SCM+Sync+configuration+plugin page and look at the comments. Near the bottom, that brilliant and devastatingly handsome Jenkins Admin, Brian Wilson, has written some detailed instructions that should let you get back to what you need. Hope this helps Brian Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41771) Post-build comment serializes concurrent builds waiting for checkpoint
Title: Message Title Matthew Bates created an issue Jenkins / JENKINS-41771 Post-build comment serializes concurrent builds waiting for checkpoint Issue Type: Bug Assignee: nathan m Components: stash-pullrequest-builder-plugin Created: 2017/Feb/06 7:21 PM Environment: Jenkins 2.19.4 and stash-pullrequest-builder 1.7.0 Labels: concurrent-build serialization stash pull_request plugin checkpoint Priority: Major Reporter: Matthew Bates At "completion" of job, when post-build steps are invoked builds can hang waiting for a checkpoint on a separate build that isn't related to the current job's build. The message that is displayed is "Stash Pull Request Builder - Post Build Comment is waiting for a checkpoint on ." It appears that there are several other plugins that have ran into this problem in the past--the fix appears to be well documented. Easy to find other reported issues by searching https://issues.jenkins-ci.org for "serialize." This ultimately ends up clogging up job queues, and artificially holding executor positions open that could have otherwise completed/released.
[JIRA] (JENKINS-40606) Add ability to perform actions on branch removal
Title: Message Title Jesse Glick commented on JENKINS-40606 Re: Add ability to perform actions on branch removal Use ItemListener.onDeleted from a plugin. I suppose you are asking for some sort of “userspace” hook, like a shell script or something, which you could configure perhaps as a JobProperty. If so, this would better be moved to plugin-proposals. Seems like a straight-up duplicate of JENKINS-37907, which seems to have been closed improperly. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35460) Multibranch Plugin: branch indexing causes java heap out of space error
Title: Message Title Jesse Glick assigned an issue to Mark Waite Jenkins / JENKINS-35460 Multibranch Plugin: branch indexing causes java heap out of space error Change By: Jesse Glick Component/s: git-plugin Component/s: workflow-multibranch-plugin Labels: multibranch Assignee: Manuel Recena Soto Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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 op
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title
Scott Epstein edited a comment on JENKINS-2111
Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace
[~jglick]Jesse, I'm new to Jenkins and this forum. I apologize for any newbie errors in advance.Am I seeing the problem that you resolved? I have directories for Multi-configuration projects sticking around after the Discard Old Builds / Max # of builds to keep (15) has been exceeded. Jobs at the bottom of the Build History (after the 15th job) disappear as new jobs complete. The directories that are kept that I'd expect to be deleted are named as follows./export/build//*sub-build*///*build*/999033/export/build//*sub-build*///*build*/999035 where CONFIGURATION=${label}_${target}_${platform}_${type}The 33 and 35 in the 999033 and 999035 at the end of the path match the Build History build numbers.Do the above directories correspond to workspaces?My Discard Old Build settings are: Strategy Log Rotation (note: this is the only option given) Days to keep builds 7 Max # of builds to keep 15I turned on some logging. Are the negative ones below a problem? Is there a way for me to determine if ANYTHING is being deleted?Feb 02, 2017 4:42:37 PM FINE hudson.tasks.LogRotatorRunning the log rotation for hudson.matrix.MatrixConfiguration@6ec64ed8[/label=e,platform=a,target=s,type=d] with numToKeep=-1 daysToKeep=-1 artifactNumToKeep=-1 artifactDaysToKeep=-1Feb 02, 2017 4:44:30 PM FINE hudson.tasks.LogRotatorRunning the log rotation for hudson.matrix.MatrixConfiguration@7b748f18[/label=e,platform=a,target=c,type=d] with numToKeep=-1 daysToKeep=-1 artifactNumToKeep=-1 artifactDaysToKeep=-1I am running 1.609. I don't see a your fix for this discarder issue listed here in the change log : https://jenkins.io/changelog/ Thank you for your help.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41769) Display "description" in build
Title: Message Title Martin Noack updated an issue Jenkins / JENKINS-41769 Display "description" in build Change By: Martin Noack In the old ui we are using the "currentBuild.description" to set version string and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41769) Display "description" in build
Title: Message Title Martin Noack created an issue Jenkins / JENKINS-41769 Display "description" in build Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/06 7:05 PM Priority: Minor Reporter: Martin Noack In the old ui we are using the "currentBuild.description" to set version and add a html link to the binary deployment. It is possible to display the description on each build also in the blue ocean ui? Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-41770) CPS serialization failure doesn't provide useful information
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-41770 CPS serialization failure doesn't provide useful information Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: workflow-cps-plugin Created: 2017/Feb/06 7:05 PM Environment: workflow-cps 2.23 Priority: Major Reporter: Andrew Bayer I'm getting a serialization error: Feb 06, 2017 5:54:40 PM org.jenkinsci.plugins.workflow.cps.CpsThreadGroup run WARNING: program state save failed java.io.IOException: Failed to persist /var/folders/pr/24nv8g910wg8vr4b4c33q34rgn/T/jenkinsTests.tmp/jenkins2922923220557378158test/jobs/test0/builds/1/program.dat at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:445) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:413) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:357) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:78) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:236) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:224) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(F
[JIRA] (JENKINS-18734) BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build
Title: Message Title Jesse Glick updated JENKINS-18734 Jenkins / JENKINS-18734 BuildStepCompatibilityLayer.perform throws UnsupportedOperation when invoked using classes that subclass Build Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41081) Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step
Title: Message Title Swathi Gangisetty updated JENKINS-41081 Bug fix and other improvements to the plugin to be released in version v1.0.5, refer to the git commit above for the changes Jenkins / JENKINS-41081 Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step Change By: Swathi Gangisetty Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this g
[JIRA] (JENKINS-41081) Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step
Title: Message Title Swathi Gangisetty updated JENKINS-41081 Jenkins / JENKINS-41081 Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step Change By: Swathi Gangisetty Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37069) Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins
Title: Message Title
Michael McCaskill edited a comment on JENKINS-37069
Re: Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins
I just did a fresh install of jenkins 2.45, installed recommended plugins, attempted to do:{noformat}node {docker.image("alecharp/maven-build-tools").inside() {sh "mvn -B clean verify"}}{noformat}and I get 3 similar errors:{noformat}[example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q] Running shell scriptsh: 1: cannot create /Users/mmccaskill/.jenkins/workspace/example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q@tmp/durable-c84ccae7/pid: Permission deniedsh: 1: cannot create /Users/mmccaskill/.jenkins/workspace/example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q@tmp/durable-c84ccae7/jenkins-log.txt: Permission deniedsh: 1: cannot create /Users/mmccaskill/.jenkins/workspace/example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q@tmp/durable-c84ccae7/jenkins-result.txt: Permission denied{noformat}Docker information:{noformat}Michaels-MacBook-Pro:~ mmccaskill $ docker versionClient: Version: 1.13.0 API version: 1.25 Go version: go1.7.4 Git commit: 49bf474 Built: OS/Arch: darwin/amd64Server: Version: 1.13.0 API version: 1.25 (minimum version 1.12) Go version: go1.7.3 Git commit: 49bf474 Built:Wed Jan 18 16:20:26 2017 OS/Arch: linux/amd64 Experimental: falseMichaels-MacBook-Pro:~ mmccaskill $ docker-machine versiondocker-machine version 0.9.0, build 15fd4c7Michaels-MacBook-Pro:~ mmccaskill $ docker-machine lsNAME ACTIVE DRIVER STATE URL SWARM DOCKERERRORSdefault -virtualbox Running tcp://192.168.99.100:2376 v1.13.0{noformat}OS information:{noformat}macOS Sierra 10.12.3 (16D32){noformat}Java information:{noformat}Michaels-MacBook-Pro:~ mmccaskill $ java -versionjava version "1.8.0_112"Java(TM) SE Runtime Environment (build 1.8.0_112-b16)Java HotSpot(TM) 64-Bit Server VM (build 25.112-b16, mixed mode){noformat} Virtualbox:{noformat}5.1.14 r112924{noformat}
Add Comment
This messa
[JIRA] (JENKINS-41081) Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step
Title: Message Title Swathi Gangisetty started work on JENKINS-41081 Change By: Swathi Gangisetty Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37069) Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins
Title: Message Title Michael McCaskill commented on JENKINS-37069 Re: Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins I downgraded to: Michaels-MacBook-Pro:~ mmccaskill $ docker version Client: Version: 1.12.1 API version: 1.24 Go version: go1.7.1 Git commit: 23cf638 Built:Sat Sep 10 02:45:38 UTC 2016 OS/Arch: darwin/amd64 Server: Version: 1.12.1 API version: 1.24 Go version: go1.6.3 Git commit: 23cf638 Built:Thu Aug 18 17:52:38 2016 OS/Arch: linux/amd64 Michaels-MacBook-Pro:~ mmccaskill $ docker-machine version docker-machine version 0.8.2, build e18a919 Michaels-MacBook-Pro:~ mmccaskill $ docker-machine ls NAME ACTIVE DRIVER STATE URL SWARM DOCKERERRORS default *virtualbox Running tcp://192.168.99.100:2376 v1.12.1 and still same errors Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41757) BUILD_NOW_TEXT is not being applied when the job is parameterized
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41757 BUILD_NOW_TEXT is not being applied when the job is parameterized Change By: Jesse Glick Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41757) BUILD_NOW_TEXT is not being applied when the job is parameterized
Title: Message Title Jesse Glick updated JENKINS-41757 Jenkins / JENKINS-41757 BUILD_NOW_TEXT is not being applied when the job is parameterized Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41757) BUILD_NOW_TEXT is not being applied when the job is parameterized
Title: Message Title Jesse Glick assigned an issue to Alvaro Lobato Jenkins / JENKINS-41757 BUILD_NOW_TEXT is not being applied when the job is parameterized Change By: Jesse Glick Assignee: Alvaro Lobato Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32167) ISVNAuthentication provider did not provide credentials
Title: Message Title Jesse Glick commented on JENKINS-32167 Re: ISVNAuthentication provider did not provide credentials Stefan Walter The issue still persists even with snapshot 2.7.2. Of course, the PR only provides logging to make it clearer what is wrong, whether with your configuration or something else. Using sole credentials in realm ‘ Your AD Username/Password for SVN’ suggests that you have not configured any credentials, “additional” or primary. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title Petr H updated an issue Jenkins / JENKINS-41767 Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method Change By: Petr H Environment: CentOS 7.3, JDK 8u112, Jenkins 2.32. 2 1 , NodeJS Plugin 1.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title Petr H created an issue Jenkins / JENKINS-41767 Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method Issue Type: Bug Assignee: Unassigned Components: nodejs-plugin Created: 2017/Feb/06 6:18 PM Environment: CentOS 7.3, JDK 8u112, Jenkins 2.32.2, NodeJS Plugin 1.0 Labels: nodejs illegalstateexception getdescriptor Priority: Minor Reporter: Petr H After trying the NodeJS Plugin upgrade to version 1.0 (which we had to roll back due to JENKINS-41535) we could see the following exceptions when attempting to load the Job configuration page for jobs utilizing this plugin: Jan 31, 2017 8:18:48 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: descriptor.configs in .../configure. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(U
[JIRA] (JENKINS-41768) testlink status not run with TAP
Title: Message Title
Mark Crusher updated an issue
Jenkins / JENKINS-41768
testlink status not run with TAP
Change By:
Mark Crusher
when trying to execute test case job in jenkins Jenkins using TAP I will always see testlink Testlink result as 'Not run' but build number variable is sent to testlink to create a new build there, so they know about each other and comunicate communicate on every buildperhaps my implementation of TAP file format/name is wrong?file name: gui_argumentscontent:{{1..2not ok 1 - gui_argumentsnot ok 2 - gui_arguments}}then the result shows this{{Executing iterative Build Steps.Looking for the test results of TestLink test cases.Found 1 test result(s).Archiving artifactsFinished: SUCCESS}}any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this gro
[JIRA] (JENKINS-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title
Petr H updated an issue
Jenkins / JENKINS-41767
Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Change By:
Petr H
After trying the NodeJS Plugin upgrade to version 1.0 (which we had to roll back due to JENKINS-41535) we could see the following exceptions (in jenkins log) when attempting to load the Job configuration page for jobs utilizing this plugin:{noformat}Jan 31, 2017 8:18:48 AM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: descriptor.configs in .../configure. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)at org.apache.commons.jell
[JIRA] (JENKINS-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title
Petr H updated an issue
Jenkins / JENKINS-41767
Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Change By:
Petr H
After trying the NodeJS Plugin upgrade to version 1.0 (which we had to roll back due to JENKINS-41535) we could see the following exceptions (in jenkins log) when attempting to load the Job configuration page for jobs utilizing this plugin:{noformat}Jan 31, 2017 8:18:48 AM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: descriptor.configs in .../configure. Reason: java.lang.reflect.InvocationTargetExceptionjava.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)at org.apache.commons.je
[JIRA] (JENKINS-41768) testlink status not run with TAP
Title: Message Title
Mark Crusher created an issue
Jenkins / JENKINS-41768
testlink status not run with TAP
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Components:
testlink-plugin
Created:
2017/Feb/06 6:21 PM
Environment:
Jenkins ver. 2.32.2 TestLink Plugin ver. 3.11 TestLink ver. 1.9.16[DEV]
Labels:
tapResults
Priority:
Major
Reporter:
Mark Crusher
when trying to execute test case job in jenkins using TAP I will always see testlink result as 'Not run' but build number variable is sent to testlink to create a new build there, so they know about each other and comunicate on every build perhaps my implementation of TAP file format/name is wrong? file name: gui_arguments content: {{1..2 not ok 1 - gui_arguments not ok 2 - gui_arguments}} then the result shows this {{Executing iterative Build Steps. Looking for the test results of TestLink test cases. Found 1 test result(s). Archiving artifacts Finished: SUCCESS}} any ideas? I spent few days and 32 runs of the job to get here and running out of ideas.
[JIRA] (JENKINS-37069) Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins
Title: Message Title
Michael McCaskill edited a comment on JENKINS-37069
Re: Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins
I just did a fresh install of jenkins 2.45, installed recommended plugins, attempted to do:{noformat}node {docker.image("alecharp/maven-build-tools").inside() {sh "mvn -B clean verify"}}{noformat}and I get 3 similar errors:{noformat}[example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q] Running shell scriptsh: 1: cannot create /Users/mmccaskill/.jenkins/workspace/example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q@tmp/durable-c84ccae7/pid: Permission deniedsh: 1: cannot create /Users/mmccaskill/.jenkins/workspace/example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q@tmp/durable-c84ccae7/jenkins-log.txt: Permission deniedsh: 1: cannot create /Users/mmccaskill/.jenkins/workspace/example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q@tmp/durable-c84ccae7/jenkins-result.txt: Permission denied{noformat} Docker information:{noformat}Michaels-MacBook-Pro:~ mmccaskill $ docker versionClient: Version: 1.13.0 API version: 1.25 Go version: go1.7.4 Git commit: 49bf474 Built: OS/Arch: darwin/amd64Server: Version: 1.13.0 API version: 1.25 (minimum version 1.12) Go version: go1.7.3 Git commit: 49bf474 Built:Wed Jan 18 16:20:26 2017 OS/Arch: linux/amd64 Experimental: falseMichaels-MacBook-Pro:~ mmccaskill $ docker-machine versiondocker-machine version 0.9.0, build 15fd4c7Michaels-MacBook-Pro:~ mmccaskill $ docker-machine lsNAME ACTIVE DRIVER STATE URL SWARM DOCKERERRORSdefault -virtualbox Running tcp://192.168.99.100:2376 v1.13.0{noformat}OS information:{noformat}macOS Sierra 10.12.3 (16D32){noformat}Java information:{noformat}Michaels-MacBook-Pro:~ mmccaskill $ java -versionjava version "1.8.0_112"Java(TM) SE Runtime Environment (build 1.8.0_112-b16)Java HotSpot(TM) 64-Bit Server VM (build 25.112-b16, mixed mode){noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-s
[JIRA] (JENKINS-37069) Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins
Title: Message Title
Michael McCaskill commented on JENKINS-37069
Re: Permission denied on durable task directory when using docker.image.inside step on fresh install of jenkins
I just did a fresh install of jenkins 2.45, installed recommended plugins, attempted to do:
node {
docker.image("alecharp/maven-build-tools").inside() {
sh "mvn -B clean verify"
}
}
and I get 3 similar errors:
[example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q] Running shell script
sh: 1: cannot create /Users/mmccaskill/.jenkins/workspace/example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q@tmp/durable-c84ccae7/pid: Permission denied
sh: 1: cannot create /Users/mmccaskill/.jenkins/workspace/example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q@tmp/durable-c84ccae7/jenkins-log.txt: Permission denied
sh: 1: cannot create /Users/mmccaskill/.jenkins/workspace/example_poc_master-GGCVXMNZOUBSWREPVP27YOR3DZTHKBWNU2ISCLF5PYNDINJX5K6Q@tmp/durable-c84ccae7/jenkins-result.txt: Permission denied
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Kevin Yu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items Daniel Beck it doesn't explain why it's taking longer time to open "Project-A" cloudbees folder (contains 6 items) than "Projects" folder (contains 34 items). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41121) GitHub Branch Source upgrade can cause a lot of rebuilds
Title: Message Title Morgan Goose commented on JENKINS-41121 Re: GitHub Branch Source upgrade can cause a lot of rebuilds Stephen Connolly I'd like to clarify, that I only installed those two plugins manually after multiple plugins failed to load saying that these versions were required. All of those complaining plugins were shown as having updates available and were updated in the suggested way (via the plugin update center web UI). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41766) expose environment variable to indicate release
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-41766 expose environment variable to indicate release Issue Type: Bug Assignee: Stanley Hillner Components: unleash-plugin Created: 2017/Feb/06 6:01 PM Priority: Minor Reporter: Jae Gangemi it would be great if the plugin could expose an environment variable, similar to the m2-plugin, to indicate a release is being performed. using IS_M2RELEASEBUILD as would be a good choice as it is default used by the m2-plugin and would allow users to switch between the two in jenkins w/o the need to make pom and/or configuration changes. Add Comment
[JIRA] (JENKINS-41334) Support parallel execution of stages in Declarative
Title: Message Title
Yannick Koehler edited a comment on JENKINS-41334
Re: Support parallel execution of stages in Declarative
I am interested in a scenario that looks like this:{noformat} stages {stage('extract') {}stage('build') { parallel {stage('build product A') { stage('build module set 1') { } stage('build module set 2') { }}stage('build product B') {} }}stage('finalize') {} }{noformat}The outcome order would be that build only occurs after extract, that finalize only occurs after all build sub-stage are completed. That build product A and build procduct B are done in parallel. That build module set 2 only occurs after build module set 1 has completed (since it has some dependencies).Now, I feel that using "stages" inside a "stage" or a "stages" tag make no sense. Also, indenting those "stage" looks messy.A suggestion would be to do this operation like Make does, by stating the stages first, then adjusting the dependencies later, i.e.: {noformat} stages {stage('extract') { }stage('build product A') { } stage('build module set 1') { } stage('build module set 2') { } stage('build product B') { } stage('finalize') { } } {noformat} This would be default create a set of dependencies such as {noformat} : 'build product A': 'extract' 'build module set 1': 'build product A' 'build module set 2': 'build module set 1' 'build product B': 'build module set 2' 'finalize': 'build product B' {noformat} Same as today, the author can then change those dependencies from the default to what he wants: {noformat} stages {stage('extract') { }stage('build product A') { } stage('build module set 1') { } stage('build module set 2') { } stage('build product B') { dependencies: [ 'extract' ]} stage('finalize') { dependencies: ['build product A', 'build product B']} } {noformat} This effectively transforming the dependency table to {noformat} : 'build product A': 'extract' 'build module set 1': 'build product A' 'build module set 2': 'build module set 1' 'build product B': 'extract' 'finalize': 'build product A', 'build product B' {noformat} Using this set of dependency, the parallelism used is imply in the dependency, as soon as a target dependency are met, the associated stage can start.This is backward compatible, get rid of the "parallel" declarative statement and add a minimum set of keywords "dependencies" to the current DSL.Anyway, just a need of mine and an opinion to share on how to do it.
Add Comment
[JIRA] (JENKINS-41334) Support parallel execution of stages in Declarative
Title: Message Title
Yannick Koehler edited a comment on JENKINS-41334
Re: Support parallel execution of stages in Declarative
I am interested in a scenario that looks like this: {{ stages {stage('extract') {}stage('build') { parallel {stage('build product A') { stage('build module set 1') { } stage('build module set 2') { }}stage('build product B') {} }}stage('finalize') {} } }} The outcome order would be that build only occurs after extract, that finalize only occurs after all build sub-stage are completed. That build product A and build procduct B are done in parallel. That build module set 2 only occurs after build module set 1 has completed (since it has some dependencies).Now, I feel that using "stages" inside a "stage" or a "stages" tag make no sense. Also, indenting those "stage" looks messy.A suggestion would be to do this operation like Make does, by stating the stages first, then adjusting the dependencies later, i.e.: stages {stage('extract') { }stage('build product A') { } stage('build module set 1') { } stage('build module set 2') { } stage('build product B') { } stage('finalize') { } }This would be default create a set of dependencies such as : 'build product A': 'extract' 'build module set 1': 'build product A' 'build module set 2': 'build module set 1' 'build product B': 'build module set 2' 'finalize': 'build product B'Same as today, the author can then change those dependencies from the default to what he wants: stages {stage('extract') { }stage('build product A') { } stage('build module set 1') { } stage('build module set 2') { } stage('build product B') { dependencies: [ 'extract' ]} stage('finalize') { dependencies: ['build product A', 'build product B']} }This effectively transforming the dependency table to : 'build product A': 'extract' 'build module set 1': 'build product A' 'build module set 2': 'build module set 1' 'build product B': 'extract' 'finalize': 'build product A', 'build product B'Using this set of dependency, the parallelism used is imply in the dependency, as soon as a target dependency are met, the associated stage can start.This is backward compatible, get rid of the "parallel" declarative statement and add a minimum set of keywords "dependencies" to the current DSL.Anyway, just a need of mine and an opinion to share on how to do it.
Add Comment
[JIRA] (JENKINS-41334) Support parallel execution of stages in Declarative
Title: Message Title
Yannick Koehler edited a comment on JENKINS-41334
Re: Support parallel execution of stages in Declarative
I am interested in a scenario that looks like this:{ { noformat} stages {stage('extract') {}stage('build') { parallel {stage('build product A') { stage('build module set 1') { } stage('build module set 2') { }}stage('build product B') {} }}stage('finalize') {} } {noformat } } The outcome order would be that build only occurs after extract, that finalize only occurs after all build sub-stage are completed. That build product A and build procduct B are done in parallel. That build module set 2 only occurs after build module set 1 has completed (since it has some dependencies).Now, I feel that using "stages" inside a "stage" or a "stages" tag make no sense. Also, indenting those "stage" looks messy.A suggestion would be to do this operation like Make does, by stating the stages first, then adjusting the dependencies later, i.e.: stages {stage('extract') { }stage('build product A') { } stage('build module set 1') { } stage('build module set 2') { } stage('build product B') { } stage('finalize') { } }This would be default create a set of dependencies such as : 'build product A': 'extract' 'build module set 1': 'build product A' 'build module set 2': 'build module set 1' 'build product B': 'build module set 2' 'finalize': 'build product B'Same as today, the author can then change those dependencies from the default to what he wants: stages {stage('extract') { }stage('build product A') { } stage('build module set 1') { } stage('build module set 2') { } stage('build product B') { dependencies: [ 'extract' ]} stage('finalize') { dependencies: ['build product A', 'build product B']} }This effectively transforming the dependency table to : 'build product A': 'extract' 'build module set 1': 'build product A' 'build module set 2': 'build module set 1' 'build product B': 'extract' 'finalize': 'build product A', 'build product B'Using this set of dependency, the parallelism used is imply in the dependency, as soon as a target dependency are met, the associated stage can start.This is backward compatible, get rid of the "parallel" declarative statement and add a minimum set of keywords "dependencies" to the current DSL.Anyway, just a need of mine and an opinion to share on how to do it.
Add Comment
[JIRA] (JENKINS-41334) Support parallel execution of stages in Declarative
Title: Message Title
Yannick Koehler commented on JENKINS-41334
Re: Support parallel execution of stages in Declarative
I am interested in a scenario that looks like this: stages { stage('extract') { } stage('build') { parallel { stage('build product A') { stage('build module set 1') { } stage('build module set 2') { } } stage('build product B') { } } } stage('finalize') { } } The outcome order would be that build only occurs after extract, that finalize only occurs after all build sub-stage are completed. That build product A and build procduct B are done in parallel. That build module set 2 only occurs after build module set 1 has completed (since it has some dependencies). Now, I feel that using "stages" inside a "stage" or a "stages" tag make no sense. Also, indenting those "stage" looks messy. A suggestion would be to do this operation like Make does, by stating the stages first, then adjusting the dependencies later, i.e.: stages { stage('extract') { } stage('build product A') { } stage('build module set 1') { } stage('build module set 2') { } stage('build product B') { } stage('finalize') { } } This would be default create a set of dependencies such as : 'build product A': 'extract' 'build module set 1': 'build product A' 'build module set 2': 'build module set 1' 'build product B': 'build module set 2' 'finalize': 'build product B' Same as today, the author can then change those dependencies from the default to what he wants: stages { stage('extract') { } stage('build product A') { } stage('build module set 1') { } stage('build module set 2') { } stage('build product B') { dependencies: [ 'extract' ] } stage('finalize') { dependencies: ['build product A', 'build product B'] } } This effectively transforming the dependency table to : 'build product A': 'extract' 'build module set 1': 'build product A' 'build module set 2': 'build module set 1' 'build product B': 'extract' 'finalize': 'build product A', 'build product B' Using this set of dependency, the parallelism used is imply in the dependency, as soon as a target dependency are met, the associated stage can start. This is backward compatible, get rid of the "parallel" declarative statement and add a minimum set of keywords "dependencies" to the current DSL. Anyway, just a need of mine and an opinion to share on how to do it.
Add Comment
[JIRA] (JENKINS-40903) Server Name Indication is not supported
Title: Message Title
Jakub Bochenski updated an issue
Jenkins / JENKINS-40903
Server Name Indication is not supported
Change By:
Jakub Bochenski
When I try to build {{config-file-provider-plugin -maven }} with a Nexus server set as proxy it fails with:{code}12:37:13 Failed to transfer Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com]12:37:13 Deleting 1 temporary files12:37:13 ERROR: Failed to parse POMs12:37:13 java.io.IOException: remote file operation failed: /home/acme/workspace/config-file-provider-plugin-maven at hudson.remoting.Channel@74a1dda5:IQ-61a8ac47b316: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 1312:37:13 12:37:13 at hudson.FilePath.act(FilePath.java:992)12:37:13 at hudson.FilePath.act(FilePath.java:974)12:37:13 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:980)12:37:13 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:692)12:37:13 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)12:37:13 at hudson.model.Run.execute(Run.java:1728)12:37:13 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:544)12:37:13 at hudson.model.ResourceController.execute(ResourceController.java:98)12:37:13 at hudson.model.Executor.run(Executor.java:404)12:37:13 Caused by: hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:12:37:13 [FATAL] Non-resolvable parent POM: Could not transfer artifact org.jenkins-ci.plugins:plugin:pom:2.17 from/to internal-repo (https://readonly-mvnrepo.acme-internal.com/content/groups/public/): Certificate for doesn't match any of the subject alternative names: [*.acme-it.com, acme-it.com, mvnrepo.acme-it.com] and 'parent.relativePath' points at wrong local POM @ line 5, column 1312:37:13 12:37:13 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1384)12:37:13 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1118)12:37:13 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731)12:37:13 at hudson.remoting.UserRequest.perform(UserRequest.java:153)12:37:13 at hu
[JIRA] (JENKINS-40057) Stage view is completely missing for long durations after restarts
Title: Message Title
Joachim Herb edited a comment on JENKINS-40057
Re: Stage view is completely missing for long durations after restarts
I see exactly the same behavior. Jenkins: 2.44stage view plugin: 2.4Windows 7Perhaps interesting information: I changed {code}-Dcom.cloudbees.workflow.rest.external.JobExt.maxRunsPerJob=50{code}in jenkins.xml. After that the stage view was empty all the time.Then I changed it to{code}-Dcom.cloudbees.workflow.rest.external.JobExt.maxRunsPerJob=5{code}and restarted Jenkins.Until and including the completion of the 5th build of the pipeline job, the stage view did not show up. But after I started the sixth build, it worked again and also showed the first 5 builds. For whatever reasons, on Linux it seems to work (even with 50 builds to be shown in the stage view).
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-40057) Stage view is completely missing for long durations after restarts
Title: Message Title Joachim Herb commented on JENKINS-40057 Re: Stage view is completely missing for long durations after restarts I see exactly the same behavior. Jenkins: 2.44 stage view plugin: 2.4 Windows 7 Perhaps interesting information: I changed -Dcom.cloudbees.workflow.rest.external.JobExt.maxRunsPerJob=50 in jenkins.xml. After that the stage view was empty all the time. Then I changed it to -Dcom.cloudbees.workflow.rest.external.JobExt.maxRunsPerJob=5 and restarted Jenkins. Until and including the completion of the 5th build of the pipeline job, the stage view did not show up. But after I started the sixth build, it worked again and also showed the first 5 builds. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34545) Assigning roles is case sensitive, and it shouldn't be
Title: Message Title David Wise edited a comment on JENKINS-34545 Re: Assigning roles is case sensitive, and it shouldn't be I have the same issue. My Jenkins instance uses Security Realm of Active Directory, and Authorization of Role-Based Strategy. If the user does not use the same user ID case I use in Role Strategy, then they get the _missing "missing the Overall/Read permission _error " error . As Active Directory does not care about case, my *workaround * WORKAROUND is to enter 2 global and project entries for the user. One uppercase, DW12345, and one lowercase, dw12345. I could tell the user to use only lowercase, but then I would just get hassled by users who don't remember, or want an excuse to debate why we are moving to Jenkins. Love the plugin, as it works perfectly to control job visibility and read/write permissions. But the case sensitivity is an unnecessary pain. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34545) Assigning roles is case sensitive, and it shouldn't be
Title: Message Title David Wise commented on JENKINS-34545 Re: Assigning roles is case sensitive, and it shouldn't be I have the same issue. My Jenkins instance uses Security Realm of Active Directory, and Authorization of Role-Based Strategy. If the user does not use the same user ID case I use in Role Strategy, then they get the _missing the Overall/Read permission _error. As Active Directory does not care about case, my *workaround *is to enter 2 global and project entries for the user. One uppercase, DW12345, and one lowercase, dw12345. I could tell the user to use only lowercase, but then I would just get hassled by users who don't remember, or want an excuse to debate why we are moving to Jenkins. Love the plugin, as it works perfectly to control job visibility and read/write permissions. But the case sensitivity is an unnecessary pain. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40929) Developer can see durations when hovering on indicators
Title: Message Title Thorsten Scherler updated JENKINS-40929 Jenkins / JENKINS-40929 Developer can see durations when hovering on indicators Change By: Thorsten Scherler Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40117) Type java.lang$Enum not present when updating 2.6 to 2.7
Title: Message Title Jesse Glick commented on JENKINS-40117 Re: Type java.lang$Enum not present when updating 2.6 to 2.7 I do not see anything in the upgrade diff that seems at all suspicious. Anyone know how to reproduce this from scratch? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41586) Acceptance tests for Pipeline Editor
Title: Message Title Keith Zantow started work on JENKINS-41586 Change By: Keith Zantow Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41755) Background 'sh' invocation
Title: Message Title Jesse Glick started work on JENKINS-41755 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title john little edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install I just upgraded to 0.0.9 and now jenkins UI is giving blank pages also. In the logs it says INFO: Jenkins is fully up and runningBut it is not.Earlier in the log file is one error:Feb 06, 2017 6:08:26 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed Loading plugin SCM Sync Configuration Plugin v0.0.9 (scm-sync-configuration)java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:521) * Please, could someone tell us how to manually downgrade the scm-sync-configuration plugin to 0.0.8? * Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41755) Background 'sh' invocation
Title: Message Title Jesse Glick updated JENKINS-41755 Jenkins / JENKINS-41755 Background 'sh' invocation Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41755) Background 'sh' invocation
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41755 Background 'sh' invocation Change By: Jesse Glick Issue Type: Improvement New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title john little commented on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install I just upgraded to 0.0.9 and now jenkins UI is giving blank pages also. In the logs it says INFO: Jenkins is fully up and running But it is not. Earlier in the log file is one error: Feb 06, 2017 6:08:26 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin SCM Sync Configuration Plugin v0.0.9 (scm-sync-configuration) java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:521) Please, could someone tell us how to manually downgrade the scm-sync-configuration plugin to 0.0.8? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41276) Abort doesn't work with Retry
Title: Message Title Jesse Glick updated JENKINS-41276 Jenkins / JENKINS-41276 Abort doesn't work with Retry Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41754) thinBackup run custom script after backup
Title: Message Title Thomas Fürer commented on JENKINS-41754 Re: thinBackup run custom script after backup thank you for your ideas. I started a new version branch (2.0) some time ago, which will cover exactly your requests in a way that the different action can be implemented in where or how the backup is stored. Unfortently I'm limited in time so the progress is very bad... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41759) Add posibilities to read environment from trusted properties file
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41759 Re: Add posibilities to read environment from trusted properties file Code changed in jenkins User: rsandell Path: pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Root.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/DeclarativeEnvironmentContributor.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/DeclarativeEnvironmentContributorDescriptor.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/DeclarativeEnvironmentContributorScript.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/environment/impl/Credentials.java pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/steps/CredentialWrapper.java pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/PropertiesToMapTranslator.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/environment/impl/CredentialsScript.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/5d2bc33a68b2e2834d2fc0825cbde7792587a8ce Log: JENKINS-41759 First make the function calls in environment extensible Work in Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41535) NodeJS installation configuration is not persisted to file
Title: Message Title Robert Gornall commented on JENKINS-41535 Re: NodeJS installation configuration is not persisted to file Thanks, seems to be writing the file to disk properly now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41765) groovy CLI command cannot be used with stdin via SSH
Title: Message Title Daniel Beck started work on JENKINS-41765 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41765) groovy CLI command cannot be used with stdin via SSH
Title: Message Title Daniel Beck updated JENKINS-41765 Jenkins / JENKINS-41765 groovy CLI command cannot be used with stdin via SSH Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41765) groovy CLI command cannot be used with stdin via SSH
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-41765 groovy CLI command cannot be used with stdin via SSH Issue Type: Bug Assignee: Daniel Beck Components: cli, core Created: 2017/Feb/06 4:12 PM Priority: Minor Reporter: Daniel Beck There's no reason this shouldn't be possible. Let's allow groovy command use via SSH CLI. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41765) groovy CLI command cannot be used with stdin via SSH
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-41765 groovy CLI command cannot be used with stdin via SSH Change By: Daniel Beck Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41546) Clearer plain text validation messages
Title: Message Title Keith Zantow updated JENKINS-41546 Jenkins / JENKINS-41546 Clearer plain text validation messages Change By: Keith Zantow Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40978) Preview release of editor
Title: Message Title Keith Zantow resolved as Done Jenkins / JENKINS-40978 Preview release of editor Change By: Keith Zantow Status: In Progress Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41276) Abort doesn't work with Retry
Title: Message Title Jesse Glick updated JENKINS-41276 Jenkins / JENKINS-41276 Abort doesn't work with Retry Change By: Jesse Glick Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41276) Abort doesn't work with Retry
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-41276 Abort doesn't work with Retry Change By: Jesse Glick Assignee: rsandell Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41764) Perforce triggered build should not trigger polling on jobs unless there are changes related to that view
Title: Message Title Robby Pocase edited a comment on JENKINS-41764 Re: Perforce triggered build should not trigger polling on jobs unless there are changes related to that view Additionally, it should verify the change is actually associated with the right port. Looks like this work may require significant overhaul of the current probeJobs implementation. The webhook would need to pass in more complete information for better decision making. That overhaul is very likely possibly out of scope of these improvement request. You might be able to accomplish that portion naively in the same request. If you retrieve the change in probeJobs using port and change you likely have a very high success ratio of matching the change to the server. If change is null, it's obviously a mismatch. If change isn't, then your depot path still has to match the jobs workspace view. I would be surprised if many Perforce deployments have large amounts of duplicated full depot paths on multiple servers. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41659) Stabilise ATH
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-41659 Stabilise ATH Change By: Tom FENNELLY Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41638) "Open Blue Ocean" button doesn't work unless the server URL is set correctly
Title: Message Title Tom FENNELLY started work on JENKINS-41638 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41764) Perforce triggered build should not trigger polling on jobs unless there are changes related to that view
Title: Message Title Robby Pocase commented on JENKINS-41764 Re: Perforce triggered build should not trigger polling on jobs unless there are changes related to that view Additionally, it should verify the change is actually associated with the right port. Looks like this work may require significant overhaul of the current probeJobs implementation. The webhook would need to pass in more complete information for better decision making. That overhaul is very likely out of scope of these improvement request. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41276) Abort doesn't work with Retry
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41276 Abort doesn't work with Retry Change By: Jesse Glick Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (TEST-93) testing123
Title: Message Title James Brown closed an issue as Done Test JIRA being closed. test / TEST-93 testing123 Change By: James Brown Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41764) Perforce triggered build should not trigger polling on jobs unless there are changes related to that view
Title: Message Title Robby Pocase created an issue Jenkins / JENKINS-41764 Perforce triggered build should not trigger polling on jobs unless there are changes related to that view Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2017/Feb/06 3:35 PM Priority: Major Reporter: Robby Pocase The current implementation triggers polling on all jobs with Perforce Triggered Build enabled. This is fine for small installations with few check ins per day, but not for installations with hundreds of jobs. This can cause massive spikes in size increases for Perforce server logs. For example, if I check in a file to "//my_depot/..." I should trigger polling on a job with view: //my_depot/... //workspace_name/... However, I should not trigger polling on a job with view: //my_depot2/... //workspace_name/...
[JIRA] (JENKINS-39598) Project configuration - NullPointerException
Title: Message Title
Test User updated an issue
Jenkins / JENKINS-39598
Project configuration - NullPointerException
Change By:
Test User
NullPointerException after opening project configuration.Error message:{code} Nov 08 Feb 06 , 2016 9 2017 4 : 29 21 : 12 49 PM FINER hudson.model.DescriptorVisibilityFilterQuerying org.jenkinsci.plugins.workflow.multibranch.SCMBinder$HideMeElsewhere@5eea20fd for visibility of com.cloudbees.plugins.credentials.impl.CertificateCredentialsImpl$DescriptorImpl@1a9cf2bb in com.cloudbees.plugins.credentials.SystemCredentialsProvider$StoreImpl@54d8ab1eFeb 06, 2017 4:21:49 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluateCaught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /job/test- project pipeline /configure. Reason: java.lang.NullPointerExceptionjava.lang.NullPointerException at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:72) at hudson.Functions.filterDescriptors(Functions.java: 1790 1863 ) at sun.reflect. GeneratedMethodAccessor397 GeneratedMethodAccessor1290 .invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly
[JIRA] (JENKINS-39598) Project configuration - NullPointerException
Title: Message Title Test User updated an issue Jenkins / JENKINS-39598 Project configuration - NullPointerException Change By: Test User Environment: Jenkins 2. 30 44 , Bitbucket Branch Source Plugin 1 Pipeline: Multibranch 2 . 8 9.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40879) Locked areas are executed multiple times in parallel
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40879 Locked areas are executed multiple times in parallel Change By: Jesse Glick Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39598) Project configuration - NullPointerException
Title: Message Title Test User assigned an issue to Unassigned Jenkins / JENKINS-39598 Project configuration - NullPointerException Change By: Test User Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39598) Project configuration - NullPointerException
Title: Message Title Test User updated an issue Jenkins / JENKINS-39598 Project configuration - NullPointerException Change By: Test User Component/s: workflow-multibranch-plugin Component/s: bitbucket-branch-source-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41763) Show a column with the Java version of an agent
Title: Message Title Christoph Obexer commented on JENKINS-41763 Re: Show a column with the Java version of an agent Baptiste Mathus Is something like this planned for the Jenkins Core? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41763) Show a column with the Java version of an agent
Title: Message Title Christoph Obexer updated an issue Jenkins / JENKINS-41763 Show a column with the Java version of an agent Change By: Christoph Obexer Summary: Show a column with the Java version of a node an agent Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41763) Show a column with the Java version of a node
Title: Message Title Christoph Obexer created an issue Jenkins / JENKINS-41763 Show a column with the Java version of a node Issue Type: New Feature Assignee: sogabe Components: versioncolumn-plugin Created: 2017/Feb/06 3:05 PM Environment: Jenkins 2.44 Priority: Major Reporter: Christoph Obexer Considering that Jenkins will soon require Java 8 and that using different Java versions is considered bad it would be very helpful if this plugin also showed the JRE/JDK version used to run the agent. Setting Agents to offline may also be a useful feature. Java 8: https://jenkins.io/blog/2017/01/17/Jenkins-is-upgrading-to-Java-8/ Add Comment
[JIRA] (JENKINS-41762) NodeJS plugin not updating PATH as expected
Title: Message Title Stefan Goor updated an issue Jenkins / JENKINS-41762 NodeJS plugin not updating PATH as expected Change By: Stefan Goor Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40874) Missing ErrorAction after Jenkins restart
Title: Message Title Sam Van Oort commented on JENKINS-40874 Re: Missing ErrorAction after Jenkins restart Yes, recampbell possibly a Bismuth bug of some flavor – or something in the internals. Either way I can investigate. Not today probably, but soon. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40874) Missing ErrorAction after Jenkins restart
Title: Message Title recampbell commented on JENKINS-40874 Re: Missing ErrorAction after Jenkins restart Sam Van Oort, this looks like a bug in Bismuth, no? If so, something for a followup with the other issues in this area after your current work. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41693) Stuck socket communication can block aync disposer
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41693 Re: Stuck socket communication can block aync disposer Code changed in jenkins User: Ing. Pavel Janousek Path: src/main/java/com/redhat/foreman/ForemanAPI.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/610efd64c72b941251012dad57f664af376fe06a Log: JENKINS-41693 Added timeouts to web client connection Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
