[JIRA] (JENKINS-16018) Not all builds show in the build history dashboard on job

[ringo.des...@gmail.com (JIRA)]

Ringo De Smet
 commented on  JENKINS-16018


Not all builds show in the build history dashboard on job















This problem also occurs to me. The last upgrade of Jenkins we did was from 1.483 to 1.486. Existing projects seem to be OK as far as I can tell, but we also created a new freestyle job. This job has 16 builds which are correctly stored on disk on the master, but the dashboard doesn't show any history for that job.



























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-15130) BuildTrigger ambiguous

[ringo.des...@gmail.com (JIRA)]

Ringo De Smet
 commented on  JENKINS-15130


BuildTrigger ambiguous















@Rolf, sorry to disappoint you but I'm also just an impacted user. I just updated the ticket to make sure that the plugin developers notice that this problem exists. I didn't change any code...



























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-15130) BuildTrigger ambiguous

[ringo.des...@gmail.com (JIRA)]

Ringo De Smet
 updated  JENKINS-15130


BuildTrigger ambiguous
















Change By:


Ringo De Smet
(03/Oct/12 11:26 AM)




Assignee:


huybrechts





Priority:


Minor
Major





Component/s:


parameterized-trigger





Component/s:


core



























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-15130) BuildTrigger ambiguous

[ringo.des...@gmail.com (JIRA)]

Ringo De Smet
 commented on  JENKINS-15130


BuildTrigger ambiguous















Updated the component field to parameterized-trigger and assigned to component lead to bring it under their attention.



























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-15263) specifying a parameterized downstream job causes IllegalArgumentException: BuildTrigger is ambiguous

[ringo.des...@gmail.com (JIRA)]

Ringo De Smet
 resolved  JENKINS-15263 as Duplicate


specifying a parameterized downstream job causes IllegalArgumentException: BuildTrigger is ambiguous
















Duplicate of JENKINS-1530





Change By:


Ringo De Smet
(03/Oct/12 11:31 AM)




Status:


Open
Resolved





Resolution:


Duplicate



























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-15263) specifying a parameterized downstream job causes IllegalArgumentException: BuildTrigger is ambiguous

[ringo.des...@gmail.com (JIRA)]

 
Ringo De Smet
 edited a comment on  JENKINS-15263


specifying a parameterized downstream job causes IllegalArgumentException: BuildTrigger is ambiguous
















Duplicate of JENKINS-15130



























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-9540) Copy Artifacts Plugin Throws IOException: Pipe is already closed

[ringo.des...@gmail.com (JIRA)]

[ 
https://issues.jenkins-ci.org/browse/JENKINS-9540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159325#comment-159325
 ] 

Ringo De Smet commented on JENKINS-9540:


Today I ended up in a situation where even the workaround of cleaning the 
workspace and triggering a clean build doesn't work. A new build again ends up 
having the exception.

What I do notice however: I have two times the Copy Artifact as build step in 
place in this project. The first instance has a filter filled in, the second 
one not. If Copy Artifact fails, it is always the second one that fails. While 
I left the field Artifacts to copy blank to copy all artifacts, the exception 
has as message:

{code}
ERROR: Failed to copy artifacts from Utilities-2.1-linux-64bit with filter: **
{code}

Filling in {{\*\*}} as filter myself is invalid input, so where does this 
{{\*\*}} come from?

 Copy Artifacts Plugin Throws IOException: Pipe is already closed
 --

 Key: JENKINS-9540
 URL: https://issues.jenkins-ci.org/browse/JENKINS-9540
 Project: Jenkins
  Issue Type: Bug
  Components: copyartifact, core
Affects Versions: current
 Environment: Windows XP SP3, Sun JRE 1.6.25
Reporter: Dirk Weinhardt
Assignee: Kohsuke Kawaguchi
 Fix For: current


 Since updating to Jenkins 1.409 and Copy Artifacts Plugin 1.16, build jobs 
 fail with an IOException when copying build artifacts from the Master to the 
 current Slave.
 ERROR: Failed to copy artifacts from ABC Build with filter: 
 _tests\UnitTests\bin\Debug\**
 java.io.IOException: Pipe is already closed
   at hudson.remoting.PipeWindow.checkDeath(PipeWindow.java:83)
   at hudson.remoting.PipeWindow$Real.get(PipeWindow.java:165)
   at hudson.remoting.ProxyOutputStream._write(ProxyOutputStream.java:118)
   at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:103)
   at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
   at java.io.BufferedOutputStream.write(Unknown Source)
   at java.util.zip.DeflaterOutputStream.deflate(Unknown Source)
   at java.util.zip.DeflaterOutputStream.write(Unknown Source)
   at java.util.zip.GZIPOutputStream.write(Unknown Source)
   at java.io.BufferedOutputStream.write(Unknown Source)
   at org.apache.tools.tar.TarBuffer.writeBlock(TarBuffer.java:410)
   at org.apache.tools.tar.TarBuffer.writeRecord(TarBuffer.java:351)
   at 
 hudson.org.apache.tools.tar.TarOutputStream.writeEOFRecord(TarOutputStream.java:356)
   at 
 hudson.org.apache.tools.tar.TarOutputStream.finish(TarOutputStream.java:137)
   at 
 hudson.org.apache.tools.tar.TarOutputStream.close(TarOutputStream.java:149)
   at hudson.util.io.TarArchiver.close(TarArchiver.java:119)
   at hudson.FilePath.writeToTar(FilePath.java:1596)
   at hudson.FilePath.copyRecursiveTo(FilePath.java:1521)
   at hudson.FilePath.copyRecursiveTo(FilePath.java:1450)
   at 
 hudson.plugins.copyartifact.FilePathCopyMethod.copyAll(FilePathCopyMethod.java:51)
   at 
 hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:225)
   at 
 hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:199)
   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
   at 
 hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:649)
   at hudson.model.Build$RunnerImpl.build(Build.java:177)
   at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:423)
   at hudson.model.Run.run(Run.java:1362)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:145)
 Caused by: java.io.IOException: Pipe is already closed
   at 
 hudson.remoting.FastPipedOutputStream.write(FastPipedOutputStream.java:147)
   at 
 hudson.remoting.FastPipedOutputStream.write(FastPipedOutputStream.java:131)
   at 
 hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:185)
   at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
   at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
   at java.util.concurrent.FutureTask.run(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
 Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
 Caused by: hudson.remoting.FastPipedInputStream$ClosedBy: The pipe was closed 
 at...
   at 
 hudson.remoting.FastPipedInputStream.close(FastPipedInputStream.java:112)
   at hudson.FilePath$32.invoke(FilePath.java:1517)