[JIRA] (JENKINS-30187) Cobetura plugin giving [ERROR] net.sourceforge.cobertura.javancss.parser.ParseException while using java 7.
Title: Message Title Steven Christou closed an issue as Won't Do This is an issue with core cobertura parsing your source code. Please file a bug in the cobertura repository and provide this error message along with the line code code it is trying to parse (line 11 column 14). Jenkins / JENKINS-30187 Cobetura plugin giving [ERROR] net.sourceforge.cobertura.javancss.parser.ParseException while using java 7. Change By: Steven Christou Status: Open Closed Assignee: Steven Christou Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42522) FLOW plugin deletes old data on startup
Title: Message Title
Steven Christou updated an issue
Jenkins / JENKINS-42522
FLOW plugin deletes old data on startup
Change By:
Steven Christou
The flow plugin at startup will delete all old data because it performs a save operation: { {\{\{ noformat} "Jenkins initialization thread@2736" daemon prio=5 tid=0x27 nid=NA runnable java.lang.Thread.State: RUNNABLE at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at hudson.model.AbstractItem.save(AbstractItem.java:521) - locked <0x3690> (a hudson.model.FreeStyleProject) at hudson.model.Job.save(Job.java:180) at hudson.model.AbstractProject.save(AbstractProject.java:306) at hudson.model.Job.addProperty(Job.java:523) at hudson.model.AbstractProject.addProperty(AbstractProject.java:786) at org.jenkinsci.plugins.flow_plugin.FlowProjectListener.addFlowProperty(FlowProjectListener.java:33) at org.jenkinsci.plugins.flow_plugin.FlowProjectListener.onLoaded(FlowProjectListener.java:17) at jenkins.model.Jenkins.(Jenkins.java:857) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225) {noformat } }}} At startup a flow property is added to each job which triggers a save operation. This happens for _any_ project. On another note: I am unable to locate the source code for this plugin.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42522) FLOW plugin deletes old data on startup
Title: Message Title
Steven Christou updated an issue
Jenkins / JENKINS-42522
FLOW plugin deletes old data on startup
Change By:
Steven Christou
The flow plugin at startup will delete all old data because it performs a save operation: \ { noformat} { \ { \{ "Jenkins initialization thread@2736" daemon prio=5 tid=0x27 nid=NA runnable java.lang.Thread.State: RUNNABLE at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at hudson.model.AbstractItem.save(AbstractItem.java:521) - locked <0x3690> (a hudson.model.FreeStyleProject) at hudson.model.Job.save(Job.java:180) at hudson.model.AbstractProject.save(AbstractProject.java:306) at hudson.model.Job.addProperty(Job.java:523) at hudson.model.AbstractProject.addProperty(AbstractProject.java:786) at org.jenkinsci.plugins.flow_plugin.FlowProjectListener.addFlowProperty(FlowProjectListener.java:33) at org.jenkinsci.plugins.flow_plugin.FlowProjectListener.onLoaded(FlowProjectListener.java:17) at jenkins.model.Jenkins.(Jenkins.java:857) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225) }} \{noformat } } At startup a flow property is added to each job which triggers a save operation. This happens for _any_ project. On another note: I am unable to locate the source code for this plugin.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42522) FLOW plugin deletes old data on startup
Title: Message Title
Steven Christou updated an issue
Jenkins / JENKINS-42522
FLOW plugin deletes old data on startup
Change By:
Steven Christou
Summary:
Metadata FLOW plugin deletes old data on startup
Component/s:
flow-plugin
Component/s:
metadata-plugin
The metadata flow plugin at startup will delete all old data content at the start of because it performs a save operation: \{noformat}{{" Jenkins initialization thread@2736" daemon prio=5 tid=0x27 nid=NA runnable java . In order to re lang.Thread.State: RUNNABLE at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:81) at hudson.model.AbstractItem.save(AbstractItem.java:521) - build the metadata information the plugin triggers locked <0x3690> ( a hudson.model.FreeStyleProject) at hudson.model.Job. save operation ( https Job.java : //github 180) at hudson . com/jenkinsci/metadata-plugin/blob/master/src/main/ model.AbstractProject.save(AbstractProject. java /com/sonyericsson/ :306) at hudson / .model.Job.addProperty(Job.java:523) at hudson.model.AbstractProject.addProperty(AbstractProject.java:786) at org.jenkinsci. plugins /metadata/contributors/JobContributorsController . flow_plugin.FlowProjectListener.addFlowProperty(FlowProjectListener. java #L89-L91 :33 ) at the start of org.jenkinsci.plugins.flow_plugin.FlowProjectListener.onLoaded(FlowProjectListener.java:17) at jenkins.model. Jenkins for each job . Because of this save operation it will delete any old data and override it (Jenkins . There should be java:857) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225) }}\{noformat} At startup a way flow property is added to trigger the rebuilding of metadata information without having to perform each job which triggers a save operation at . This happens for _any_ project. On another note: I am unable to locate the start of Jenkins source code for this plugin .
[JIRA] (JENKINS-42639) Parameterized trigger hangs when script not approved
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-42639 Parameterized trigger hangs when script not approved Change By: Steven Christou If you trigger another job with the parameterized trigger plugin and the script for the other job is not approved yet, it will hang forever. Steps to reproduce: # Create a job (Job A) with a script not yet approved. # Create another job (Job B) with a parameterized trigger which calls the previous job (Make sure to check the option to block when building). # Trigger the parameterized job (Job B)Taking a thread dump it will show that Job B is blocked until Job A is built, and since Job A requires approval it will never complete. It would be nice if the job failed with a message about the script needing to be approved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-42639) Parameterized trigger hangs when script not approved
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-42639 Parameterized trigger hangs when script not approved Issue Type: Improvement Assignee: huybrechts Components: parameterized-trigger-plugin, script-security-plugin Created: 2017/Mar/09 8:27 PM Priority: Major Reporter: Steven Christou If you trigger another job with the parameterized trigger plugin and the script for the other job is not approved yet, it will hang forever. Steps to reproduce: Create a job (Job A) with a script not yet approved. Create another job (Job B) with a parameterized trigger which calls the previous job (Make sure to check the option to block when building). Trigger the parameterized job (Job B) Taking a thread dump it will show that Job B is blocked until Job A is built, and since Job A requires approval it will never complete. It would be nice if the job failed with a message about the script needing to be approved. Add
[JIRA] (JENKINS-42522) Metadata plugin deletes old data on startup
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-42522 Metadata plugin deletes old data on startup Issue Type: Bug Assignee: rsandell Components: metadata-plugin Created: 2017/Mar/06 11:53 PM Priority: Critical Reporter: Steven Christou The metadata plugin will delete old data content at the start of Jenkins. In order to re-build the metadata information the plugin triggers a save operation (https://github.com/jenkinsci/metadata-plugin/blob/master/src/main/java/com/sonyericsson/hudson/plugins/metadata/contributors/JobContributorsController.java#L89-L91) at the start of Jenkins for each job. Because of this save operation it will delete any old data and override it. There should be a way to trigger the rebuilding of metadata information without having to perform a save operation at the start of Jenkins. Add Comment
[JIRA] (JENKINS-42376) Report project which caused dead executor thread
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-42376 Report project which caused dead executor thread Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Feb/28 6:07 PM Priority: Trivial Reporter: Steven Christou The error message is reported if the nextBuildNumber is lower than the current build number: hudson.model.Executor#run: Unexpected executor death java.lang.IllegalStateException: cannot create a build with number NUMBER since that (or higher) is already in use among [NUMBER] Unfortunately this does not report the actual project which is hitting the issue, so it is difficult to determine which project(s) need to be fixed. You can easily reproduce this problem by triggering 3 builds and manually setting the nextBuildNumber file to be 1. Triggering a new build will kill the build executor thread. Add Comment
[JIRA] (JENKINS-42043) A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting
Title: Message Title Steven Christou commented on JENKINS-42043 Re: A NPE in SlaveComputer.setNode shouldn't prevent Jenkins from starting My $0.02 - I think it should keep the node and act as if it is a disconnected node instead of removing the node (i.e. ignore it and move on with the startup). We should never be removing nodes from the list that fail to connect. We should only remove them if the node is manually removed by an administrator, or the node is removed by the plugin via a timeout. 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-40552) Deadlock between JobPropertyImpl and PromotionProcess
Title: Message Title Steven Christou assigned an issue to Steven Christou Jenkins / JENKINS-40552 Deadlock between JobPropertyImpl and PromotionProcess Change By: Steven Christou Assignee: christ66 Steven Christou 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-41145) Node response times might show incorrect values
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-41145 Node response times might show incorrect values Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Jan/17 5:39 PM Priority: Minor Reporter: Steven Christou Currently the response times for the Jenkins agents are computed using: System.currentTimeMillis(); https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/node_monitors/ResponseTimeMonitor.java#L109, So the response time might be slightly skewed. Instead it might be better if we switch to using System.nanoTime(); for more accurate times. Add Comment
[JIRA] (JENKINS-40094) Global config.xml only contains a exception
Title: Message Title Steven Christou updated JENKINS-40094 Jenkins / JENKINS-40094 Global config.xml only contains a exception Change By: Steven Christou 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-37318) Generate a background thread to allow for integration with Plugin Usage Plugin
Title: Message Title Steven Christou commented on JENKINS-37318 Re: Generate a background thread to allow for integration with Plugin Usage Plugin Closing as won't fix. This should come from the Component extension point in the support core plugin and this information should be generated at runtime. There is a caching mechanism we use in the support core plugin, which can be used to cache the results from the plugin usage 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-37318) Generate a background thread to allow for integration with Plugin Usage Plugin
Title: Message Title Steven Christou closed an issue as Won't Fix Jenkins / JENKINS-37318 Generate a background thread to allow for integration with Plugin Usage Plugin Change By: Steven Christou 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-39275) StepExecution tostring hangs
Title: Message Title Steven Christou assigned an issue to Jesse Glick Jenkins / JENKINS-39275 StepExecution tostring hangs Change By: Steven Christou Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39275) StepExecution tostring hangs
Title: Message Title
Steven Christou updated an issue
Jenkins / JENKINS-39275
StepExecution tostring hangs
Change By:
Steven Christou
There is some improvements to be made in the support core plugin (will create a different ticket jira ), but there is a case where the pipeline step executions toString method can hang forever if it is unable to obtain the durable task steps workspace:{noformat}"Running CpsFlowExecution[Owner[JOB_NAME:JOB_NAME#BUILD_NUMBER]] / waiting for hudson.remoting.Channel@1:NODE_NAME" #1 daemon prio=5 os_prio=0 tid=0x2e00d800 nid=0x4a8 in Object.wait() [0x2f5de000] java.lang.Thread.State: TIMED_WAITING (on object monitor)at java.lang.Object.wait(Native Method)at hudson.remoting.Request.call(Request.java:147)- locked <0x0007b795ff98> (a hudson.remoting.UserRequest)at hudson.remoting.Channel.call(Channel.java:780)at hudson.FilePath.act(FilePath.java:979)at hudson.FilePath.act(FilePath.java:968)at hudson.FilePath.isDirectory(FilePath.java:1504)at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.getWorkspace(DurableTaskStep.java:108)at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.getStatus(DurableTaskStep.java:153)at org.jenkinsci.plugins.workflow.steps.StepExecution.toString(StepExecution.java:98)at java.lang.String.valueOf(String.java:2994)at java.lang.StringBuilder.append(StringBuilder.java:131)at java.util.AbstractCollection.toString(AbstractCollection.java:462)at java.util.Collections$UnmodifiableCollection.toString(Collections.java:1035)at java.text.MessageFormat.subformat(MessageFormat.java:1280)at java.text.MessageFormat.format(MessageFormat.java:865)at java.text.Format.format(Format.java:157)at java.text.MessageFormat.format(MessageFormat.java:841)at java.util.logging.Formatter.formatMessage(Formatter.java:138)- locked <0x0006c394e168> (a com.cloudbees.jenkins.support.SupportLogFormatter)at com.cloudbees.jenkins.support.SupportLogFormatter.format(SupportLogFormatter.java:89)at java.util.logging.StreamHandler.publish(StreamHandler.java:211)- locked <0x0006c394e130> (a java.util.logging.StreamHandler)at com.cloudbees.jenkins.support.impl.JenkinsLogs$LogFile.publish(JenkinsLogs.java:544)at com.cloudbees.jenkins.support.impl.JenkinsLogs$CustomHandler.publish(JenkinsLogs.java:583)at java.util.logging.Logger.log(Logger.java:738)at java.util.logging.Logger.doLog(Logger.java:765)at java.util.logging.Logger.log(Logger.java:830)at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1.onSuccess(FlowExecutionList.java:177){noformat}I believe the issue is that the [StepExecution.toString|https://github.com/jenkinsci/workflow-step-api-plugin/blob/99a0704aa7b2fed962b4a434d122bcf8dc7158af/src/main/java/org/jenkinsci/plugins/workflow/steps/StepExecution.java#L98] make a call to {{getStatus}} which if it is currently in a
[JIRA] (JENKINS-39275) StepExecution tostring hangs
Title: Message Title Steven Christou assigned an issue to Unassigned Jenkins / JENKINS-39275 StepExecution tostring hangs Change By: Steven Christou Assignee: Steven Christou 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-39275) StepExecution tostring hangs
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-39275 StepExecution tostring hangs Change By: Steven Christou Component/s: support-core-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-39275) StepExecution tostring hangs
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-39275 StepExecution tostring hangs Issue Type: Bug Assignee: Steven Christou Components: support-core-plugin, workflow-step-api-plugin Created: 2016/Oct/26 7:05 PM Priority: Minor Reporter: Steven Christou There is some improvements to be made in the support core plugin (will create a different ticket), but there is a case where the pipeline step executions toString method can hang forever if it is unable to obtain the durable task steps workspace: "Running CpsFlowExecution[Owner[JOB_NAME:JOB_NAME#BUILD_NUMBER]] / waiting for hudson.remoting.Channel@1:NODE_NAME" #1 daemon prio=5 os_prio=0 tid=0x2e00d800 nid=0x4a8 in Object.wait() [0x2f5de000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:147) - locked <0x0007b795ff98> (a hudson.remoting.UserRequest) at hudson.remoting.Channel.call(Channel.java:780) at hudson.FilePath.act(FilePath.java:979) at hudson.FilePath.act(FilePath.java:968) at hudson.FilePath.isDirectory(FilePath.java:1504) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.getWorkspace(DurableTaskStep.java:108) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.getStatus(DurableTaskStep.java:153) at org.jenkinsci.plugins.workflow.steps.StepExecution.toString(StepExecution.java:98) at java.lang.String.valueOf(String.java:2994) at java.lang.StringBuilder.append(StringBuilder.java:131) at java.util.AbstractCollection.toString(AbstractCollection.java:462) at java.util.Collections$UnmodifiableCollection.toString(Collections.java:1035) at
[JIRA] (JENKINS-30823) Exception in thread "Channel reader thread: " java.lang.OutOfMemoryError: Java heap space
Title: Message Title Steven Christou assigned an issue to Unassigned Jenkins / JENKINS-30823 Exception in thread "Channel reader thread: " java.lang.OutOfMemoryError: Java heap space Change By: Steven Christou Assignee: Steven Christou 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-38572) Support Core Plugin gets java.lang.NoClassDefFoundError: jenkins/plugins/asynchttpclient/AHCUtils at startup
Title: Message Title Steven Christou updated JENKINS-38572 Jenkins / JENKINS-38572 Support Core Plugin gets java.lang.NoClassDefFoundError: jenkins/plugins/asynchttpclient/AHCUtils at startup Change By: Steven Christou 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-38572) Support Core Plugin gets java.lang.NoClassDefFoundError: jenkins/plugins/asynchttpclient/AHCUtils at startup
Title: Message Title Steven Christou started work on JENKINS-38572 Change By: Steven Christou 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-38572) Support Core Plugin gets java.lang.NoClassDefFoundError: jenkins/plugins/asynchttpclient/AHCUtils at startup
Title: Message Title Steven Christou commented on JENKINS-38572 Re: Support Core Plugin gets java.lang.NoClassDefFoundError: jenkins/plugins/asynchttpclient/AHCUtils at startup Ok, I created https://github.com/jenkinsci/support-core-plugin/pull/76. 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-38572) Support Core Plugin gets java.lang.NoClassDefFoundError: jenkins/plugins/asynchttpclient/AHCUtils at startup
Title: Message Title Steven Christou commented on JENKINS-38572 Re: Support Core Plugin gets java.lang.NoClassDefFoundError: jenkins/plugins/asynchttpclient/AHCUtils at startup Ops, I'm sorry. I'll fix this ASAP. 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-35364) java.lang.NoClassDefFoundError if rabbitmq-consumer plugin is not installed
Title: Message Title Steven Christou resolved as Fixed Fixed in version 2.21.1: https://github.com/jenkinsci/gerrit-trigger-plugin/commit/33957ae997ed2cb7e6a491c113395b5a9d1b0d46. Jenkins / JENKINS-35364 java.lang.NoClassDefFoundError if rabbitmq-consumer plugin is not installed Change By: Steven Christou 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
[JIRA] (JENKINS-25333) Jenkins 1.586 not starting up using Java8
Title: Message Title
Steven Christou updated an issue
Jenkins / JENKINS-25333
Jenkins 1.586 not starting up using Java8
Change By:
Steven Christou
Using Java8, Jenkins doesn't start with the following message: {noformat} SCHWERWIEGEND: Container startup failedjava.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.(Launcher.java:149) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at Main._main(Main.java:293) at Main.main(Main.java:98)Caused by: java.lang.NoClassDefFoundError: sun/security/x509/CertAndKeyGen at winstone.HttpsConnectorFactory.start(HttpsConnectorFactory.java:101) at winstone.Launcher.spawnListener(Launcher.java:207) ... 8 moreCaused by: java.lang.ClassNotFoundException: sun.security.x509.CertAndKeyGen at java.net.URLClassLoader$1.run(URLClassLoader.java:372) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:360) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 10 more {noformat} After switching back to Oracle Java 7, it works without problems.
Add Comment
[JIRA] (JENKINS-25333) Jenkins 1.586 not starting up using Java8
Title: Message Title Steven Christou commented on JENKINS-25333 Re: Jenkins 1.586 not starting up using Java8 Daniel Beck Maybe it's best to remove this functionality from Winstone. My PR was just to give us some time before removing it completely. The fix I provided won't work with JDK 9, so this might give us a few months(years?) to suggest to avoid using the built-in cert generation and use a valid one before everyone starts using JDK 9 heavily. I could also provide an error on startup suggesting everyone switch to using an outside certificate instead. 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-33400) How to create a log file in the local computer showing only the build status and erros(Jenkins).
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-33400 How to create a log file in the local computer showing only the build status and erros(Jenkins). Change By: Steven Christou Component/s: support-core-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-37354) Add description field when generating a new bundle
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-37354 Add description field when generating a new bundle Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 2016/Aug/11 4:52 PM Priority: Minor Reporter: Steven Christou Adding a description field of the reason why the support bundle was generated would be nice. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37103) Job DSL documentation broken
Title: Message Title
Steven Christou updated an issue
Jenkins / JENKINS-37103
Job DSL documentation broken
Change By:
Steven Christou
About:Jenkins ver. 1.651.3 .1 (CloudBees Jenkins Enterprise 16.06) job-dsl:1.48Steps:* Load attached job (config.xml)* From job page, click "Job DSL API Reference"Stack trace thrown:{code}Error while serving http://jenkins/plugin/job-dsl/api-viewer/build/data/update-center.jsonpjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:403) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) 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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at com.cloudbees.jenkins.ha.HAHealthCheckFilter.doFilter(HAHealthCheckFilter.java:35) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:38) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter._doFilter(OfflineSecurityRealmFilter.java:90) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter.doFilter(OfflineSecurityRealmFilter.java:67) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.cloudbees.opscenter.security.ClusterSessionFilter._doFilter(ClusterSessionFilter.java:69) at com.cloudbees.opscenter.security.ClusterSessionFilter.doFilter(ClusterSessionFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at
[JIRA] (JENKINS-37103) Job DSL documentation broken
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-37103 Job DSL documentation broken Change By: Steven Christou Summary: Job DSL documentation broken in CJE 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-36929) Add the version of protocols used by connectors
Title: Message Title Steven Christou assigned an issue to Steven Christou Jenkins / JENKINS-36929 Add the version of protocols used by connectors Change By: Steven Christou Assignee: Steve Nicolai Steven Christou 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-36929) Add the version of protocols used by connectors
Title: Message Title Steven Christou assigned an issue to Steve Nicolai Jenkins / JENKINS-36929 Add the version of protocols used by connectors Change By: Steven Christou Assignee: Steven Christou Steve Nicolai 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-34722) Unbounded searches with BuildUtil.getDownstreamBuild
Title: Message Title Steven Christou commented on JENKINS-34722 Re: Unbounded searches with BuildUtil.getDownstreamBuild Dilip M How many builds are currently in your pipeline view, and how many pipelines are you currently displaying? A large part of the performance issue also revolves around the number of pipeline runs that are being displayed. 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] [docker-plugin] (JENKINS-35033) Support for binding of port ranges
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-35033 Support for binding of port ranges Change By: Steven Christou Recently the docker-java library merged [PR 575 ]( | https://github.com/docker-java/docker-java/pull/575 ) ] which allowed for binding of ports on multiple addresses. Currently I have only been able to bind to one port. When the new release of the docker-java library is released we should support the ability of binding to multiple port ranges. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-plugin] (JENKINS-35033) Support for binding of port ranges
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-35033 Support for binding of port ranges Issue Type: New Feature Assignee: magnayn Components: docker-plugin Created: 2016/May/23 5:00 PM Priority: Minor Reporter: Steven Christou Recently the docker-java library merged [PR 575](https://github.com/docker-java/docker-java/pull/575) which allowed for binding of ports on multiple addresses. Currently I have only been able to bind to one port. When the new release of the docker-java library is released we should support the ability of binding to multiple port ranges. Add Comment
[JIRA] [ircbot-plugin] (JENKINS-28175) config change deadlock Jenkins when pircx.shutdown() is invoked
Title: Message Title Steven Christou commented on JENKINS-28175 Re: config change deadlock Jenkins when pircx.shutdown() is invoked Please make sure to update to the latest version of the ircbot plugin which uses 2.1 of the pircbotx plugin. If this does not solve your issue, then please re-attach a new thread dump to diagnose the deadlock. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-pipeline-plugin] (JENKINS-34722) Unbounded searches with BuildUtil.getDownstreamBuild
Title: Message Title Steven Christou assigned an issue to Steven Christou Jenkins / JENKINS-34722 Unbounded searches with BuildUtil.getDownstreamBuild Change By: Steven Christou Assignee: Steven Christou Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-34636) Get tomcat logs
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-34636 Get tomcat logs Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 2016/May/05 10:26 PM Priority: Minor Reporter: Steven Christou It would be nice for the support core plugin to request adding the catalina.log files if it is in a tomcat container. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [active-directory-plugin] (JENKINS-34426) Changing project-based settings for AD-Groups shows error
Title: Message Title Steven Christou commented on JENKINS-34426 Re: Changing project-based settings for AD-Groups shows error It looks like the issue is there are two locations where the UserCache is being obtained: https://github.com/jenkinsci/active-directory-plugin/blob/876a05dd49789008f5de89f742a68bbcd83e681d/src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java#L302 and https://github.com/jenkinsci/active-directory-plugin/blob/876a05dd49789008f5de89f742a68bbcd83e681d/src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java#L136 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-18032) "Delete Project" link fails with 403 Exception: No valid crumb was included in the request
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-18032 "Delete Project" link fails with 403 Exception: No valid crumb was included in the request Change By: Steven Christou Labels: 1.509.3-fixed 2.0-planned crumb lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-31952) Dockerfile: cloudbees/jenkins needs to be cloudbees/jenkins-enterprise
Title: Message Title Steven Christou reopened an issue Jenkins / JENKINS-31952 Dockerfile: cloudbees/jenkins needs to be cloudbees/jenkins-enterprise Change By: Steven Christou Resolution: Won't Fix Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [monitoring-plugin] (JENKINS-31619) java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N
Title: Message Title Steven Christou commented on JENKINS-31619 Re: java.lang.NoClassDefFoundError: Could not initialize class net.bull.javamelody.I18N Tomasz Śniatowski I am wondering if this is caused by the monitoring plugin, and the monitoring jar having the same package path which might confuse the classloader. Potentially fixed by forcing the binaries location: https://github.com/christ66/monitoring-plugin/commit/df81844f763ee416ffe445ad8552d158e62f0db3. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-33628) Support bundle corrupt via UI
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-33628 Support bundle corrupt via UI Issue Type: Bug Assignee: Steven Christou Components: support-core-plugin Created: 2016/Mar/17 4:21 PM Priority: Critical Reporter: Steven Christou Some users who generate a support bundle via the UI run into issues where the content of the bundle get corrupt. Unfortunately there is not much logging in the logs to determine what could have potentially caused this issue. The support bundle contents usually stop after the browser.md is generated. Doing a quick test locally, the about.md content is next to be generated: Writing file: nodes/slave/test/logs/all_2016-03-11_05.59.17.log to the support bundle. Writing file: nodes/slave/test/logs/all_2016-03-11_06.02.04.log to the support bundle. Writing file: browser.md to the support bundle. Writing file: about.md to the support bundle. however the about.md content is never generated.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title
Steven Christou edited a comment on JENKINS-33467
Re: CauseAction.causes can become huge
I marked this as an {{lts-candidate}}, as this can cause memory issues and lots of disk I/O .
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Steven Christou commented on JENKINS-33467 Re: CauseAction.causes can become huge I marked this as an lts-candidate, as this can cause memory issues. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-33467 CauseAction.causes can become huge Change By: Steven Christou Labels: lts-candidate performance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-26409) ClientAbortException logged when cancelling a support bundle download
Title: Message Title Steven Christou reopened an issue Félix Belzunce Arcos The support bundle logs this error message still: WARNING c.c.j.support.SupportAction#doDownload: java.io.IOException: Broken pipe org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:393) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:426) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:342) at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:317) at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:110) at net.bull.javamelody.FilterServletOutputStream.flush(FilterServletOutputStream.java:65) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:374) If this message should be removed it should be removed from: SupportAction.java#L171 instead of closing the stream. Jenkins / JENKINS-26409 ClientAbortException logged when cancelling a support bundle download Change By: Steven Christou Resolution: Fixed Status: Resolved Reopened Add Comment
[JIRA] [support-core-plugin] (JENKINS-31952) Dockerfile: cloudbees/jenkins needs to be cloudbees/jenkins-enterprise
Title: Message Title Steven Christou closed an issue as Won't Fix Please log this in the cloudbees jira as this is a cloudbees specific issue. Jenkins / JENKINS-31952 Dockerfile: cloudbees/jenkins needs to be cloudbees/jenkins-enterprise Change By: Steven Christou Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-32265) Add Launcher.VERSION to Version Details
Title: Message Title Steven Christou resolved as Fixed Jenkins / JENKINS-32265 Add Launcher.VERSION to Version Details Change By: Steven Christou Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-33394) Generate support bundle before providing download
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-33394 Generate support bundle before providing download Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 08/Mar/16 3:43 PM Priority: Minor Reporter: Steven Christou Users have found that the support core plugin can be corrupted which causes some issues while generating a support bundle. The support core plugin should generate a new bundle and place it in disk, then make the support bundle available through download (2 buttons where you click "Generate", and "Download"). This would make for less corrupt support bundles and much faster download speeds for support bundles as it only needs to go on disk and get the support bundle vs potentially waiting a very long time which can also hit timeouts Add Comment
[JIRA] [categorized-view-plugin] (JENKINS-32071) Slow Performance with Category View Plugin
Title: Message Title
Steven Christou updated an issue
Jenkins / JENKINS-32071
Slow Performance with Category View Plugin
Change By:
Steven Christou
Issue seems to be related to to AbstractLazyLoadRunMap blocking when categorised view is used. This is causing Jenkins to backup while waiting for unblock. Causing page load times to slow down.Logs:{code}2015-12-15_03:16:10.77157 "Handling GET /job/MyJob/ : http-8082-1 View/index.jelly StatusColumn/column.jelly" #17 daemon prio=5 os_prio=0 tid=0x7f236c004800 nid=0x7b79 waiting for monitor entry [0x7f239951b000]2015-12-15_03:16:10.77158java.lang.Thread.State: BLOCKED (on object monitor)2015-12-15_03:16:10.77158 at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:465)2015-12-15_03:16:10.77159 - waiting to lock <0xde0dee38> (a hudson.model.RunMap)2015-12-15_03:16:10.77159 at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:448)2015-12-15_03:16:10.77160 at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:356)2015-12-15_03:16:10.77161 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:332)2015-12-15_03:16:10.77161 at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:274)2015-12-15_03:16:10.77162 at jenkins.model.lazy.LazyBuildMixIn.getLastBuild(LazyBuildMixIn.java:240)2015-12-15_03:16:10.77164 at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:985)2015-12-15_03:16:10.77165 at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:144)2015-12-15_03:16:10.77166 at hudson.model.Job.getIconColor(Job.java:1053)2015-12-15_03:16:10.77166 at hudson.model.AbstractProject.getIconColor(AbstractProject.java:738)2015-12-15_03:16:10.77167 at org.jenkinsci.plugins.categorizedview.GroupTopLevelItem.getIconColor(GroupTopLevelItem.java:87){code}Cause on last line.To reproduce: * 100+ build history* Slow Disk (not sure how to apply this to a test at the moment)Plugin: categorized-view:1.8Jenkins: 1.609 .4.6
Add Comment
[JIRA] [awseb-deployment-plugin] (JENKINS-32952) Credentials inside folders do not show up properly
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-32952 Credentials inside folders do not show up properly Issue Type: Bug Assignee: Unassigned Components: awseb-deployment-plugin Created: 15/Feb/16 3:32 PM Priority: Minor Reporter: Steven Christou If you put credentials inside of a folder, and use them in the job configuration page it will produce the error: Failure javax.security.auth.login.CredentialNotFoundException: CREDENTIAL_HASH_VALUE at br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSClientFactory.lookupNamedCredential(AWSClientFactory.java:105) at br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSClientFactory.getClientFactory(AWSClientFactory.java:86) at br.com.ingenieux.jenkins.plugins.awsebdeployment.AWSEBDeploymentBuilder$DescriptorImpl.doValidateCredentials(AWSEBDeploymentBuilder.java:285) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) If you trigger a new build with those same credentials it throws the error:
[JIRA] [groovy-postbuild-plugin] (JENKINS-32681) Option to disable script security approval
Title: Message Title
Steven Christou commented on JENKINS-32681
Re: Option to disable script security approval
The sandbox approval does not work with the Overall\RunScript permission. It still posts a request to have the script approved:
Sandbox mode:
Groovy script failed: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder$BadgeManager getHudson at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:150)
Non-Sanbox mode:
ERROR: Failed to evaluate groovy script. org.jenkinsci.plugins.scriptsecurity.scripts.UnapprovedUsageException: script not yet approved for use at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.using(ScriptApproval.java:428) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:166) at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:362)
The title of this should most likely be switched to allow for Overall\RunScript to work with the groovy postbuild plugin.
Can be reproduced by having the groovy script manager.hudson.getItemByFullName("JOBNAME");
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [groovy-postbuild-plugin] (JENKINS-32681) Option to disable script security approval
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-32681 Option to disable script security approval Issue Type: Improvement Assignee: wolfs Components: groovy-postbuild-plugin, script-security-plugin Created: 28/Jan/16 10:51 PM Priority: Trivial Reporter: Steven Christou It would be nice to have an option in Manage Jenkins -> Configure Security to disable the need for approval process for the groovy-postbuild plugin. By default the script security plugin is enabled and with no method for disabling, or ignoring an entire project. Add Comment
[JIRA] [cli] (JENKINS-32622) deadlock due to support-core use of classloading during logging
Title: Message Title Steven Christou resolved as Fixed Jenkins / JENKINS-32622 deadlock due to support-core use of classloading during logging Change By: Steven Christou Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-25048) Git plugin ignores included/excluded paths when triggering build on commit nitification
Title: Message Title Steven Christou commented on JENKINS-25048 Re: Git plugin ignores included/excluded paths when triggering build on commit nitification Mark Waite Was this fixed in https://github.com/jenkinsci/git-plugin/commit/dae26dc8d01bd457aa84fdbcdb755c7fdbc5458f? It might be fixed, but a PR was never created for it. It looks like this PR also has no associating branch. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30914) Add more log information when build is stuck in Queue
Title: Message Title Steven Christou assigned an issue to Steven Christou Jenkins / JENKINS-30914 Add more log information when build is stuck in Queue Change By: Steven Christou Assignee: Steven Christou Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30914) Add more log information when build is stuck in Queue
Title: Message Title Steven Christou resolved as Fixed Jenkins / JENKINS-30914 Add more log information when build is stuck in Queue Change By: Steven Christou Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [statusmonitor-plugin] (JENKINS-32223) Compatibility with folders plugin
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-32223 Compatibility with folders plugin Issue Type: New Feature Assignee: danielgalan Components: statusmonitor-plugin Created: 29/Dec/15 10:38 PM Priority: Minor Reporter: Steven Christou Currently the status monitor plugin only provides a list of jobs at the root folder instead of providing status on any of the subfolders also. It would be nice for the status monitor plugin to iterate through each folder to provide a status on the subfolder jobs also. Add Comment
[JIRA] [statusmonitor-plugin] (JENKINS-32223) Compatibility with folders plugin
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-32223 Compatibility with folders plugin Change By: Steven Christou Currently the status monitor plugin only provides a the list of jobs at the root folder level instead of providing status on any of the subfolders also jobs within a folder . It would be nice for I setup the status monitor plugin to iterate through each folder to provide a status on have the subfolder status monitor postbuild action, however it still only shows top level folder jobs also . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-30117) Support bundle blocks with lots of log data
Title: Message Title Steven Christou resolved as Fixed Fixed in 2.29. Jenkins / JENKINS-30117 Support bundle blocks with lots of log data Change By: Steven Christou Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31915) Proxy settings in plugins page are ignored
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-31915 Proxy settings in plugins page are ignored Issue Type: Bug Assignee: Unassigned Components: core Created: 04/Dec/15 11:48 PM Environment: Jenkins latest + reverse proxy Priority: Minor Reporter: Steven Christou If you setup a Jenkins instance behind a proxy, the configuration from Manage Jenkins > Manage Plugins > Advanced tab are ignored and are not correctly being used. The documentation in the proxy configuration help option states: The value you submit here will be set as http.proxyHost system property. Looking quickly at the source code I was unable to locate references to the http.proxyHost property being set. I was able to workaround the issue by setting up the proxy settings manually via the startup arguments: -Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttp.nonProxyHosts=
[JIRA] [support-core-plugin] (JENKINS-31820) Limit size of support bundles or split the support bundles after a provided size limit
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-31820 Limit size of support bundles or split the support bundles after a provided size limit Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 01/Dec/15 9:00 AM Priority: Minor Reporter: Steven Christou The support core plugin should be able to either truncate the .zip file, or split the zip file into multiple parts. A JVM argument, or a static configurable environment variable would be best for configuring this information. Add Comment
[JIRA] [support-core-plugin] (JENKINS-28216) Obtaining slave log records blocks channel
Title: Message Title Steven Christou resolved as Fixed Fixed and will be made available in the next release. Jenkins / JENKINS-28216 Obtaining slave log records blocks channel Change By: Steven Christou Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-28216) Obtaining slave log records blocks channel
Title: Message Title Steven Christou started work on JENKINS-28216 Change By: Steven Christou Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-31160) Update Jenkins UI not to call everything a "Build"
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-31160 Update Jenkins UI not to call everything a "Build" Change By: Steven Christou Jenkins (core, plugins, etc.) has a tendency to call everything a "build". These days, "build" tends to conjure thoughts of Continuous Integration use cases only. In fact, our very own [~ uaarkoti uday ] wrote a [plugin so users could change the "build now" button|https://wiki.jenkins-ci.org/display/JENKINS/Customize+Build+Now+Plugin] to "deploy now" (or whatever his customer's heart desired). There are many other areas in Jenkins where the notion of "build" is the default. This RFE requests updating them to a more fashionable term. It seems there are two options:* Jenkins either needs to be "smarter" to know there are different types of things (eg: Build Job, Test Job, Deploy Job, Pipeline)* Or we need a more acceptable generic word than "build" (since it seems less fashionably to point at CI use cases specifically) - eg: everything is a "job" (job history, job queue, and so on)Quick List of Build References:* Global: Build History* Global: Build Queue* Global: Build Executor Status* Job: Discard Old Builds* Job: Build Now* Job: Build with Parameters* Job: Skip Builds* Job: Build History* Job: Last build* Job: Last failed build* Job: Last unsuccessful build* Job: Show Consolidated Build View* Job: This build is parameterized* Job: Promote builds when...* Job: Disable Build* Job: Execute concurrent builds* Job: Build Triggers: ** Job: Build Environment: ** Job: Build Steps: ** Job: Post-build Actions: ** Jenkins Analytics: BUILDS PER MASTER* Jenkins Analytics: BUILDSrelates to JENKINS-7628 but that ticket was closed with "Not a Bug" resolution. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [subversion-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Title: Message Title Steven Christou commented on JENKINS-26612 Re: svn: absolutely unacceptably SLOW The problem is not specific to the subversion plugin, but the svnkit library (https://issues.tmatesoft.com/issue/SVNKIT-553). I did a lot of profiling for this issue. The issue is that for each file that is committed there are several sql query operations being done in SVNCancellableEditor.closeFile. Performing a "closeFile" operation create 3 sql queries against the sqljet engine this I believe causes the performance issue. I'm not sure if this is specific to how large the repository is vs the number of files/folders that exist in the repository, but it's easily reproducible if you perform a checkout of a repository that's over several MB large, and contains a lot of files/folders. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [deploy-websphere-plugin] (JENKINS-31338) Deployment Sphere Plugin - Unable to determine URL for classpath location: db/migration
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-31338 Deployment Sphere Plugin - Unable to determine URL for classpath location: db/migration Change By: Steven Christou Environment: * Version: ` Jenkins 1.609.1 .1 (CloudBees Jenkins Enterprise 15.05)` * Mode:Webapp Directory * Servlet container - Specification: 3.1 - Name: `Apache Tomcat/8.0.24`* Operating system - Name: Linux - Architecture: amd64 - Version: 2.6.32-504.el6.x86_64 - Distribution: "Red Hat Enterprise Linux Server release 6.6 (Santiago)" - LSB Modules: `:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch`* Java - Vendor: Oracle Corporation - Version: 1.8.0_45 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [deploy-websphere-plugin] (JENKINS-31338) Deployment Sphere Plugin - Unable to determine URL for classpath location: db/migration
Title: Message Title Steven Christou commented on JENKINS-31338 Re: Deployment Sphere Plugin - Unable to determine URL for classpath location: db/migration This error message could be happening because the db/migration folder was not properly packaged when the hpi file was created: https://github.com/jenkinsci/deployment-sphere-plugin/tree/9c376f6031deb3949b035f9512b061a7e7ba8cb8/plugin/src/main/resources/db/migration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-31360) Permgen leak with SimpleXStreamFlowNodeStorage
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-31360 Permgen leak with SimpleXStreamFlowNodeStorage Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 02/Nov/15 10:28 PM Priority: Major Reporter: Steven Christou The workflow plugin can potentially cause a permgen leak if the SimpleXStreamFlowNodeStorage has a lot of flow nodes. Unfortunately I have not been able to reproduce this issue locally. Stack track: java.lang.String.intern(Native Method) org.xmlpull.mxp1.MXParserCachingStrings.newStringIntern(MXParserCachingStrings.java:317) org.xmlpull.mxp1.MXParserCachingStrings.newString(MXParserCachingStrings.java:287) org.xmlpull.mxp1.MXParser.parseStartTag(MXParser.java:1779) org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1127) org.xmlpull.mxp1.MXParser.next(MXParser.java:1093) com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:109) com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148) com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:135) com.thoughtworks.xstream.io.xml.AbstractPullReader.hasMoreChildren(AbstractPullReader.java:87) com.thoughtworks.xstream.io.ReaderWrapper.hasMoreChildren(ReaderWrapper.java:32) hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:267) hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:228)
[JIRA] [blamesubversion-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
Title: Message Title Steven Christou commented on JENKINS-26318 Re: Subversion Plug in 2.5 causes sporadic problems I created PR 1 a while ago to provide compatibility with the blame subversion plugin, and svnkit 1.8. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [maven-plugin] (JENKINS-26021) xunit published results don't show up or hides maven test results in maven projects
Title: Message Title Steven Christou commented on JENKINS-26021 Re: xunit published results don't show up or hides maven test results in maven projects This is also an issue for post-build steps too. If your maven project type and you have unit tests it will only display the ones from the maven build and ignore the one from the junit plugin. Checking the junitReport.xml file the content is properly being handled, but it does not display the results. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-25550) Hard kill
Title: Message Title
Steven Christou commented on JENKINS-25550
Re: Hard kill
Jesse Glick The workaround works. You need to specify a throwable for the finish method.
Jenkins.instance.getItemByFullName("jobName").getBuildByNumber(9).finish(hudson.model.Result.ABORTED, new java.io.IOException("Aborting build");
This will free up the executor on the master/slave machine and new builds can run on the machine, but the build shows up as still executing in the jobs page.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-29902) Unexpected executor death - java.lang.IllegalStateException: already existed
Title: Message Title Steven Christou commented on JENKINS-29902 Re: Unexpected executor death - java.lang.IllegalStateException: already existed I was able to reproduce this issue by changing the nextBuildNumber on disk from a valid number to a number which already has an associating build. Steps to reproduce: 1. Trigger multiple builds (5 builds) 2. Change the JENKINS_HOME/job/JOBNAME/nextBuildNumber to one of the build numbers with an associating build (like 1), or remove the nextBuildNumber file. 3. Restart Jenkins 4. The UI will show correct information, however when triggering a new build the executor will throw the same exception. Only workaround I know of is to change the nextBuildNumber to a valid build number. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [packer-plugin] (JENKINS-30945) Unable to install from packer site
Title: Message Title Steven Christou commented on JENKINS-30945 Re: Unable to install from packer site Ahmed Mostafa I believe this issue was fixed in INFRA-376. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30914) Add more log information when build is stuck in Queue
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-30914 Add more log information when build is stuck in Queue Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Oct/15 12:06 AM Priority: Major Reporter: Steven Christou I would like to add more logging information to the build queue in the even a build is stuck and the job is not executing. Add Comment This message
[JIRA] [support-core-plugin] (JENKINS-24814) Bundle rotated slave launch logs
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-24814 Bundle rotated slave launch logs Change By: Steven Christou Summary: Bundle rorated rotated slave launch logs Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [support-core-plugin] (JENKINS-30816) Allow for customizing JENKINS_HOME/logs/custom size
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-30816 Allow for customizing JENKINS_HOME/logs/custom size Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 06/Oct/15 7:18 PM Priority: Trivial Reporter: Steven Christou Currently the support core plugin records custom loggers to the file system, however it would be nice to allow users to customize the size (via JVM argument). https://github.com/jenkinsci/support-core-plugin/blob/5edc573e45457dd79b8e07594bc24f5921606ef2/src/main/java/com/cloudbees/jenkins/support/impl/JenkinsLogs.java#L70 would need to be fixed to use FileListCapComponent.MAX_FILE_SIZE Add Comment
[JIRA] [subversion-plugin] (JENKINS-30774) Subversion parameterized build throws error in job configuration
Title: Message Title Steven Christou edited a comment on JENKINS-30774 Re: Subversion parameterized build throws error in job configuration [~recena] that sounds good. The current error message (and huge stack trace generated) can be a little misleading confusing . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-30774) Subversion parameterized build throws error in job configuration
Title: Message Title Steven Christou commented on JENKINS-30774 Re: Subversion parameterized build throws error in job configuration Manuel Jesús Recena Soto that sounds good. The current error message (and huge stack trace generated) can be a little misleading. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-30774) Subversion parameterized build throws error in job configuration
Title: Message Title
Steven Christou created an issue
Jenkins / JENKINS-30774
Subversion parameterized build throws error in job configuration
Issue Type:
Improvement
Assignee:
Steven Christou
Components:
subversion-plugin
Created:
02/Oct/15 6:40 PM
Priority:
Minor
Reporter:
Steven Christou
If you configure the subversion plugin to use a parameterized build, and use the parameterized build in the URL part it will throw an error claiming an authentication error.
Example URL:
http://SVNURL.com/svn/$RELEASE
Instead we should remove any parameterized environment variables in the URL (or anything with
$
or
${}
[JIRA] [xunit-plugin] (JENKINS-30710) xUnit plugin to do case insensitive xsd validation
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-30710 xUnit plugin to do case insensitive xsd validation Issue Type: Improvement Assignee: Gregory Boissinot Components: xunit-plugin Created: 29/Sep/15 11:20 PM Priority: Minor Reporter: Steven Christou The current xUnit plugin does not properly handle a situation where if the attributes from the xsd are case insensitive. The timestamp as an example could be timeStamp which would cause the output file to fail to properly format: Recording test results [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing JUnit [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'TEST1.xml' relative to '/private/tmp' for the testing framework 'JUnit'. [xUnit] [ERROR] - The result file '/private/tmp/TEST1.xml' for the metric 'JUnit' is not valid. The result file has been skipped. [xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated. [xUnit] [INFO] - There are errors when processing test results. [xUnit] [INFO] - Skipping tests recording. [xUnit] [INFO] - Stop build. Build step 'Publish xUnit test result report' changed build result to FAILURE There is room for improvement in that the libdtkit can have a validation where case insensitive searching is available (see ValidationService.java for more information).
[JIRA] [workflow-plugin] (JENKINS-30651) File descriptor leak when invoking for-loop
Title: Message Title
Steven Christou created an issue
Jenkins / JENKINS-30651
File descriptor leak when invoking for-loop
Issue Type:
Bug
Assignee:
Jesse Glick
Attachments:
fd.txt
Components:
workflow-plugin
Created:
25/Sep/15 6:19 PM
Priority:
Minor
Reporter:
Steven Christou
Steps to reproduce:
Create a workflow job with the following:
stage 'all'
for (int i = 0; i < ; i++) {
echo "running #${i}"
}
Expected output: "running #0" to "running #9998"
Actual output: After 7940 the build will freeze, and the System.out will show:
After upgrading to 1.7 I see the exception earlier on:
Aug 14, 2015 9:03:37 PM org.jenkinsci.plugins.workflow.graph.FlowNode$1 persist
WARNING: failed to save actions for FlowNode id=7945
java.io.IOException: Failed to create a temporary file in
[JIRA] [run-condition-plugin] (JENKINS-30654) Several run conditional steps causes long configuration load times
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-30654 Several run conditional steps causes long configuration load times Issue Type: Bug Assignee: bap Attachments: screenshot.png Components: run-condition-plugin Created: 26/Sep/15 12:12 AM Priority: Minor Reporter: Steven Christou For each run conditional that is added to the configuration page the load time almost comes at an n^2 cost. The reason for this is because for each run conditional that is added to the list in the job configuration screen is re-drawn in order to properly handle the spacing of each element on the screen. With a run conditional of 40 the job configuration page takes about 20 minutes to load! Screenshot.png is an example where I added multiple run conditionals and it took over 20 minutes to load because of the number of re-draws that needed to be executed.
[JIRA] [core] (JENKINS-30456) Executables.getEstimatedDurationFor() throws NPE when argument is null
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-30456 Executables.getEstimatedDurationFor() throws NPE when argument is null Change By: Steven Christou Component/s: mansion-cloud-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30456) Executables.getEstimatedDurationFor() throws NPE when argument is null
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-30456 Executables.getEstimatedDurationFor() throws NPE when argument is null Change By: Steven Christou Environment: CloudBees DEV@cloud 1.609.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [artifactory-plugin] (JENKINS-20119) Job configuration pages not loading when Artifactory server is down
Title: Message Title Steven Christou resolved as Fixed This issue has already been fixed as part of PR 11 and is available in 2.2.5 of the artifactory plugin. Jenkins / JENKINS-20119 Job configuration pages not loading when Artifactory server is down Change By: Steven Christou Status: Open Resolved Assignee: yossis Steven Christou Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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
[JIRA] [support-core-plugin] (JENKINS-30117) Support bundle blocks with lots of log data
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-30117 Support bundle blocks with lots of log data Issue Type: Bug Assignee: Steven Christou Components: support-core-plugin Created: 24/Aug/15 9:18 PM Priority: Critical Reporter: Steven Christou The SupportLogFormatter.format could potential cause a performance issue if there is lots of log information being printed. I have only seen this issue happen if the log content is over 16MB in size, or lots of log data is being sent. Thread dumps Blocking thread: Thread 15139: (state = IN_VM) - java.lang.Throwable.fillInStackTrace(int) @bci=0 (Compiled frame; information may be imprecise) - java.lang.Throwable.fillInStackTrace() @bci=16, line=782 (Compiled frame) - java.lang.Throwable.init() @bci=24, line=250 (Compiled frame) - java.util.logging.LogRecord.inferCaller() @bci=13, line=528 (Compiled frame) - java.util.logging.LogRecord.getSourceMethodName() @bci=8, line=336 (Compiled frame) - com.cloudbees.jenkins.support.SupportLogFormatter.format(java.util.logging.LogRecord) @bci=73, line=55 (Compiled frame) - java.util.logging.StreamHandler.publish(java.util.logging.LogRecord) @bci=14, line=196 (Compiled frame) - com.cloudbees.jenkins.support.impl.JenkinsLogs$LogFile.publish(java.util.logging.LogRecord) @bci=58, line=497 (Compiled frame) -
[JIRA] [git-parameter-plugin] (JENKINS-23473) empty tags / revisions list when using Folders - NullPointerException - getParentProject()
Title: Message Title Steven Christou resolved as Fixed This issue was fixed by Nicolas De Loof in 92971c Jenkins / JENKINS-23473 empty tags / revisions list when using Folders - NullPointerException - getParentProject() Change By: Steven Christou Status: Open Resolved Assignee: NiklausGiger NicolasDeLoof Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [envinject-plugin] (JENKINS-27382) EnvInject plugin passes astrisk to Gradle plugin
Title: Message Title Steven Christou commented on JENKINS-27382 Re: EnvInject plugin passes astrisk to Gradle plugin I believe this is a regression from commit d50c5. I did a git checkout for each commit between 1.90, and 1.91, and found this commit to inject the * characters. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Title: Message Title
Steven Christou resolved as Fixed
Again marking this issue as solved. The initial fix for this was the parameterized build not obtaining the proper environment variables while polling. The envinject plugin version of this issue can be found in JENKINS-22922.
Jenkins / JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Change By:
Steven Christou
Status:
Reopened Resolved
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [disk-usage-plugin] (JENKINS-24182) Disk Usage plugin throws NullPointerException preventing Maven jobs from loading
Title: Message Title Steven Christou resolved as Fixed Jenkins / JENKINS-24182 Disk Usage plugin throws NullPointerException preventing Maven jobs from loading Change By: Steven Christou Status: InProgress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mansion-cloud-plugin] (JENKINS-29751) unkillable workflow builds with mansion cloud plugin
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-29751 unkillable workflow builds with mansion cloud plugin Change By: Steven Christou Environment: workflow1.9-beta1,jenkins1.609.1(Dev@Cloud) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gradle-plugin] (JENKINS-12769) Cannot specify location of gradle wrapper
Title: Message Title Steven Christou commented on JENKINS-12769 Re: Cannot specify location of gradle wrapper Gregory Boissinot Sorry, I just found it: PR 13 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gradle-plugin] (JENKINS-12769) Cannot specify location of gradle wrapper
Title: Message Title Steven Christou commented on JENKINS-12769 Re: Cannot specify location of gradle wrapper Gregory Boissinot do you know which commit this was part of which resolved this issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-26158) Active Directory authentication for Subversion plugin fails
Title: Message Title Steven Christou resolved as Duplicate This issue is a duplicate of JENKINS-27084 which was fixed in 2.5.1. Jenkins / JENKINS-26158 Active Directory authentication for Subversion plugin fails Change By: Steven Christou Status: InProgress Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-29492) Fix several findbugs issues
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-29492 Fix several findbugs issues Issue Type: Bug Assignee: Steven Christou Components: subversion-plugin Created: 19/Jul/15 1:10 PM Priority: Trivial Reporter: Steven Christou This issue is to resolve the following findbug issues: Use %n instead of \n to handle platform-specific line separators. Use StringBuilder for concatenating strings. Unnecessary unboxing of longs. Ignore the debugging static variable which can be mutable.
[JIRA] [subversion-plugin] (JENKINS-26370) Subversion Plugin 2.5 skips some externals resulting in partial checkout
Title: Message Title Steven Christou resolved as Duplicate Resolving issue as a duplicate of JENKINS-27084 . This was fixed in PR 117 and will be made available in the next release. Jenkins / JENKINS-26370 Subversion Plugin 2.5 skips some externals resulting in partial checkout Change By: Steven Christou Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title Steven Christou assigned an issue to Steven Christou Jenkins / JENKINS-27084 SVN authentication fails using subversion plugin v.2.5 Change By: Steven Christou Assignee: StevenChristou Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
