[JIRA] (JENKINS-57199) java.io.IOException: Exception archiving {...list of files...}
Title: Message Title
Robert Baker updated an issue
Jenkins / JENKINS-57199
java.io.IOException: Exception archiving {...list of files...}
Change By:
Robert Baker
*23:11:56* ERROR: [withMaven] WARNING Exception executing Maven reporter 'Generated Artifacts Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at [https://issues.jenkins-ci.org|https://issues.jenkins-ci.org/]*23:11:56* java.io.IOException: Exception archiving \{...removed list of files...}*23:11:56* at org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher.process(GeneratedArtifactsPublisher.java:122)*23:11:56* at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118)*23:11:56* at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050)*23:11:56* at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:366)*23:11:56* at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)*23:11:56* at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166)*23:11:56* at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)*23:11:56* at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)*23:11:56* at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)*23:11:56* at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)*23:11:56* at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)*23:11:56* at java.util.concurrent.FutureTask.run(FutureTask.java:266)*23:11:56* at
[JIRA] (JENKINS-57199) java.io.IOException: Exception archiving {...list of files...}
Title: Message Title
Robert Baker updated an issue
Jenkins / JENKINS-57199
java.io.IOException: Exception archiving {...list of files...}
Change By:
Robert Baker
*23:11:56* ERROR: [withMaven] WARNING Exception executing Maven reporter 'Generated Artifacts Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at [https://issues.jenkins-ci.org|https://issues.jenkins-ci.org/]*23:11:56* java.io.IOException: Exception archiving \{...redacted list of files...}*23:11:56* at org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher.process(GeneratedArtifactsPublisher.java:122)*23:11:56* at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118)*23:11:56* at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050)*23:11:56* at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:366)*23:11:56* at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)*23:11:56* at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166)*23:11:56* at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)*23:11:56* at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)*23:11:56* at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)*23:11:56* at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59)*23:11:56* at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)*23:11:56* at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:58)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:332)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:83)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:244)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:232)*23:11:56* at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64)*23:11:56* at java.util.concurrent.FutureTask.run(FutureTask.java:266)*23:11:56* at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)*23:11:56* at
[JIRA] (JENKINS-57199) java.io.IOException: Exception archiving {...list of files...}
Title: Message Title
Robert Baker created an issue
Jenkins / JENKINS-57199
java.io.IOException: Exception archiving {...list of files...}
Issue Type:
Bug
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2019-04-26 19:41
Environment:
Jenkins 2.89.4 pipeline-maven-plugin 3.5.9
Priority:
Minor
Reporter:
Robert Baker
23:11:56 ERROR: [withMaven] WARNING Exception executing Maven reporter 'Generated Artifacts Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org 23:11:56 java.io.IOException: Exception archiving {...redacted list of files...}23:11:56 at org.jenkinsci.plugins.pipeline.maven.publishers.GeneratedArtifactsPublisher.process(GeneratedArtifactsPublisher.java:122)23:11:56 at org.jenkinsci.plugins.pipeline.maven.MavenSpyLogProcessor.processMavenSpyLogs(MavenSpyLogProcessor.java:118)23:11:56 at org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution$WithMavenStepExecutionCallBack.finished(WithMavenStepExecution.java:1050)23:11:56 at org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback$TailCall.onSuccess(BodyExecutionCallback.java:114)23:11:56 at org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.receive(CpsBodyExecution.java:366)23:11:56 at com.cloudbees.groovy.cps.Outcome.resumeFrom(Outcome.java:73)23:11:56 at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:166)23:11:56 at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)23:11:56 at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)23:11:56 at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261)23:11:56 at
[JIRA] (JENKINS-51938) After updating jenkins....its show this warning to me..... [WARNING] Attempt to (de-)serialize anonymous class hudson.maven.reporters.SurefireArchiver$2; see: https://jenkins.io
Title: Message Title Robert Baker commented on JENKINS-51938 Re: After updating jenkinsits show this warning to me. [WARNING] Attempt to (de-)serialize anonymous class hudson.maven.reporters.SurefireArchiver$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ what can i do now? Jenkins: 2.164.1, Unix slave, version 3.29, Maven Integration Plugin: 3.2 Receives similar warnings: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running com.unisys.mcpsql.EscapeSyntaxTokenizerTest [INFO] Tests run: 54, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.502 s - in com.unisys.mcpsql.EscapeSyntaxTokenizerTest [INFO] [INFO] Results: [INFO] [INFO] Tests run: 54, Failures: 0, Errors: 0, Skipped: 0 [INFO] [JENKINS] Recording test results[WARNING] Attempt to (de-)serialize anonymous class hudson.maven.reporters.SurefireArchiver$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/[WARNING] Attempt to (de-)serialize anonymous class hudson.maven.reporters.BuildInfoRecorder$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ 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-35421) Exception: "Could not create rootDir"
Title: Message Title Robert Baker reopened an issue I'm encountering a similar issue to this one in my environment: SLES 11 SP4 Jenkins 2.89.4 Job Configuration History Plugin 2.18 Docker Plugin 1.1.4 I've configured a Cloud using the Docker plugin and in that cloud I've defined a Jenkins slave container with a label of "SLES12SLAVEJDK8". When I run a job on this slave, however, the slave agent is never invoked and the job fails with the following error: SEVERE: Unexpected uncaught exception encountered while processing agent Image of ustr-docker.na.uis.unisys.com/singularity/sles12-slave-jdk8:latest java.lang.RuntimeException: Could not create rootDir /root/.jenkins/config-history/nodes/docker-111b76fe6f9/2018-05-22_14-15-48 at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryDir(FileHistoryDao.java:266) at hudson.plugins.jobConfigHistory.FileHistoryDao.getRootDir(FileHistoryDao.java:899) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntry(FileHistoryDao.java:906) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewHistoryEntryAndSaveConfig(FileHistoryDao.java:790) at hudson.plugins.jobConfigHistory.FileHistoryDao.createNewNode(FileHistoryDao.java:772) at hudson.plugins.jobConfigHistory.ComputerHistoryListener.onAdd(ComputerHistoryListener.java:82) at hudson.plugins.jobConfigHistory.ComputerHistoryListener.onConfigurationChange(ComputerHistoryListener.java:59) at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:231) at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1551) at jenkins.model.Nodes$2.run(Nodes.java:137) at hudson.model.Queue._withLock(Queue.java:1373) at hudson.model.Queue.withLock(Queue.java:1250) at jenkins.model.Nodes.addNode(Nodes.java:133) at jenkins.model.Jenkins.addNode(Jenkins.java:2094) at hudson.slaves.NodeProvisioner$2.run(NodeProvisioner.java:241) at hudson.model.Queue._withLock(Queue.java:1373) at hudson.model.Queue.withLock(Queue.java:1250) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:207) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Apparently the dynamic creation of the slave causes the job configuration history plugin to be invoked to save the configuration changes, however, no folder exists for the docker slave (docker-111b76fe6f9) in the node configuration history folder (/root/.jenkins/config-history/nodes). This makes the job configuration history plugin unusable in this environment, and so I had to disable it. Jenkins / JENKINS-35421
[JIRA] (JENKINS-50751) Link created by naginator plugin contains comma in job numbers over 999
Title: Message Title Robert Baker created an issue Jenkins / JENKINS-50751 Link created by naginator plugin contains comma in job numbers over 999 Issue Type: Bug Assignee: Nicolas De Loof Components: naginator-plugin Created: 2018-04-11 19:37 Environment: Jenkins 2.89.4 Naginator 1.17.2 Priority: Minor Reporter: Robert Baker The Naginator plugin creates a link on the project's build page like the following: Started by Naginator after the failure of build 2018-04-11-143326 Where "2018-04-11-143326" is the name of a build that failed and is hyperlinked to the build output. The hyperlink is: https://my.jenkins.unisys.com/view/Stealth(aware)/job/NFoS-Sysgen-Branch/1,070/ As you can see, when the build number exceeds 999 a comma is injected into the URL, making it invalid. Add Comment
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title Robert Baker commented on JENKINS-39343 Re: Persistent search/overviews/filtered views For enhanced security please implement support for Folders and folder-level security in Blue Ocean. We've created a multi-tenant Jenkins server for our internal development teams using Folders to isolate project teams and their jobs. When a team logs into our Jenkins server only their folders are visible. Team admins are only permitted to create new jobs within their respective folders and sub-folders, however, the Blue Ocean interface doesn't recognize folder-level permissions, and so the teams are unable to create new pipeline jobs using the Blue Ocean interface. 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 from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39483) javax.net.ssl.SSLException: Received fatal alert: certificate_unknown
Title: Message Title Robert Baker created an issue Jenkins / JENKINS-39483 javax.net.ssl.SSLException: Received fatal alert: certificate_unknown Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Nov/03 4:13 PM Environment: Jenkins 1.651.3 SLES 11 SP4 Priority: Minor Reporter: Robert Baker Our Jenkins server showing countless of these warnings in the System Log: Nov 01, 2016 9:39:17 PM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn javax.net.ssl.SSLException: Received fatal alert: certificate_unknown Nov 03, 2016 9:43:56 AM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn javax.net.ssl.SSLException: Received fatal alert: certificate_unknown Nov 03, 2016 9:43:58 AM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn javax.net.ssl.SSLException: Received fatal alert: certificate_unknown Nov 03, 2016 9:44:00 AM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn javax.net.ssl.SSLException: Received fatal alert: certificate_unknown Nov 03, 2016 9:44:03 AM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn javax.net.ssl.SSLException: Received fatal alert: certificate_unknown Nov 03, 2016 9:44:05 AM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn I believe we have imported all the relevant SSL certificates into the Java keystore. I've turned on various logs, but cannot get any further information to determine the unknown certificate. I'm looking for advice how to further diagnose and eliminate this warning.
[JIRA] (JENKINS-36239) StackOverflowError in plugin manager on 1.596.1
Title: Message Title Robert Baker commented on JENKINS-36239 Re: StackOverflowError in plugin manager on 1.596.1 Perhaps related - when the error first appeared I had inadvertently installed a plugin that was not compatible with my Jenkins version (i.e. the plugin required a slightly higher version of Jenkins). I have recently upgraded Jenkins to the required version and now the error seems to have gone away. 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] [git-client-plugin] (JENKINS-35338) Slave agent posts "Authentication Required" dialog when checking out from git
Title: Message Title Robert Baker commented on JENKINS-35338 Re: Slave agent posts "Authentication Required" dialog when checking out from git Thanks Mark - I'll give that a try. Also appears to work when slave agent runs as a Windows service. This is not critical as I now have at least two workarounds. 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-client-plugin] (JENKINS-35338) Slave agent posts "Authentication Required" dialog when checking out from git
Title: Message Title Robert Baker commented on JENKINS-35338 Re: Slave agent posts "Authentication Required" dialog when checking out from git PS - using JGit as git client and GitLab as git server. 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-client-plugin] (JENKINS-35338) Slave agent posts "Authentication Required" dialog when checking out from git
Title: Message Title Robert Baker created an issue Jenkins / JENKINS-35338 Slave agent posts "Authentication Required" dialog when checking out from git Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin, git-plugin Created: 2016/Jun/03 4:52 PM Environment: Jenkins 2.7 (Linux) Jenkins slave 2.57 (Windows 7) git-client-plugin 1.19.6 git-plugin 2.4.4 Priority: Minor Reporter: Robert Baker I have a simple job that checks out from a git repository (using https:// URL) and prints a directory of the workspace. Whenever this job runs on my Windows slave (connected by JNLP with slave agent running on the slave's desktop - that is, NOT as a service) it posts a dialog box to the slave's desktop requesting credentials for the git repository. While the dialog box is open the job hangs. As soon as I cancel the dialog without entering credentials the job completes successfully, however, the next execution of the job posts the dialog box again. I've provided the appropriate credentials in Jenkins for this git repository. When using git-client-plugin 1.18.0 and git-plugin 2.2.13 this job runs successfully without posting the dialog box on the slave.
[JIRA] [xunit-plugin] (JENKINS-32066) Time axis incorrect on Test History graph
Title: Message Title Robert Baker created an issue Jenkins / JENKINS-32066 Time axis incorrect on Test History graph Issue Type: Bug Assignee: Gregory Boissinot Attachments: TestResultsHistoryGraph.PNG Components: xunit-plugin Created: 14/Dec/15 9:38 PM Environment: Jenkins 1.575 xUnit plugin 1.95 Priority: Minor Reporter: Robert Baker Test results history consists of two tests that ran for 28 minutes and 11 minutes respectively. The graph includes a Y-axis labeled "seconds" with a range from 0 - 2 seconds (see attachment). Y-axis should be labeled "minutes" with a range from 0 - 30.
