[JIRA] [build-flow-plugin] (JENKINS-22516) FileAlreadyExistsException on parallel builds
Title: Message Title Aaron Marasco commented on JENKINS-22516 Re: FileAlreadyExistsException on parallel builds Possibly duped by JENKINS-25930. 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] [token-macro-plugin] (JENKINS-32012) Multi-line JOB_DESCRIPTION in subject blows up
Title: Message Title Aaron Marasco commented on JENKINS-32012 Re: Multi-line JOB_DESCRIPTION in subject blows up I was thinking something like that, or maybe a special case of just stopping at the first newline if you're in a subject. A multiline would probably be fine in the body. 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] [email-ext-plugin] (JENKINS-32014) Expose "Build Description" as a token
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-32014 Expose "Build Description" as a token Issue Type: Improvement Assignee: Alex Earl Components: email-ext-plugin Created: 10/Dec/15 6:13 PM Environment: Jenkins 1.634, email-ext 2.40.5, description-setter 1.10 Priority: Trivial Reporter: Aaron Marasco During the build, I use the Description Setter Plugin to push to the main project page some details that would normally take a little digging (e.g. which Jenkins node the build process was on, the git branch, etc). I'd like that information to be exposed as a token available in an email message. Add Comment
[JIRA] [email-ext-plugin] (JENKINS-32012) Multi-line JOB_DESCRIPTION in subject blows up
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-32012 Multi-line JOB_DESCRIPTION in subject blows up Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 10/Dec/15 6:08 PM Environment: Jenkins 1.634, email-ext 2.40.5 Priority: Minor Reporter: Aaron Marasco Multi-line JOB_DESCRIPTION causes the newlines to be inserted into the subject. That then causes the receiving mail client to display the rest of the headers as part of the message, e.g.: TODO: Expand. Are there HDL ones? - Still Failing! MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_Part_3_637129346.1449769940205" X-Jenkins-Job: Pretty name of job X-Jenkins-Result: FAILURE Precedence: bulk --=_Part_3_637129346.1449769940205 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit
[JIRA] [envinject-plugin] (JENKINS-19754) Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
Title: Message Title
Aaron Marasco commented on JENKINS-19754
Re: Jenkins/EnvInject incorrectly sets ${WORKSPACE} on slave node
I hit this bug as well with Jenkins 1.634 and EnvInject 1.92.1. The workaround above worked for me as well.
Before workaround, slave's "root" workspace used:
Building remotely on xilinx_builder (x86_64 hdlbuilder-ml605) in workspace /data/jenkins_workspace_xilinx_1/workspace/build_hdl + env + sort WORKSPACE=/data/jenkins_workspace_xilinx_1
After:
Building remotely on xilinx_builder (x86_64 hdlbuilder-ml605) in workspace /data/jenkins_workspace_xilinx_1/workspace/build_hdl + env + sort WORKSPACE=/data/jenkins_workspace_xilinx_1/workspace/build_hdl
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-environment-plugin] (JENKINS-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Aaron Marasco commented on JENKINS-22088 Re: Disk space leak with multiple copies of winstone-.jar in TEMP folder This seems to happen on non-Windows as well; I have a Linux server and have a bunch in /tmp. 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] [ruby-runtime-plugin] (JENKINS-31019) Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass
Title: Message Title Aaron Marasco commented on JENKINS-31019 Re: Ruby Runtime Plugin - java.lang.ClassCircularityError: org/jruby/RubyClass Has this issue been picked up? I'm pretty sure this error is the cause of JENKINS-30930, which is currently unclaimed. 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] [discard-old-build-plugin] (JENKINS-31255) Add paramerization support
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-31255 Add paramerization support Issue Type: Improvement Assignee: nkns165 Components: discard-old-build-plugin Created: 29/Oct/15 11:07 AM Priority: Minor Reporter: Aaron Marasco Parameterized builds should be treated in a different way, e.g. if the oldest build is using a parameter that there are no other successful builds for, it could be protected in some way. Add Comment
[JIRA] [build-keeper-plugin] (JENKINS-31254) Parameterized build support
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-31254 Parameterized build support Issue Type: Improvement Assignee: bap Components: build-keeper-plugin Created: 29/Oct/15 11:07 AM Priority: Minor Reporter: Aaron Marasco I'd like an option to be able to lock a build based upon parameters, e.g. "always keep the newest successful build for each permutation of parameters." I have a job where the build takes about 11 hours, so I don't run it much. But the next time I do the build, I want the new one to be tagged as "keep forever" and the previous one unlocked for normal removal. Add Comment
[JIRA] [clone-workspace-plugin] (JENKINS-26058) Implement a tarball-only option for cloning the workspace
Title: Message Title Aaron Marasco commented on JENKINS-26058 Re: Implement a tarball-only option for cloning the workspace Yes please, since "zip" screws up permissions. 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] [clone-workspace-plugin] (JENKINS-9779) Parent Project can not be defined by variable
Title: Message Title Aaron Marasco commented on JENKINS-9779 Re: Parent Project can not be defined by variable There are two proposed fixes on github - 1 and 2. Right now this is kind of a showstopper for me unless I write some hack to work around it. The plugin hasn't been touched in two years and is on many lists of "essential Jenkins plugins." Is it still being maintained? 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] [nodeofflinenotification] (JENKINS-31075) SEVERE: Failed Loading plugin nodeofflinenotification
Title: Message Title Aaron Marasco commented on JENKINS-31075 Re: SEVERE: Failed Loading plugin nodeofflinenotification Probably a dupe of JENKINS-31019. I'm having the same problem with git-notes. 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] [valgrind-plugin] (JENKINS-30993) Plugin using deprecated interface for "Run.getEnvironment"
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-30993 Plugin using deprecated interface for "Run.getEnvironment" Issue Type: Bug Assignee: Johannes Ohlemacher Components: valgrind-plugin Created: 16/Oct/15 12:30 PM Environment: Jenkins 1.633 CentOS 7 Labels: plugins api Priority: Minor Reporter: Aaron Marasco In the log file: Oct 16, 2015 7:53:28 AM hudson.model.Run getEnvironment WARNING: deprecated call to Run.getEnvironment at org.jenkinsci.plugins.valgrind.ValgrindPublisher.perform(ValgrindPublisher.java:115)
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Title: Message Title Aaron Marasco updated an issue Jenkins / JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Change By: Aaron Marasco Below is the stacktrace.It happened when I ran two jobs on a master. After running a while, both jobs crashed with this exception.I think this might be caused by a small flip-flop connectivity of the network, but I didn't noticed any disconnection.Another cause may be the huge load of jenkins: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 25942 hudson15 0 6902m 5.8g 5720 S 0.3 74.3 401:22.30 java Does the jenkins runs its own garbage collector at some specified time?We have to restart every few days because it's getting slower and slower until hangs out.FATAL: Unable to delete script file /tmp/hudson8303731085225956739.shhudson.util.IOException2: remote file operation failed: /tmp/hudson8303731085225956739.sh at hudson.remoting.Channel@30e472f4:build@autom-1 at hudson.FilePath.act(FilePath.java:781) at hudson.FilePath.act(FilePath.java:767) at hudson.FilePath.delete(FilePath.java:1022) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:461) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230)Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:499) at hudson.remoting.Request.call(Request.java:110) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:774) ... 13 moreCaused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115)Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) [jenkins] at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109)FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channelhudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy29.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:859) at hudson.Launcher$ProcStarter.join
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Title: Message Title Aaron Marasco updated an issue Jenkins / JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Change By: Aaron Marasco Below is the stacktrace.It happened when I ran two jobs on a master. After running a while, both jobs crashed with this exception.I think this might be caused by a small flip-flop connectivity of the network, but I didn't noticed any disconnection.Another cause may be the huge load of jenkins: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 25942 hudson15 0 6902m 5.8g 5720 S 0.3 74.3 401:22.30 java Does the jenkins runs its own garbage collector at some specified time?We have to restart every few days because it's getting slower and slower until hangs out.FATAL: Unable to delete script file /tmp/hudson8303731085225956739.shhudson.util.IOException2: remote file operation failed: /tmp/hudson8303731085225956739.sh at hudson.remoting.Channel@30e472f4:build@autom-1 at hudson.FilePath.act(FilePath.java:781) at hudson.FilePath.act(FilePath.java:767) at hudson.FilePath.delete(FilePath.java:1022) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:461) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230)Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:499) at hudson.remoting.Request.call(Request.java:110) at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.act(FilePath.java:774) ... 13 moreCaused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115)Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) [jenkins] at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109)FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channelhudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy29.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:859) at hudson.Launcher$ProcStarter.join
