[JIRA] (JENKINS-41792) NeoLoad plugin attempts to parse archived XML files
Title: Message Title Tuukka Mustonen created an issue Jenkins / JENKINS-41792 NeoLoad plugin attempts to parse archived XML files Issue Type: Bug Assignee: Unassigned Components: neoload-jenkins Created: 2017/Feb/07 7:58 AM Environment: Jenkins 2.7.4 Neoload plugin 2.0.1 Priority: Minor Reporter: Tuukka Mustonen I am not sure when exactly this happens, but my jenkins.log gets pretty much flooded by something like this: [Fatal Error] dashBoard_*.xml:9:12: Attribute name "_ping" associated with an element type "GET" must be followed by the ' = ' character. Feb 07, 2017 7:55:15 AM com.neotys.nl.controller.report.transform.NeoLoadReportDoc WARNING: Error reading xml file. Attribute name "_ping" associated with an element type "GET" must be followed by the ' = ' character. org.xml.sax.SAXParseException; systemId: file:///var/lib/jenkins/jobs/COSMOS-CI-PERF-ew1-perftest-ping/builds/5/archive/dashBoard_*.xml; lineNumber: 9; columnNumber: 12; Attribute name "_ping" associated with an element type "GET" must be followed by the ' = ' character. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:339) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:177) at org.jenkinsci.plugins.neoload.integration.supporting.XMLUtilities.readXmlFile(XMLUtilities.java:226) at com.neotys.nl.controller.report.transform.NeoLoadReportDoc.(NeoLoadReportDoc.java:102) at org.jenkinsci.plugins.neoload.integration.ProjectSpecificAction.
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items Also i forgot to mention for all of cloudbees folders, I have removed health metrics so the view (page) doesn't require any info from the underlying 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-27244) Performance plugin archives dashBoard_*.xml
Title: Message Title Tuukka Mustonen commented on JENKINS-27244 Re: Performance plugin archives dashBoard_*.xml Is there a workaround to avoid this? On my Jenkins, I get lots of these in jenkins.log: Feb 07, 2017 7:55:15 AM com.neotys.nl.controller.report.transform.NeoLoadReportDoc WARNING: Error reading xml file. Attribute name "_ping" associated with an element type "GET" must be followed by the ' = ' character. org.xml.sax.SAXParseException; systemId: file:///var/lib/jenkins/jobs/COSMOS-CI-PERF-ew1-perftest-ping/builds/5/archive/dashBoard_*.xml; lineNumber: 9; columnNumber: 12; Attribute name "_ping" associated with an element type "GET" must be followed by the ' = ' character. ...long stacktrace... So, something tries to parse the XML file and because it's invalid XML (or not up to some standard anyway): ... 291 ... I am not sure why Jenkins would try to parse the archived XML file - looks like it's the NeoLoad plugin? But why would it do that? I think I'll open a ticket for them also and link here. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41558) Memory leak in Jenkins stage view
Title: Message Title Robin Björklin commented on JENKINS-41558 Re: Memory leak in Jenkins stage view I'm running 64-bit Firefox version 51.0.1 under Linux if it makes any difference. 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 Stanley Hillner commented on JENKINS-41766 Re: expose environment variable to indicate release Hi, good point. I thought about the ability to provide several env variables to the build but I'm not quite sure whether this made sense. I mean it could be possible to specify names and values of multiple variables instead of this one variable only. This way you could also configure the IS_M2RELEASEBUILD variable. Pros/Cons? 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 Stanley Hillner updated an issue Jenkins / JENKINS-41766 expose environment variable to indicate release Change By: Stanley Hillner Issue Type: Bug 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-41374) docker.image("busybox").inside() breaks
Title: Message Title
Seg Fault commented on JENKINS-41374
Re: docker.image("busybox").inside() breaks
A workaround for me is to use a wrapper script in a custom busybox image, built with this dockerfile:
FROM busybox
RUN echo -e '#!/bin/sh\nbusybox sh $@\n' >> /bin/bash && chmod ugo+x /bin/bash
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-41542) Run details changes
Title: Message Title Josh McDonald started work on JENKINS-41542 Change By: Josh McDonald 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-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Daniel Wilmer created an issue Jenkins / JENKINS-41791 Pipeline waiting for user input does not survive Jenkins restart Issue Type: Bug Assignee: Unassigned Attachments: blue ocean.png, log.png, paused for input.png, pipeline view.png Components: pipeline Created: 2017/Feb/07 6:36 AM Priority: Minor Reporter: Daniel Wilmer I have a lot of Pipeline Jobs that are waiting for user input before deploying to production. It is quite normal, that pipelines are in this state for several days. After a Jenkins restart (e.g. because of a Jenkins Update) the Pipelines are still in running state, but the user input controls are missing. log pipeline view paused for input Paused for input is available, but the controls are missing. blue ocean Add Comment
[JIRA] (JENKINS-41495) Jenkins Update for plugins URL not working in 2.32.1 version
Title: Message Title Cristian Uroz commented on JENKINS-41495 Re: Jenkins Update for plugins URL not working in 2.32.1 version Same here with version 2.32.1 In manage jenkins, when "check now" is pushed this exception is returned java.net.MalformedURLException: no protocol: ?id=default&version=2.32.1 at java.net.URL.(Unknown Source) at java.net.URL.(Unknown Source) at java.net.URL.(Unknown Source) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:180) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1619) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) 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.MetaClass$2.doDispatch(MetaClass.java:174) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.Basic
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title
Robert St. John edited a comment on JENKINS-41787
Re: Android Signing plugin command not correct...
The logging you provided indicates that you simply need to append {{\zipalign}} to the value of your {{ANDROID_ZIPALIGN}} variable, so the full value of {{ANDROID_ZIPALIGN}} should be {{d:\android-studio\build-tools\25.0.2\zipalign}}. The plugin expects the value of {{ANDROID_ZIPALIGN}} to be the full path to the {{zipalign}} executable, rather than the parent directory. My apologies if that is not clear in the [README|https://github.com/jenkinsci/android-signing-plugin]. I'll modify it to provide specific examples. Please let me know in a comment if that fixes your problem.Cheers
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-41495) Jenkins Update for plugins URL not working in 2.32.1 version
Title: Message Title
Cristian Uroz edited a comment on JENKINS-41495
Re: Jenkins Update for plugins URL not working in 2.32.1 version
Same here with version 2.32.1In manage jenkins plugins , when "check now" is pushed this exception is returned{code}java.net.MalformedURLException: no protocol: ?id=default&version=2.32.1 at java.net.URL.(Unknown Source) at java.net.URL.(Unknown Source) at java.net.URL.(Unknown Source) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:180) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1619) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) 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.MetaClass$2.doDispatch(MetaClass.java:174) 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:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilt
[JIRA] (JENKINS-41787) Android Signing plugin command not correct...
Title: Message Title Robert St. John commented on JENKINS-41787 Re: Android Signing plugin command not correct... The logging you provided indicates that you simply need to append \zipalign to the value of your ANDROID_ZIPALIGN variable, so the full value of ANDROID_ZIPALIGN should be d:\android-studio\build-tools\25.0.2\zipalign. The plugin expects the value of ANDROID_ZIPALIGN to be the full path to the zipalign executable, rather the parent directory. My apologies if that is not clear in the README. I'll modify it to provide specific examples. Please let me know in a comment if that fixes your problem. Cheers 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-41790) GitHub organization Webhook is not re-registered after deleting webhook on github
Title: Message Title Miyata Jumpei created an issue Jenkins / JENKINS-41790 GitHub organization Webhook is not re-registered after deleting webhook on github Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2017/Feb/07 6:18 AM Environment: OS: Ubuntu 14.04 Jenkins: docker container (jenkins:2.32.2) Plugin version: 2.0.1 Priority: Minor Reporter: Miyata Jumpei The following is the reproducing steps. 1. Create a GitHub organization folder 2. Delete the folder 3. Delete the org's webhook on GitHub 4. Create the GitHub organization folder again -> Webhook is not registered on GitHub It is because the existence of webhook is managed on Jenkins master as a file. https://github.com/jenkinsci/github-branch-source-plugin/blob/github-branch-source-2.0.1/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubOrgWebHook.java#L104 But I think it is not good idea. It seems that the existence of webhook can be checked by looking at urls of org's webhook. Add Comment
[JIRA] (JENKINS-41716) Upgrade Breaks NodeJS Tool Installations
Title: Message Title Matthew Sexton closed an issue as Duplicate I have validated that this fix was applied with the 1.0.1 update, and that an upgrade to 2.45 also did not reintroduce this issue. Duplicate of JENKINS-41535. Closing. Jenkins / JENKINS-41716 Upgrade Breaks NodeJS Tool Installations Change By: Matthew Sexton Status: Open Closed Resolution: Duplicate 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
[JIRA] (JENKINS-41625) Com Exception During Run
Title: Message Title Prabir Sooraj updated an issue Jenkins / JENKINS-41625 Com Exception During Run Change By: Prabir Sooraj Priority: Minor Major Encounter the following exception during the run of a suite. The exception causes the whole build to hang. The test set will usually run a few tests then encounter the below exception. Unhandled Exception: System.Runtime.InteropServices.COMException: The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT)) at Mercury.TD.Client.Ota.QC9.ITestSet.get_TSTestFactory() at HpToolsLauncher.AlmTestSetsRunner.RunTestSet(String tsFolderName, String tsName, Double timeout, QcRunMode runMode, String runHost) at HpToolsLauncher.AlmTestSetsRunner.Run() at HpToolsLauncher.Launcher.RunTests(IAssetRunner runner, String resultsFile) at HpToolsLauncher.Launcher.Run() at HpToolsLauncher.Program.Main(String[] args) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41784) REGRESSION: Window view does not follow long logs
Title: Message Title Josh McDonald resolved as Fixed Fixed in c8fef2ea6521e3590763724fdd477b603bcfa0a3 Jenkins / JENKINS-41784 REGRESSION: Window view does not follow long logs Change By: Josh McDonald Status: Open 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-41784) REGRESSION: Window view does not follow long logs
Title: Message Title Josh McDonald stopped work on JENKINS-41784 Change By: Josh McDonald Status: In Progress Open 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-40860) Go to the end of the expanded log
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-40860 Go to the end of the expanded log Change By: Michael Neale Assignee: Michael Neale 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-40860) Go to the end of the expanded log
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40860 Go to the end of the expanded log Change By: Michael Neale Sprint: pannonian release candidate , panthalassa pannonian 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-40860) Go to the end of the expanded log
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40860 Go to the end of the expanded log Change By: Michael Neale Priority: Major Minor 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-40860) Go to the end of the expanded log
Title: Message Title Michael Neale commented on JENKINS-40860 Re: Go to the end of the expanded log I tried, but can't reproduce this. I made a long pipeline log with a failing step - and it jumped to it. If there is another example we can record a video of - should do it, but we can park this for now (I suspect there is some race condition) 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-41784) REGRESSION: Window view does not follow long logs
Title: Message Title Josh McDonald commented on JENKINS-41784 Re: REGRESSION: Window view does not follow long logs https://github.com/jenkinsci/blueocean-plugin/pull/795 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-41789) GitLabTriggerPlugin Ignores Regex Match in DSL
Title: Message Title Jayme Howard commented on JENKINS-41789 Re: GitLabTriggerPlugin Ignores Regex Match in DSL https://github.com/jenkinsci/job-dsl-plugin/pull/992 should be all set to merge. 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 Michael Neale commented on JENKINS-41638 Re: "Open Blue Ocean" button doesn't work unless the server URL is set correctly My preference: if they don't have it setup correctly - just direct them to the basic /blue home page - which we know will work. If they have it set up correctly, all will be great for them, and we don't have to do crazy shenanigans to make it work without the correct config. If there is a warning to them that it isn't configured correctly - that is nice, but optional. 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 Michael Neale commented on JENKINS-41659 Re: Stabilise ATH Tom FENNELLY can we have a look at the event source stuff (if it is the cause of the recent badness) urgently? I can only work so many 16 hour days running the ATH for people by hand. 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 Michael Neale stopped work on JENKINS-41638 Change By: Michael Neale Status: In Progress Open 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-41789) GitLabTriggerPlugin Ignores Regex Match in DSL
Title: Message Title Jayme Howard created an issue Jenkins / JENKINS-41789 GitLabTriggerPlugin Ignores Regex Match in DSL Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2017/Feb/07 4:47 AM Environment: job-dsl-plugin: 1.57 gitlab-plugin: 1.44 Jenkins: 2.32.2 Labels: job-dsl-plugin gitlab Priority: Minor Reporter: Jayme Howard There is a flaw in the DSL support for the gitlab-plugin which causes the trigger to only work for standard matching, not regex. This is the default for the gitlab-plugin, so it just appears to work if you're not trying to use the regex match. I have a patch already written for this and will be submitting a pull request momentarily. Add Comment
[JIRA] (JENKINS-41788) sfaigerghu
Title: Message Title santosh reddy updated JENKINS-41788 Jenkins / JENKINS-41788 sfaigerghu Change By: santosh reddy Status: In Review Closed 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-41788) sfaigerghu
Title: Message Title santosh reddy updated JENKINS-41788 Jenkins / JENKINS-41788 sfaigerghu Change By: santosh reddy 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-41788) sfaigerghu
Title: Message Title santosh reddy created an issue Jenkins / JENKINS-41788 sfaigerghu Issue Type: Bug Assignee: santosh reddy Components: all-changes-plugin Created: 2017/Feb/07 4:45 AM Priority: Critical Reporter: santosh reddy 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 unsubsc
[JIRA] (JENKINS-41788) sfaigerghu
Title: Message Title santosh reddy started work on JENKINS-41788 Change By: santosh reddy 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-41787) Android Signing plugin command not correct...
Title: Message Title Tony Anecito created an issue Jenkins / JENKINS-41787 Android Signing plugin command not correct... Issue Type: Bug Assignee: Robert St. John Components: android-signing-plugin Created: 2017/Feb/07 4:39 AM Environment: Windows 10 Priority: Blocker Reporter: Tony Anecito Jenkins 2.44, android-signing-plugin 2.0.7, Windows 10, Java 1.8.0_91 When the signing plugin runs during the build I get an error: Total time: 4 mins 24.557 secs Build step 'Invoke Gradle script' changed build result to SUCCESS [SignApksBuilder] found zipalign path in env ANDROID_ZIPALIGN=d:\android-studio\build-tools\25.0.2 [Disaster Center] $ d:\android-studio\build-tools\25.0.2 -f -p 4 "C:\Users\\.jenkins\workspace\Disaster Center\app\build\outputs\apk\app-release-unsigned.apk" "C:\Users\\.jenkins\workspace\Disaster Center\app\build\outputs\apk\app-release-unsigned-aligned.apk" Access is denied FATAL: Cannot run program "d:\android-studio\build-tools\25.0.2" (in directory "C:\Users\\.jenkins\workspace\Disaster Center"): CreateProcess error=5, Access is denied java.io.IOException: Cannot run program "d:\android-studio\build-tools\25.0.2" (in directory "C:\Users\\.jenkins\workspace\Disaster Center"): CreateProcess error=5, Access is denied at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.(Proc.java:245) at hudson.Proc$LocalProc.(Proc.java:214) at hudson.Launcher$LocalLauncher.launch(Launcher.java:846) at hudson.Launcher$ProcStarter.start(Launcher.java:384) at hudson.Launcher$ProcStarter.join(Launcher.java:395) at org.jenkinsci.plugins.androidsigning.SignApksBuilder.perform(SignApksBuilder.java:158) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStep
[JIRA] (JENKINS-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder'
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41785 Multi-branch pipeline status icon no longer shows worst status of jobs in that multi-branch 'folder' Change By: Mark Waite Summary: Multi-branch pipeline status icon no longer shows worst status of jobs in that job multi-branch 'folder' 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-41166) Error shown in job configuration when master has no git installation
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-41166 Error shown in job configuration when master has no git installation Change By: Mark Waite Status: Open Closed Resolution: Won't Fix 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-41553) Git plugin should get list of submodules from git submodule status cmd
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-41553 Git plugin should get list of submodules from git submodule status cmd Change By: Mark Waite Assignee: 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41785
Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Change By:
Mark Waite
The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.Steps to see the expected behavior (before the change):# Clone my docker instance and checkout the JENKINS-41785-before tag{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before $ cd JENKINS-41785-before $ git checkout -b JENKINS-41785-before JENKINS-41785-before{code}# Build and run the docker instance{code} $ docker build -t jenkins:JENKINS-41785-before . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-before{code}# Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder# Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correctSteps to see the unexpected (changed) behavior:# Clone my docker instance and checkout the JENKINS-41785-after tag{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after $ cd JENKINS-41785-after $ git checkout -b JENKINS-41785-after JENKINS-41785-after{code}# Build and run the docker instance{code} $ docker build -t jenkins:JENKINS-41785-after . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-after{code}# Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status) (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! )# Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status) See ! parent Pipeline - folder icon - no-longer- shows- correct worst - aggregate job - color status .PNG|thumbnail! The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
[JIRA] (JENKINS-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41785
Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Change By:
Mark Waite
The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.Steps to see the expected behavior (before the change):# Clone my docker instance and checkout the JENKINS-41785-before tag{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before $ cd JENKINS-41785-before $ git checkout -b JENKINS-41785-before JENKINS-41785-before{code}# Build and run the docker instance{code} $ docker build -t jenkins:JENKINS-41785-before . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-before{code}# Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder# Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correctSteps to see the unexpected (changed) behavior:# Clone my docker instance and checkout the JENKINS-41785-after tag{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after $ cd JENKINS-41785-after $ git checkout -b JENKINS-41785-after JENKINS-41785-after{code}# Build and run the docker instance{code} $ docker build -t jenkins:JENKINS-41785-after . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-after{code}# Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status) (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! ) # Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status) See !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
[JIRA] (JENKINS-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41785
Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Change By:
Mark Waite
The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.Steps to see the expected behavior (before the change):# Clone my docker instance and checkout the JENKINS-41785-before tag{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before $ cd JENKINS-41785-before $ git checkout -b JENKINS-41785-before JENKINS-41785-before{code}# Build and run the docker instance{code} $ docker build -t jenkins:JENKINS-41785-before . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-before{code}# Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder# Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correctSteps to see the unexpected (changed) behavior:# Clone my docker instance and checkout the JENKINS-41785-after tag{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after $ cd JENKINS-41785-after $ git checkout -b JENKINS-41785-after JENKINS-41785-after{code}# Build and run the docker instance{code} $ docker build -t jenkins:JENKINS-41785-after . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-after{code}# Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status) (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail!) # Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status) See ! Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! ! parent-folder- configured-show-aggregate-ball-color-status.PNG|thumbnail! !parent-folder- shows-correct-aggregate-color.PNG|thumbnail! The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
[JIRA] (JENKINS-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41785
Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Change By:
Mark Waite
The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.Steps to see the expected behavior (before the change):# Clone my docker instance and checkout the JENKINS-41785-before tag{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before $ cd JENKINS-41785-before $ git checkout -b JENKINS-41785-before JENKINS-41785-before{code}# Build and run the docker instance{code} $ docker build -t jenkins:JENKINS-41785-before . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-before{code}# Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder# Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correctSteps to see the unexpected (changed) behavior:# Clone my docker instance and checkout the JENKINS-41785-after tag{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after $ cd JENKINS-41785-after $ git checkout -b JENKINS-41785-after JENKINS-41785-after{code}# Build and run the docker instance{code} $ docker build -t jenkins:JENKINS-41785-after . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-after{code}# Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)(see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! # Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status) See !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! !parent-folder-configured-show-aggregate-ball-color-status.PNG|thumbnail! !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.
[JIRA] (JENKINS-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-41785
Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Change By:
Mark Waite
The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.Steps to see the expected behavior (before the change):# Clone my docker instance and checkout the xx JENKINS-41785-before tag {code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before $ cd JENKINS-41785-before $ git checkout -b JENKINS-41785-before JENKINS-41785-before{code} # Build and run the docker instance # Run the {code} $ docker instance build -t jenkins:JENKINS-41785-before . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-before{code} # Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder# Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correctSteps to see the unexpected (changed) behavior:# Clone my docker instance and checkout the yy JENKINS-41785-after tag {code} $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after $ cd JENKINS-41785-after $ git checkout -b JENKINS-41785-after JENKINS-41785-after{code} # Build and run the docker instance # Run the {code} $ docker instance build -t jenkins:JENKINS-41785-after . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-41785-after{code} # Open a web browser to that running docker instance# Open the "Bugs - Pipeline Checks" folder# Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status) (see !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! # Open the jenkins-bugs multi-branch pipeline folder and index the branches# Wait until at least one of the pipeline jobs completes# Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status) !Pipeline-icon-no-longer-shows-worst-job-status.PNG|thumbnail! !parent-folder-configured-show-aggregate-ball-color-status.PNG|thumbnail! !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! The parent folder does still show the "worst status" when it is configured (see !parent-folder-shows-correct-aggregate-color.PNG|thumbnail! ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when
[JIRA] (JENKINS-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41785 Multi-branch pipeline status icon no longer shows worst status of jobs in that job Change By: Mark Waite Attachment: Pipeline-icon-no-longer-shows-worst-job-status.PNG 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-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41785 Multi-branch pipeline status icon no longer shows worst status of jobs in that job Change By: Mark Waite Attachment: parent-folder-shows-correct-aggregate-color.PNG 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-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-41785 Multi-branch pipeline status icon no longer shows worst status of jobs in that job Change By: Mark Waite Attachment: parent-folder-configured-show-aggregate-ball-color-status.PNG 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-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu edited a comment on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items Here's the benchmark together with putting multibranch project into another Cloudbees folder:|| || Chrome || Chrome || Chrome || Firefox || Firefox || Firefox Authorization Method || Open Projects Folder || Open Project-A Folder (with Multibranch job) || Open Project-A Folder (put multibranch into subfolder) || Open Projects Folder || Open Project-A Folder (with Multibranch job) || Open Project-A Folder (put multibranch into subfolder) Anyone can do anything | 2.10 sec | 8.43 sec | 1.24 | 5.99 sec | 17.05 sec | 4.34 ||| Logged-in users can do anything | 3.97 sec | 9.94 sec | 3.43 | 7.97 sec | 20.06 sec | 6.93 ||| Initial default Role-based configuration - admin role | 8.22 sec | 14.54 sec | 7.43 | 16.47 sec | 28.55 sec | 14.54 ||| Role-based configuration - admin role with 119 Project roles | 18.81 sec | 31.95 sec | 25.03 | 37.7 sec | 65 | 50.5 |From the table,the benchmark is now making sense:Open *ProjectA* with Cloudbees folder only (in theory should process only 6 items without recursive)now is faster than open *Projects* folder (in theory should process only 34 items without recursive) 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-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu edited a comment on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items Here's the benchmark together with putting multibranch project into another Cloudbees folder:|| || Chrome || Chrome || Chrome || Firefox || Firefox || Firefox Authorization Method || Open Projects Folder || Open Project-A Folder || Open Project-A Folder (put multibranch into subfolder) || Open Projects Folder || Open Project-A Folder || Open Project-A Folder (put multibranch into subfolder) Anyone can do anything | 2.10 sec | 8.43 sec | 1.24 | 5.99 sec | 17.05 sec | 4.34 ||| Logged-in users can do anything | 3.97 sec | 9.94 sec | 3.43 | 7.97 sec | 20.06 sec | 6.93 ||| Initial default Role-based configuration - admin role | 8.22 sec | 14.54 sec | 7.43 | 16.47 sec | 28.55 sec | 14.54 ||| Role-based configuration - admin role with 119 Project roles | 18.81 sec | 31.95 sec | 25.03 | 37.7 sec | 65 | 50.5 | From the table,the benchmark is now making sense:Open *ProjectA* with Cloudbees folder only (in theory should process only 6 items without recursive)now is faster than open *Projects* folder (in theory should process only 34 items without recursive) 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-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items Here's the benchmark together with putting multibranch project into another Cloudbees folder: Chrome Chrome Chrome Firefox Firefox Firefox Authorization Method Open Projects Folder Open Project-A Folder Open Project-A Folder (put multibranch into subfolder) Open Projects Folder Open Project-A Folder Open Project-A Folder (put multibranch into subfolder) Anyone can do anything 2.10 sec 8.43 sec 1.24 5.99 sec 17.05 sec 4.34 Logged-in users can do anything 3.97 sec 9.94 sec 3.43 7.97 sec 20.06 sec 6.93 Initial default Role-based configuration - admin role
[JIRA] (JENKINS-41786) Main search REST query retrieves overlapping data
Title: Message Title Ben Walding created an issue Jenkins / JENKINS-41786 Main search REST query retrieves overlapping data Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Feb/07 4:05 AM Priority: Trivial Reporter: Ben Walding The main search query is paged with a page size (limit) of 26. However the start is only incremented by 25 each time. Batch 1: Retrieve start = 0, limit=26 => items 0 - 25 Batch 2: Retrieve start = 25, limit=26 => items 25 - 50 i.e. item 25 has been retrieved twice Add Comment
[JIRA] (JENKINS-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title
Nikolas Falco edited a comment on JENKINS-40624
Re: nodejs installer not compatible with declarative pipeline definition
Current pipeline DSL supported are for:* nodejs tool definition{noformat}pipeline {agent anytools {nodejs 'Node 6.x'}stages {stage('Build') {steps {sh 'npm -version'}}}}{noformat}* and nodejs build step{noformat}pipeline {agent anystages {stage('Build') {steps {nodejs(nodeJSInstallationName: 'Node 6.x', configId: null) {sh 'npm config ls'}}}}}{noformat}[~robwatts] the code was merged in master.Before it is released could anyone provides feedback? A _mvn clean package_ is sufficient to create a snapshot from source code
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-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title Nikolas Falco updated JENKINS-40624 Jenkins / JENKINS-40624 nodejs installer not compatible with declarative pipeline definition Change By: Nikolas Falco 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-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title Nikolas Falco updated JENKINS-40624 Jenkins / JENKINS-40624 nodejs installer not compatible with declarative pipeline definition Change By: Nikolas Falco 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-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title
Nikolas Falco commented on JENKINS-40624
Re: nodejs installer not compatible with declarative pipeline definition
Current pipeline DSL supported are for:
nodejs tool definition
pipeline {
agent any
tools {
nodejs 'Node 6.x'
}
stages {
stage('Build') {
steps {
sh 'npm -version'
}
}
}
}
and nodejs build step
pipeline {
agent any
stages {
stage('Build') {
steps {
nodejs(nodeJSInstallationName: 'Node 6.x', configId: null) {
sh 'npm config ls'
}
}
}
}
}
Robert Watts the code was merged in master. Before it is released could anyone provides feedback?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41092) Build Triggers > Build periodically is not preset for child project by multi-branch-project-plugin
Title: Message Title Matthew DeTullio resolved as Not A Defect This is intended. The parent project does the polling and triggers the child projects. Schedules don't get copied to the children. Jenkins / JENKINS-41092 Build Triggers > Build periodically is not preset for child project by multi-branch-project-plugin Change By: Matthew DeTullio Status: Open Resolved Resolution: Not A Defect 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 sto
[JIRA] (JENKINS-41399) API to get reason for MBP and Org Folder failures
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41399 API to get reason for MBP and Org Folder failures Change By: James Dumay Sprint: iapetus panthalassa 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-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title Matthew DeTullio updated an issue Jenkins / JENKINS-41785 Multi-branch pipeline status icon no longer shows worst status of jobs in that job Change By: Matthew DeTullio Component/s: workflow-multibranch-plugin Component/s: multi-branch-project-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-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title Matthew DeTullio assigned an issue to Unassigned Jenkins / JENKINS-41785 Multi-branch pipeline status icon no longer shows worst status of jobs in that job Change By: Matthew DeTullio Assignee: Matthew DeTullio 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-41785) Multi-branch pipeline status icon no longer shows worst status of jobs in that job
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-41785 Multi-branch pipeline status icon no longer shows worst status of jobs in that job Issue Type: Bug Assignee: Matthew DeTullio Components: cloudbees-folder-plugin, core, multi-branch-project-plugin Created: 2017/Feb/07 3:48 AM Environment: Refer to my docker repository for precise configuration before the problem was first detected, and for precise configuration after the problem was detected. Priority: Minor Reporter: Mark Waite The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status. Steps to see the expected behavior (before the change): Clone my docker instance and checkout the xx tag Build the docker instance Run the docker instance Open a web browser to that running docker instance Open the "Bugs - Pipeline Checks" folder Observe the icon for the jenkins-bugs multi-branch pipeline folder Open the jenkins-bugs multi-branch pipeline folder and index the branches Wait until at least one of the pipeline jobs completes
[JIRA] (JENKINS-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40624 Re: nodejs installer not compatible with declarative pipeline definition Code changed in jenkins User: Nikolas Falco Path: pom.xml src/main/java/jenkins/plugins/nodejs/NodeJSBuildWrapper.java src/main/java/jenkins/plugins/nodejs/NodeJSCommandInterpreter.java src/main/java/jenkins/plugins/nodejs/NodeJSUtils.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstallation.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java src/test/java/jenkins/plugins/nodejs/NpmrcFileSupplyTest.java src/test/java/jenkins/plugins/nodejs/configfiles/RegistryHelperTest.java src/test/resources/jenkins/plugins/nodejs/dsl/NodeJSBuild.pipeline src/test/resources/jenkins/plugins/nodejs/dsl/NodeJSInstallation.pipeline http://jenkins-ci.org/commit/nodejs-plugin/cebb2bc6e8077bb9e1816d32d1ac7f6ce7c35188 Log: JENKINS-40624 Add @Symbol annotation to builder wrapper. Rework of installer to support pipeline (Computer.currectComputer returns always null). Provide some DSL sample to use in the future with unit test (current version of jenkins does not support pipeline). Like other plugin does we add support to pipeline adding @Symbol annotation but version of jenkins is that one defined in the parent pom to support older versions. 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/optou
[JIRA] (JENKINS-41784) REGRESSION: Window view does not follow long logs
Title: Message Title Josh McDonald started work on JENKINS-41784 Change By: Josh McDonald 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-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu edited a comment on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items I did further a further benchmark testing.After I put each of 5 of Multibranch jobs into another Cloudbees folder,somehow the "*ProjectA*" load time is improved by 7 seconds.This makes wonder could it be a bug for the multi-branch-project-plugin?The multi-branch-project job doesn't behave like Cloudbees folder that preventing the Jenkins core to process permission recursively.Hence loading a page containing only 1 multi-branch-project item would recursively get to the branch jobs.If this is true,then this bug would still be valid for Multi-branch-project job. Or if it's Jenkins core always process items recursively,then Jenkins core is process extra un-needed items,and it'd be a bug. I'll reopen the bug for 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-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu edited a comment on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items I did further a further benchmark testing.After I put each of 5 of Multibranch jobs into another Cloudbees folder,somehow the "*ProjectA*" load time is improved by 7 seconds.This makes wonder could it be a bug for the multi-branch-project-plugin?The multi-branch-project job doesn't behave like Cloudbees folder that preventing the Jenkins core to process permission recursively.Hence loading a page containing only 1 multi-branch-project item would recursively get to the branch jobs.If this is true,then this bug would still be valid for Multi-branch-project job. Or if it's Jenkins core always process items recursively,then Jenkins core is process extra un-needed items,and it'd be a bug. I'll reopen the bug for 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-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu reopened an issue I did further a further benchmark testing. After I put each of 5 of Multibranch jobs into another Cloudbees folder, somehow the "ProjectA" load time is improved by 7 seconds. This makes wonder could it be a bug for the multi-branch-project-plugin? The multi-branch-project job doesn't behave like Cloudbees folder that preventing the Jenkins core to process permission recursively. Hence loading a page containing only 1 multi-branch-project item would recursively get to the branch jobs. If this is true, then this bug would still be valid for Multi-branch-project job. I'll reopen the bug for now. Jenkins / JENKINS-41722 Job folder loading performance is worse when folder contains fewer items Change By: Rick Liu Resolution: Not A Defect Status: Resolved Reopened 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 Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items I did further a further benchmark testing. After I put each of 5 of Multibranch jobs into another Cloudbees folder, somehow the "ProjectA" load time is improved by 7 seconds. This makes wonder could it be a bug for the multi-branch-project-plugin? The multi-branch-project job doesn't behave like Cloudbees folder that preventing the Jenkins core to process permission recursively. Hence loading a page containing only 1 multi-branch-project item would recursively get to the branch jobs. If this is true, then this bug would still be valid for Multi-branch-project job. I'll reopen the bug for 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-41784) REGRESSION: Window view does not follow long logs
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41784 REGRESSION: Window view does not follow long logs Change By: Michael Neale Sprint: iapetus 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-41784) REGRESSION: Window view does not follow long logs
Title: Message Title Michael Neale assigned an issue to Josh McDonald Jenkins / JENKINS-41784 REGRESSION: Window view does not follow long logs Change By: Michael Neale Assignee: Josh McDonald 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-41784) REGRESSION: Window view does not follow long logs
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-41784
REGRESSION: Window view does not follow long logs
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2017/Feb/07 3:22 AM
Priority:
Critical
Reporter:
Michael Neale
You can see a video of it here: http://www.giphy.com/gifs/26xBJwaD7pnH7wdiw It should make the view scroll down to tail the log. To reproduce:
node {
stage('yeah') {
sh 'ping -c 40 www.apple.com'
}
stage('shorty') {
sh 'ping -c 5 www.apple.com'
}
}
Run this as a basic pipeline, and as long as your screen height isn't too high, you will see it. This should follow along with the log. When the log completes, it would be folded away, and it starts again.
Add Comment
[JIRA] (JENKINS-22983) The job status should correspond the branch with the worst build status
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins multi-branch pipeline will automatically create and destroy a job for each branch. I think that is a more broadly usable technique than overloading the semantics of the job status icon for a specific job. Jenkins / JENKINS-22983 The job status should correspond the branch with the worst build status Change By: Mark Waite Status: Open Closed Resolution: Won't Fix 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" gro
[JIRA] (JENKINS-41722) Job folder loading performance is worse when folder contains fewer items
Title: Message Title Rick Liu commented on JENKINS-41722 Re: Job folder loading performance is worse when folder contains fewer items Daniel Beck Could you also clarify whether Jenkins core always load page with recursive calls of process permission? 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-41542) Run details changes
Title: Message Title Josh McDonald commented on JENKINS-41542 Re: Run details changes More importantly, we're going to have a lot of layouts that can blow out with extension points, so y'all might want to warm up to letting go of a little control 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-41542) Run details changes
Title: Message Title Josh McDonald commented on JENKINS-41542 Re: Run details changes I'll do what I can about the alignment stuff, but no promises you're going to get pixel-perfection, IIRC it doesn't fit exactly evenly. I mean, I can put things on half-pixels and it'll be sweet on retina, but god help those people on duplo-pixels with IE's text renderer 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-27845) Support auto install on Mac OS X
Title: Message Title Nikolas Falco resolved as Fixed Mac OS is supported and installation of NodeJS 0.10 till 6.9 was tested and works. The NodeJSInstallation delegate to the default jenkins DownloadFromUrlInstaller class download and install of mac archives (tar.gz) Jenkins / JENKINS-27845 Support auto install on Mac OS X Change By: Nikolas Falco Status: Open 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
[JIRA] (JENKINS-24425) Using both NodeJS and Rbenv build environment plugins, rbenv is unable to create .rbenv.lock directory
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-24425 Using both NodeJS and Rbenv build environment plugins, rbenv is unable to create .rbenv.lock directory Change By: Nikolas Falco Status: Open Closed 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-41542) Run details changes
Title: Message Title Josh McDonald commented on JENKINS-41542 Re: Run details changes Note to self: ellipses for long branches, as per JENKINS-41782 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-41782) Text wrapping in run details
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-41782 Text wrapping in run details Change By: Michael Neale long creative descriptions can be common. Elipsis should be used. 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-41088) Show "latest" run results via fixed URL (dashboard like feature)
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41088 Show "latest" run results via fixed URL (dashboard like feature) Change By: James Dumay Labels: adoption 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-36166) Internal Server Error on creating new job from Jenkins API written in Node.js
Title: Message Title Nikolas Falco closed an issue as Not A Defect This is not related to NodeJS Plugin and I think also with any other jenkins plugin. From the attachment: java.io.IOException: Failed to persist config.xml at hudson.model.ItemGroupMixIn.createProjectFromXML(ItemGroupMixIn.java:299) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:194) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:3102) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:308) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) Check your _javascript_ library documentation, or open a defect to the correct component. Jenkins / JENKINS-36166 Internal Server Error on creating new job from Jenkins API written in Node.js Change By: Nikolas Falco Status: Open Closed Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-41782) Text wrapping in run details
Title: Message Title Michael Neale commented on JENKINS-41782 Re: Text wrapping in run details What did the old one used to do? as we have always had very long branch names. 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-41783) Editor link in header is incorrectly placed in the new design
Title: Message Title Keith Zantow commented on JENKINS-41783 Re: Editor link in header is incorrectly placed in the new design James Dumay yes, exactly. this is a perfect example of the nested component mess being overkill and complicating stuff. 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-41782) Text wrapping in run details
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-41782 Text wrapping in run details Change By: James Dumay Status: Open Resolved Resolution: Duplicate 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-36166) Internal Server Error on creating new job from Jenkins API written in Node.js
Title: Message Title Nikolas Falco edited a comment on JENKINS-36166 Re: Internal Server Error on creating new job from Jenkins API written in Node.js Can you provide more informations about the issue?From your job config.xml i can not see any nodejs plugin builder configured .Seems that you are using this library https://github.com/jansepar/node-jenkins-api implemented in NodeJS to handle a Jenkins server instance, but it's not related with NodeJS 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-41542) Run details changes
Title: Message Title Josh McDonald commented on JENKINS-41542 Re: Run details changes <-- Fix long-branch-name also 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-41542) Run details changes
Title: Message Title Josh McDonald updated an issue Jenkins / JENKINS-41542 Run details changes Change By: Josh McDonald Attachment: screenshot-1.png 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-37834) Spacing and alignment of "action" icons is inconsistent
Title: Message Title James Dumay resolved as Won't Fix Will do the table overhaul instead Jenkins / JENKINS-37834 Spacing and alignment of "action" icons is inconsistent Change By: James Dumay Status: Open Resolved Resolution: Won't Fix 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-40202) Action buttons are misaligned
Title: Message Title James Dumay updated JENKINS-40202 Jenkins / JENKINS-40202 Action buttons are misaligned Change By: James Dumay Status: Resolved In 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-41783) Editor link in header is incorrectly placed in the new design
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41783 Editor link in header is incorrectly placed in the new design Issue Type: Bug Assignee: Keith Zantow Attachments: editortab.png Components: blueocean-pipeline-editor-plugin Created: 2017/Feb/07 2:37 AM Priority: Minor Reporter: James Dumay Need to fix the Pipeline Editor link up in the new design (now on master). Release an update to the editor when beta 23 is released. Sidenote: heres where a typed extension point "link" would be handy Add Comment
[JIRA] (JENKINS-41547) Container must have a max-width
Title: Message Title Josh McDonald closed an issue as Fixed Fixed in master Jenkins / JENKINS-41547 Container must have a max-width Change By: Josh McDonald Status: Resolved Closed 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-40202) Action buttons are misaligned
Title: Message Title Josh McDonald commented on JENKINS-40202 Re: Action buttons are misaligned Definitely not worth fixing with impending table overhaul 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-36166) Internal Server Error on creating new job from Jenkins API written in Node.js
Title: Message Title Nikolas Falco commented on JENKINS-36166 Re: Internal Server Error on creating new job from Jenkins API written in Node.js Can you provide more informations about the issue? From your job config.xml i can not see any nodejs plugin builder configured 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-41782) Text wrapping in run details
Title: Message Title James Dumay created an issue Jenkins / JENKINS-41782 Text wrapping in run details Issue Type: Bug Assignee: Josh McDonald Attachments: wrapping.png Components: blueocean-plugin Created: 2017/Feb/07 2:34 AM Priority: Minor Reporter: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-41715) Git credentials selection + git ls-remote test of config is wonky
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-41715 Git credentials selection + git ls-remote test of config is wonky Change By: Mark Waite Assignee: 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40545) NPE in console log when I configure a folder in a folder or a pipeline in a folder
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-40545 NPE in console log when I configure a folder in a folder or a pipeline in a folder Change By: Mark Waite Comment: Can you provide more details on how to duplicate the problem? 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-41762) NodeJS plugin not updating PATH as expected
Title: Message Title Nikolas Falco commented on JENKINS-41762 Re: NodeJS plugin not updating PATH as expected This sound like duplicate of JENKINS-27170 Do you have EnvInject plugin installed? If yes than you fall in JENKINS-26583 Workaround is remove EnvInject plugin, or make a custom build of workaround-26583 branch. (this branch will never merge into master, it's a EnvInject plugin issue not nodejs) 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-40545) NPE in console log when I configure a folder in a folder or a pipeline in a folder
Title: Message Title
Mark Waite edited a comment on JENKINS-40545
Re: NPE in console log when I configure a folder in a folder or a pipeline in a folder
I am able to duplicate the null pointer exception in h.filterDescriptors without any message from the git plugin. I believe this is a problem in core, though I could easily be wrong.Steps I take to see the problem:# Clone my docker repository and checkout the lts-with-plugins branch{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-40545 $ cd JENKINS-40545 $ git checkout -b lts-with-plugins -t origin/lts-with-plugins{code}# Build and run that docker image{code} $ docker build -t jenkins:JENKINS-40545 . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-40545{code}# Open a web browser to http://localhost:8080/# Click the "Git Client Plugin Folder" folder in that web browser# Click the "Git Client Branches - Maven" multi-branch job# Click the "Configure" link in that multi-branch maven job, and watch the console log from the docker imageThe console log reports:{noformat}Feb 06, 2017 6:55:04 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /job/Git-Folder/job/git-plugin-freestyle-multi-branch/configure. Reason: java.lang.NullPointerExceptionjava.lang.NullPointerExceptionat hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:72)at hudson.Functions.filterDescriptors(Functions.java:1790)at sun.reflect.GeneratedMethodAccessor437.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){noformat}I see the same null pointer exception if I try to configure a folder inside a folder. For example, the problem happens if I use the following steps:# Click the "Hosting Providers" top level folder# Click the "Assembla" folder# Click the "Configure" link in the Assembla folder (folder in a folder)I don't see that null pointer exception when I configure a freestyle job inside a folder. Just in case this behavior changes from later modifications to my lts-with-plugins branch, I placed a git tag named "[JENKINS-40545|https://github.com/MarkEWaite/docker/releases/tag/JENKINS-40545]" in that repository.
[JIRA] (JENKINS-41781) Blue Ocean - UI support for multiple build and test in parallel
Title: Message Title mishal shah created an issue Jenkins / JENKINS-41781 Blue Ocean - UI support for multiple build and test in parallel Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2017-02-06 at 6.16.53 PM.png Components: blueocean-plugin Created: 2017/Feb/07 2:23 AM Environment: Jenkins 2.32.2 Priority: Minor Reporter: mishal shah Add support in the UI to handle multiple build in parallel. Please see attached screen shot. Add Comment
[JIRA] (JENKINS-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-41767 Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method Change By: Nikolas Falco Component/s: config-file-provider-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-40545) NPE in console log when I configure a folder in a folder or a pipeline in a folder
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-40545
NPE in console log when I configure a folder in a folder or a pipeline in a folder
Change By:
Mark Waite
A null pointer exception is reported by the jelly code when I try to configure a folder in a folder or a pipeline in a folder.The message is "Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /configure. Reason: java.lang.NullPointerException" Refer to [comment later in this report|https://issues.jenkins-ci.org/browse/JENKINS-40545?focusedCommentId=286511&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-286511] for steps [~markewaite] used to duplicate the problem.{noformat}ERROR: Timeout after 10 minutesERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git fetch --tags --progress http://dev.newtranx.com:18080/git/app/newtranxPT_iOS.git +refs/heads/*:refs/remotes/origin/*" returned status code 143:stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:512) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) at hudson.scm.SCM.checkout(SCM.java:495) 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:1720) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)ERROR: null{noformat}{noformat}Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /configure. Reason: java.lang.NullPointerExceptionjava.lang.NullPointerException at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:72) at hudson.Functions.filterDescriptors(Functions.java:1790) at sun.reflect.GeneratedMethodAccessor266.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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.
[JIRA] (JENKINS-41767) Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
Title: Message Title
Nikolas Falco commented on JENKINS-41767
Re: Exception in jenkins log: class org.jenkinsci.lib.configprovider.model.Config must override 'getDescriptor()' this method
The issue JENKINS-41535 has been closed. Anyway the log above seems not related to NodeJS plugin code. When you open the job configuration page I populate a combobox with all available config of kind NPMConfig. The config holder (part of config-file-provider plugin) cycle on all extension and filter configs by the given descriptor class. The error in the log is caused due new API changes in config-file-provider that requires all extension point (Config) have to implement the getDescriptor method (as NPMConfig already does) in the subclass. Excluding config type shipped with the config-file-provider plugin, you could have other plugin that extends it but it's not updated to latest API (>=2.15). So in short I see two way:
check which other plugin in your jenkins extends config-file-provider and ask to mantainer update to new API
ask to Dominik Bartholdi to handle this kind of scenario providing a default implementation of getDescriptor() in the super class like:
return (ConfigProvider) Jenkins.getActiveInstance().getDescriptorOrDie(getClass());
or surround the code in GlobalConfigFiles#getConfigs(Class) to handle that exception
public Collection getConfigs(Classextends Descriptor> descriptor) {
List cs = new ArrayList();
for (Config c : configs) {
ConfigProvider provider;
try {
provider = c.getDescriptor();
} catch (IllegalStateException e) {
// continue or a a sort of fallback code
provider = Jenkins.getActiveInstance().getDescriptorOrDie(c.getClass());
}
if (provider.getClass().equals(descriptor)) {
cs.add(c);
}
}
return cs;
}
or something similar.
Add Comment
[JIRA] (JENKINS-40545) NPE to console log when I configure a folder in a folder or a pipeline in a folder
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-40545 NPE to console log when I configure a folder in a folder or a pipeline in a folder Change By: Mark Waite Summary: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in / NPE to console log when I configure . Reason: java.lang.NullPointerException a folder in a folder or a pipeline in a folder 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-40545) NPE in console log when I configure a folder in a folder or a pipeline in a folder
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-40545 NPE in console log when I configure a folder in a folder or a pipeline in a folder Change By: Mark Waite Summary: NPE to in console log when I configure a folder in a folder or a pipeline in a folder 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-40545) Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /configure. Reason: java.lang.NullPointerException
Title: Message Title
Mark Waite edited a comment on JENKINS-40545
Re: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /configure. Reason: java.lang.NullPointerException
I am able to duplicate the null pointer exception in h.filterDescriptors without any message from the git plugin. I believe this is a problem in core, though I could easily be wrong.Steps I take to see the problem:# Clone my docker repository and checkout the lts-with-plugins branch{code} $ git clone https://github.com/MarkEWaite/docker JENKINS-40545 $ cd JENKINS-40545 $ git checkout -b lts-with-plugins -t origin/lts-with-plugins{code}# Build and run that docker image{code} $ docker build -t jenkins:JENKINS-40545 . $ docker run -i --rm --publish 8080:8080 --publish 5:5 --publish 18022:18022 -t jenkins:JENKINS-40545{code}# Open a web browser to http://localhost:8080/# Click the "Git Client Plugin Folder" folder in that web browser# Click the "Git Client Branches - Maven" multi-branch job# Click the "Configure" link in that multi-branch maven job, and watch the console log from the docker imageThe console log reports:{noformat}Feb 06, 2017 6:55:04 PM hudson.ExpressionFactory2$JexlExpression evaluateWARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /job/Git-Folder/job/git-plugin-freestyle-multi-branch/configure. Reason: java.lang.NullPointerExceptionjava.lang.NullPointerExceptionat hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:72)at hudson.Functions.filterDescriptors(Functions.java:1790)at sun.reflect.GeneratedMethodAccessor437.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){noformat}I see the same null pointer exception if I try to configure a pipeline inside a folder. For example, the problem happens if I use the following steps: # Click the "Hosting Providers" top level folder # Click the "Assembla" folder# Click the "Configure" link in the Assembla folder (folder in a folder) I don't see that null pointer exception when I configure a freestyle job inside a folder.
