[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title
Jan Hoppe commented on JENKINS-57205
Re: Null pointer exception in JGit pre-build merge
This one made us revert version to Git/GitClient 3.11/2.8. Lots of our pipeline-jobs with merge in first step were breaking after few seconds. Please increase priority! Log: 11:59:44 Merging Revision f000ac5075553c119e286b18a561fdd01b50364a (origin/development) to origin/master, UserMergeOptions{mergeRemote='origin', mergeTarget='master', mergeStrategy='DEFAULT', fastForwardMode='FF'} java.lang.NullPointerException at hudson.plugins.git.util.GitUtils.getRevisionForSHA1(GitUtils.java:165) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:120) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:1053) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1146) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received thi
[JIRA] (JENKINS-45164) In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects
Title: Message Title Jan Hoppe commented on JENKINS-45164 Re: In jenkins pipeline a "checkout scm" now adds "--no-tags" instead of "--tags" for git projects If anyone knows how to add a fetch --tags in pipeline scripts i spend a beer. I am calling "git fetch" in shell script for working builds... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Jan Hoppe updated JENKINS-55905 Jenkins / JENKINS-55905 Git Plugin 3.9.2 cannot clone remote repo Change By: Jan Hoppe Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Jan Hoppe updated JENKINS-55905 The initial failure is fixed with 3.9.3 (I checked it yesterday!) Jenkins / JENKINS-55905 Git Plugin 3.9.2 cannot clone remote repo Change By: Jan Hoppe Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Jan Hoppe created an issue Jenkins / JENKINS-55905 Git Plugin 3.9.2 cannot clone remote repo Issue Type: Bug Assignee: Mark Waite Attachments: config.xml Components: git-plugin Created: 2019-02-01 06:58 Priority: Minor Reporter: Jan Hoppe Clone works with 3.9.1. I restored this version. Checking out Revision 3798afd32ccac880988e2c065f0445454e42dd95 (origin/master) Commit message: "#DC Added commits from SIG-Signa SIG-BIN-TestDaten to master" FATAL: not implemented yet Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from kie-jenkinsbld9.ceu.corp.heidelberg.com/10.51.200.115:57675 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserResponse.retrieve(UserRequest.java:389) at hudson.remoting.Channel.call(Channel.java:955) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283) at com.sun.proxy.$Proxy114.setupSubmoduleUrls(Unknown Source) at org.jenkinsci.plugins.gitclient.RemoteGitImpl.setupSubmoduleUrls(RemoteGitImpl.java:655) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:101) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1257) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1819) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.jav
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title Jan Hoppe commented on JENKINS-54250 Re: Disable restarting stages in jenkinsfile optionally That's right, disabling restart for all or a single stage would be great! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54386) preserveStashes does not work with parameter
Title: Message Title Jan Hoppe commented on JENKINS-54386 Re: preserveStashes does not work with parameter Yes, that works! The example in https://jenkins.io/doc/book/pipeline/syntax/ should be fixed! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54386) preserveStashes does not work with parameter
Title: Message Title
Jan Hoppe created an issue
Jenkins / JENKINS-54386
preserveStashes does not work with parameter
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-11-01 07:34
Environment:
Plugins: Pipeline: Declarative 1.3.2 Pipeline: Basic Steps 2.11
Priority:
Minor
Reporter:
Jan Hoppe
I tried the pipeline script below, I get WorkflowScript: 4: "preserveStashes" should have 0 arguments but has 1 arguments instead. @ line 4, column 9. w/o parameter restart with unstash works (by the way, multiple unstashes in one pipe is working too, as expected!) http://kie-jenkinslts.ppe.kie.de.heidelberg.com:8080/blue/organizations/jenkins/StashUnstash/detail/StashUnstash/9/pipeline#log-12 preserveStashes(5) pipeline { agent \{label 'master'} options { preserveStashes(5) } stages{ stage('create stash'){ steps { //create file writeFile file: './myFile.txt', text: 'fun stuff' stash includes: '*.txt', name: 'funstufftxt' } } stage('unstash first'){ steps{ dir('first') { unstash 'funstufftxt' script { def funtxt = readFile 'myFile.txt' println funtxt } } } } stage('unstash second'){ steps{ dir('second') { unstash 'funstufftxt' script { def funtxt = readFile 'myFile.txt' println funtxt } } } } } }
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title Jan Hoppe updated an issue Jenkins / JENKINS-54250 Disable restarting stages in jenkinsfile optionally Change By: Jan Hoppe Summary: Disable restarting stages in jenkinsfile optionally Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile
Title: Message Title Jan Hoppe updated an issue Jenkins / JENKINS-54250 Disable restarting stages in jenkinsfile Change By: Jan Hoppe Summary: Diesable Disable restarting stages in jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54250) Diesable restarting stages in jenkinsfile
Title: Message Title
Jan Hoppe created an issue
Jenkins / JENKINS-54250
Diesable restarting stages in jenkinsfile
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-10-25 12:00
Priority:
Major
Reporter:
Jan Hoppe
I'd like to switch off the restart stage option. My pipelines currently don't work correctly after restarting a stage (I check out git only at first stage...) like that: options { disableResume() *disableRestart()* }
Add Comment
[JIRA] (JENKINS-45455) Restarting stages
Title: Message Title Jan Hoppe commented on JENKINS-45455 Re: Restarting stages I might be wrong, but I don't get how to switch off the restart stage option. My pipelines currently don't work correctly after restarting a stage (I check out git only at first stage...) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45614) Activity tab is really slow
Title: Message Title Jan Hoppe commented on JENKINS-45614 Re: Activity tab is really slow Hey Guys, you did a great job to enhance the blue ocen performance! Thanks a lot! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-35998) No issue update if at least one issue does not exists
Title: Message Title
Jan Hoppe updated an issue
Jenkins / JENKINS-35998
No issue update if at least one issue does not exists
Change By:
Jan Hoppe
If an issue does not exist in JIRA, all other issues in build will not get an update.JIRA issues won't be saved either!I am using Plugin-Version 2.2.1Build Log:Checking out Revision 7a9b0232458eea8717a61bbb90bf93d7d0d8f815 (refs/remotes/origin/v18.00/feature/IssueUpdate)Error updating JIRA issues. Saving issues for next build.java.lang.NullPointerException Jenkins-Log:Jun 16, 2016 9:00:39 AM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotateAnnotating JIRA id: 'PD-882099'Jun 16, 2016 9:00:39 AM WARNING hudson.plugins.jira.JiraRestService getIssuejira rest client get issue error. cause: RestClientException{statusCode=Optional.of(404), errorCollections=[ErrorCollection{status=404, errors={}, errorMessages=[DER VORGANG EXISTIERT NICHT.]}]}Jun 16, 2016 9:00:39 AM WARNING hudson.plugins.jira.JiraChangeLogAnnotator annotateError getting remote issue PD-882099com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key PD-882099. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2383) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at hudson.plugins.jira.JiraSite.getIssue(JiraSite.java:424) at hudson.plugins.jira.JiraChangeLogAnnotator.annotate(JiraChangeLogAnnotator.java:101) at hudson.scm.ChangeLogSet$Entry.getMsgAnnotated(ChangeLogSet.java:252) at sun.reflect.GeneratedMethodAccessor242.invoke(Unknown Source)
Add Comment
[JIRA] (JENKINS-35998) No issue update if at least one issue does not exists
Title: Message Title Jan Hoppe updated an issue Jenkins / JENKINS-35998 No issue update if at least one issue does not exists Change By: Jan Hoppe If an issue does not exist in JIRA, all other issues in build will not get an update.JIRA issues won't be saved either! I am using Plugin-Version 2.2.1 Build Log:Checking out Revision 7a9b0232458eea8717a61bbb90bf93d7d0d8f815 (refs/remotes/origin/v18.00/feature/IssueUpdate)Error updating JIRA issues. Saving issues for next build.java.lang.NullPointerException 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-35998) No issue update if at least one issue does not exists
Title: Message Title Jan Hoppe created an issue Jenkins / JENKINS-35998 No issue update if at least one issue does not exists Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2016/Jun/16 6:32 AM Priority: Critical Reporter: Jan Hoppe If an issue does not exist in JIRA, all other issues in build will not get an update. JIRA issues won't be saved either! Build Log: Checking out Revision 7a9b0232458eea8717a61bbb90bf93d7d0d8f815 (refs/remotes/origin/v18.00/feature/IssueUpdate) Error updating JIRA issues. Saving issues for next build. java.lang.NullPointerException Add Comment
[JIRA] [email-ext] (JENKINS-23458) NullPointerException if Before Build reciepients is empty
Jan Hoppe resolved JENKINS-23458 as Cannot Reproduce NullPointerException if Before Build reciepients is empty Yes, but currently the problem has gone... Change By: Jan Hoppe (14/Jul/14 5:36 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-23458) NullPointerException if Before Build reciepients is empty
Jan Hoppe commented on JENKINS-23458 NullPointerException if Before Build reciepients is empty The problems occured directly after updating to 2.38.1 with the previously posted config... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-23458) NullPointerException if Before Build reciepients is empty
Jan Hoppe
commented on JENKINS-23458
NullPointerException if Before Build reciepients is empty
This is the PreBuild-Trigger, which kills the plugin
f...@bar.com, f...@bar.com
Achtung, in 5-10 Minuten werden die AutoInstalls gestartet
Rechner ${ENV,var="JKBP_AUTOINSTALL_PRT"}
false
false
project
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-23458) NullPointerException if Before Build reciepients is empty
Jan Hoppe created JENKINS-23458 NullPointerException if Before Build reciepients is empty Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 17/Jun/14 6:23 AM Description: Email was triggered for: Before Build Sending email for trigger: Before Build ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:515) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281) at hudson.plugins.emailext.ExtendedEmailPublisher.prebuild(ExtendedEmailPublisher.java:223) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:838) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:833) at hudson.model.Build$BuildExecution.doRun(Build.java:142) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1676) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: Jenkins ver. 1.554.1, emait-ext 2.38.1 Project: Jenkins Priority: Critical Reporter: Jan Hoppe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jan Hoppe commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException You should create a thread dump from your vm to enrich this report. Configuration is mentioned in http://devophuman.blogspot.com/2013/04/jenkins-is-going-wild.html. The VisualVM is part of Oracles JDK... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jan Hoppe commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException I blogged a little bit about detecting that problem: http://devophuman.blogspot.com/2013/04/jenkins-is-going-wild.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13013) User Info runs into a performance problem
Jan Hoppe closed JENKINS-13013 as Duplicate User Info runs into a performance problem Change By: Jan Hoppe (07/Mar/13 5:04 AM) Status: Resolved Closed Assignee: Kohsuke Kawaguchi Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jan Hoppe commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Hi, we have been running into these troubles often the last time. I found a "disable" flag for "reportException". Add -Dorg.kohsuke.stapler.compression.CompressionFilter.disabled=true to your VM-Options in jenkins xml! Good luck, Jan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11747) Wall Display does not show jobs in a nested view
Jan Hoppe closed JENKINS-11747 as Fixed Wall Display does not show jobs in a nested view Change By: Jan Hoppe (12/Nov/12 6:11 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11747) Wall Display does not show jobs in a nested view
Jan Hoppe resolved JENKINS-11747 as Fixed Wall Display does not show jobs in a nested view Fixed with Version 0.6.16. Works fine, thank you! I think fix is included with JENKINS-14660 Change By: Jan Hoppe (12/Nov/12 6:11 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13013) User Info runs into a performance problem
[ https://issues.jenkins-ci.org/browse/JENKINS-13013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hoppe reassigned JENKINS-13013: --- Assignee: Kohsuke Kawaguchi (was: Kosuke Nagano) > User Info runs into a performance problem > - > > Key: JENKINS-13013 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13013 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current >Reporter: Jan Hoppe >Assignee: Kohsuke Kawaguchi >Priority: Critical > > If I select "User-View" in Web-Interface, our system seems to block. > Same problem occurs in finishing a build and the E-Mail-Plugin fetches the > build commiters and culprits. > It seems that all changelog.xml-files of all builds up to now will be parsed! > "Handling GET /people/ : RequestHandlerThread[#17]" Id=93 Group=main RUNNABLE > at java.io.WinNTFileSystem.getBooleanAttributes(Native Method) > at java.io.File.exists(Unknown Source) > at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:814) > at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:792) > at hudson.model.View$People.getUserInfo(View.java:629) > at hudson.model.View$People.(View.java:607) > at jenkins.model.Jenkins.getPeople(Jenkins.java:903) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at > org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) > at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) > at org.kohsuke.stapler.Stapler.service(Stapler.java:159) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) > at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) > at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) > at > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) > at > hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74) > at > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) > at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) > at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) > at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) > at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) > at > hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) > at > hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegra
[JIRA] (JENKINS-13013) User Info runs into a performance problem
Jan Hoppe created JENKINS-13013: --- Summary: User Info runs into a performance problem Key: JENKINS-13013 URL: https://issues.jenkins-ci.org/browse/JENKINS-13013 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: Jan Hoppe Assignee: Kosuke Nagano Priority: Critical If I select "User-View" in Web-Interface, our system seems to block. Same problem occurs in finishing a build and the E-Mail-Plugin fetches the build commiters and culprits. It seems that all changelog.xml-files of all builds up to now will be parsed! "Handling GET /people/ : RequestHandlerThread[#17]" Id=93 Group=main RUNNABLE at java.io.WinNTFileSystem.getBooleanAttributes(Native Method) at java.io.File.exists(Unknown Source) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:814) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:792) at hudson.model.View$People.getUserInfo(View.java:629) at hudson.model.View$People.(View.java:607) at jenkins.model.Jenkins.getPeople(Jenkins.java:903) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477) at org.kohsuke.stapler.Stapler.service(Stapler.java:159) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at
[JIRA] (JENKINS-12882) Master stays offline if once low disk space occured
Jan Hoppe created JENKINS-12882: --- Summary: Master stays offline if once low disk space occured Key: JENKINS-12882 URL: https://issues.jenkins-ci.org/browse/JENKINS-12882 Project: Jenkins Issue Type: Bug Components: master-slave Reporter: Jan Hoppe Priority: Blocker After deleting files or/and decreasing DiskSpace variables Jenkins master stays offline! The offline information is permanently stored in config.xml in jenkins install dir. It's like 1011720192 true hudson.node_monitors.MonitorMarkedNodeOffline ... Delete those lines from the file an start jenkins again, everything is fine! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12882) Master stays offline if once low disk space occured
[ https://issues.jenkins-ci.org/browse/JENKINS-12882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hoppe updated JENKINS-12882: Affects Version/s: current > Master stays offline if once low disk space occured > --- > > Key: JENKINS-12882 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12882 > Project: Jenkins > Issue Type: Bug > Components: master-slave >Affects Versions: current >Reporter: Jan Hoppe >Priority: Blocker > > After deleting files or/and decreasing DiskSpace variables Jenkins master > stays offline! > The offline information is permanently stored in config.xml in jenkins > install dir. > It's like > class="hudson.node_monitors.DiskSpaceMonitorDescriptor$DiskSpace"> > 1011720192 > true > > > hudson.node_monitors.MonitorMarkedNodeOffline > > ... > Delete those lines from the file an start jenkins again, everything is fine! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
