[JIRA] [parameterized-trigger-plugin] (JENKINS-34319) Cannot trigger multi-configuration from job
Title: Message Title Tommi Kiviniemi commented on JENKINS-34319 Re: Cannot trigger multi-configuration from job Some more information. I tried with the "Restrict matrix execution to a subset" option as well, but it seems to conflict with the Matrix Combinations Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Combinations+Plugin). Would be excellent if these two could co-exist. 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] [parameterized-trigger-plugin] (JENKINS-34319) Cannot trigger multi-configuration from job
Title: Message Title Tommi Kiviniemi updated an issue Jenkins / JENKINS-34319 Cannot trigger multi-configuration from job Change By: Tommi Kiviniemi It seems as the plugin can't trigger a specific configuration inside a matrix job. I have a CI trigger job set up to build a specific permutation of a multi-config job, such asMasterBuild/BRANCH_NAME=MyBranchName,BUILD_TYPE=Dev,PLATFORM=MyPlatform.When starting to type in the "Projects to build" input box it even fills in the parameters. However, when the job is triggered I get this:ERROR: Build aborted. Can't trigger undefined projects. 3 of the below project(s) can't be resolved: > BUILD_TYPE=Dev > MasterBuild/BRANCH_NAME= Puzzler MyBranchName > PLATFORM= ios MyPlatform It seems as the comma sign in the branch is used as a delimiter, thus making three trigger calls. Is matrix job triggering not supported? Can it be extended with say a checkbox for "Invoke matrix project", which would use a different delimiter (semicolon maybe)? 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] [parameterized-trigger-plugin] (JENKINS-34319) Cannot trigger multi-configuration from job
Title: Message Title Tommi Kiviniemi created an issue Jenkins / JENKINS-34319 Cannot trigger multi-configuration from job Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2016/Apr/18 10:31 PM Priority: Major Reporter: Tommi Kiviniemi It seems as the plugin can't trigger a specific configuration inside a matrix job. I have a CI trigger job set up to build a specific permutation of a multi-config job, such as MasterBuild/BRANCH_NAME=MyBranchName,BUILD_TYPE=Dev,PLATFORM=MyPlatform. When starting to type in the "Projects to build" input box it even fills in the parameters. However, when the job is triggered I get this: ERROR: Build aborted. Can't trigger undefined projects. 3 of the below project(s) can't be resolved: > BUILD_TYPE=Dev > MasterBuild/BRANCH_NAME=Puzzler > PLATFORM=ios It seems as the comma sign in the branch is used as a delimiter, thus making three trigger calls. Is matrix job triggering not supported? Can it be extended with say a checkbox for "Invoke matrix project", which would use a different delimiter (semicolon maybe)?
[JIRA] [p4-plugin] (JENKINS-34280) Ability to set "Populate options" from environment variable
Title: Message Title Tommi Kiviniemi created an issue Jenkins / JENKINS-34280 Ability to set "Populate options" from environment variable Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2016/Apr/15 2:14 PM Priority: Major Reporter: Tommi Kiviniemi There is no way to set the populate options dynamically. We have a master multi-configuration job which is invoked both manually and from CI trigger jobs. We'd like to do a "Auto cleanup and sync" for the CI builds (i.e. incremental sync), and a "Forced clean and sync" for the others. Right now we have to duplicate the entire master job just because this is not dynamic. Please add an option to drive this via an environment variable. Add Comment
[JIRA] [parameterized-trigger-plugin] (JENKINS-11577) Matrix axis are not recognixed as parameter
Title: Message Title
Tommi Kiviniemi edited a comment on JENKINS-11577
Re: Matrix axis are not recognixed as parameter
I can not access axes before SCM sync. I have a multi-configuration job where I want to define a custom workspace for the master's checkout and reuse that for the child (child workspace "."). Setting custom workspace to $ {BRANCH_NAME}_ BRANCH_NAME_ $ {PLATFORM}_ PLATFORM_ $ { BUILD_TYPE } results in a workspace called "$ {BRANCH_NAME}_ BRANCH_NAME_ $ {PLATFORM}_ PLATFORM_ $ { BUILD_TYPE } ". Trying to access the axes in "Prepare an environment for this run" can not access them yet either, nor via properties or a Groovy script. Right now there is no way for me to construct the workspace name due to this. Could you please make the axes available already at that point?
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] [parameterized-trigger-plugin] (JENKINS-11577) Matrix axis are not recognixed as parameter
Title: Message Title
Tommi Kiviniemi commented on JENKINS-11577
Re: Matrix axis are not recognixed as parameter
I can not access axes before SCM sync. I have a multi-configuration job where I want to define a custom workspace for the master's checkout and reuse that for the child (child workspace "."). Setting custom workspace to $ {BRANCH_NAME}${PLATFORM}${BUILD_TYPE} results in a workspace called "${BRANCH_NAME}
_$ {PLATFORM}
_$ {BUILD_TYPE}
". Trying to access the axes in "Prepare an environment for this run" can not access them yet either, nor via properties or a Groovy script. Right now there is no way for me to construct the workspace name due to this. Could you please make the axes available already at that point?
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] [matrix-project-plugin] (JENKINS-14618) ignore the checkout on the master
Title: Message Title Tommi Kiviniemi commented on JENKINS-14618 Re: ignore the checkout on the master Can this be reopened? There are other issues that had been closed as duplicates of this, and this one is closed. I see it if not a bug, then a huge oversight that there is not a checkbox for whether master should do an SCM checkout as well. I am in the exact same boat as Alexander, the master does a lengthy unnecessary SCM checkout before the slaves start building. I tried to work around this by using a custom workspace for the slaves and reuse it from the master, but the workspace name can not be constructed from the axis values as they are not initialised there yet. The current behaviour is 1) unexpected 2) increases build times by tens of percent for no gain. What good does it do to do two SCM syncs, where one is discarded? 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-failure-analyzer-plugin] (JENKINS-25441) java null exception in ScanOnDemandBaseAction
Title: Message Title Tommi Kiviniemi edited a comment on JENKINS-25441 Re: java null exception in ScanOnDemandBaseAction We are getting this as well. New builds don't get scanned, and the existing ones can not be scanned either for in that one particular job. We also get the same exception. 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-failure-analyzer-plugin] (JENKINS-25441) java null exception in ScanOnDemandBaseAction
Title: Message Title Tommi Kiviniemi commented on JENKINS-25441 Re: java null exception in ScanOnDemandBaseAction We are getting this as well. New builds don't get scanned, and the existing ones can not be scanned either for that one particular job. We also get the same exception. 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] [xcode-plugin] (JENKINS-31398) Archive no longer works
Title: Message Title Tommi Kiviniemi created an issue Jenkins / JENKINS-31398 Archive no longer works Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 04/Nov/15 3:12 PM Environment: Mac OS X El Capitan Priority: Major Reporter: Tommi Kiviniemi The archive option no longer works with newer Xcode versions as it has been obsoleted. It can be called via this command instead: xcodebuild -project "XXX.xcodeproj" -scheme "Unity-iPhone" -configuration Release archive Would be great if the plugin could be updated to support this. Thanks! Tommi
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi commented on JENKINS-23958 Pipe Broken I am sorry that I haven't gotten back to you regarding the sample project yet, but we are just about to release our game and have been too swamped to find time for it. Just wanted to let you know that I will do it as soon as time permits. PS. We are using Unity Cache server, running on the same machine as everything else. If you have it could you try enabling it to see if you get the sample project build to fail? 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi commented on JENKINS-23958 Pipe Broken Thank you so much for looking into this issue. I will try to build the sample project with our setup to see whether it fails and report any findings. I don't know if this affects anything but the slave executors are running on the same machine as the master in our current setup, so the SSH connections never go over the network. I will try to set up a repository with the sample project as quickly as possible to help you get more data. Thanks, Tommi 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi updated JENKINS-23958 Pipe Broken Change By: Tommi Kiviniemi (05/Aug/14 9:58 AM) Description: WegetapipebrokenexceptionintheJenkinsUnitypluginabout50%ofthetime. Theworkspaceiscleanedbeforeeverybuild,andcompiledassetsarefetchedfromaUnityCacheserverrunningonthesamemachine. ItALWAYS Theerror happens ALWAYS attheexactsamestep:[...]Refresh:trashingasset2197dcffa7f1e4295a0f8e83fed9f5bfRefresh:trashingassetbca6eeff7c4924a429da9a1b3450b036Refresh:trashingasset6b4a9fff255e844c999a4bcd6105d894Refresh:trashingassetd63cefffccda34624843a84caddbb852Failureonremotejava.io.IOException:Pipebrokenatjava.io.PipedInputStream.read(PipedInputStream.java:322)atjava.io.PipedInputStream.read(PipedInputStream.java:378)atjava.io.InputStream.read(InputStream.java:101)atorg.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64)Whenitsucceeds,thenextlineisALWAYSUpdatingAssets-GUID:1000...done.[Time:18.743246ms]SoIFthebuildfails,thenitisALWAYSrightafterthelastassetbeingtrashed.Ifitmakesittothenextline(updatingassetwithGUID1000),thenthebuildwillALWAYSsucceed.Ithinkthatthefrequencyoftheerrorisdependentonhowlargetheprojectis,aswedidntgettheerrornearlyasmuchinthebeginningphasesoftheproject.Nowthattheprojectislargewegetthepipebrokenerrorabout50%ofthetime.Thisisofcourseconjectureandthefrequencyoftheerrorcouldbecausedbysomethingelseentirely.Also,errorstendtohappenmultipletimesinarow.Conversely,onceitsucceedsittendstosucceedforseveralconsecutivebuilds.Thisisofcourseverymuchashowstopperforus,soIdbeextremelygratefulifsomeonecouldhavealookatthisissue.Thanks!-TommiKiviniemiVPTechnology,Co-founderSeriouslyDigitalEntertainmentLtd. 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi edited a comment on JENKINS-23958 Pipe Broken Please also note that the log file itself does contain the portions after the point where Jenkins bails out, so it is not a matter of log truncation or similar. I'm suspecting this might be a timeout in the log stream, as that step takes quite a long time and Unity doesn't output anything in the log there. 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi edited a comment on JENKINS-23958 Pipe Broken Hi lacostej! We are currently using Jenkins 1.574 (newest stable), and this has happened with pretty much every Jenkins version for the last couple of months. Yes, we are using -logFile (to prevent multiple concurrent builds from overwriting the same log). Here's the argument to the Unity plugin: -noGraphics -batchmode -quit -projectPath “/XXX/workspace/YYY/ZZZ" -logFile "/XXX/workspace/YYY/Editor.log" -executeMethod Builder.BuildFromCommandLine -CustomArgs:Mode=Debug;Target=iPhone;OutputPath=/XXX/workspace/YYY/Build/iOS_XCode If I open the log file at /XXX/workspace/YYY/Editor.log I can see the lines following the pipe broken error (Updating Assets - GUID: 1000... etc.), so Unity is definitely outputting that to the log. For whatever reason the Unity plugin's stream reader seems to think that the log stream gets broken there and bails out. I don't know if the stream times out or what the heck is going on there? Please let me know if you need any more info. Tommi 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi commented on JENKINS-23958 Pipe Broken Hi lacostej! We are currently using Jenkins 1.574 (newest stable), and this has happened with pretty much every Jenkins version for the last couple of months. Yes, we are using -logFile (to prevent multiple concurrent builds from overwriting the same log). Here's the argument to the Unity plugin: i-noGraphics -batchmode -quit -projectPath “/XXX/workspace/YYY/ZZZ" -logFile "/XXX/workspace/YYY/Editor.log" -executeMethod Builder.BuildFromCommandLine -CustomArgs:Mode=Debug;Target=iPhone;OutputPath=/XXX/workspace/YYY/Build/iOS_XCode/i If I open the log file at /XXX/workspace/YYY/Editor.log I can see the lines following the pipe broken error (Updating Assets - GUID: 1000... etc.), so Unity is definitely outputting that to the log. For whatever reason the Unity plugin's stream reader seems to think that the log stream gets broken there and bails out. I don't know if the stream times out or what the heck is going on there? Please let me know if you need any more info. Tommi 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi edited a comment on JENKINS-23958 Pipe Broken Please also note that the log file itself does contain the portions after the point where Jenkins bails out, so it is not a matter of log truncation or similar. I'm suspecting this might be a timeout in the log stream reader, as that step takes quite a long time and Unity doesn't output anything in the log there. 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi edited a comment on JENKINS-23958 Pipe Broken Hi lacostej! We are currently using Jenkins 1.574 (newest stable), and this has happened with pretty much every Jenkins version for the last couple of months. Yes, we are using -logFile (to prevent multiple concurrent builds from overwriting the same log). Here's the argument to the Unity plugin: -noGraphics -batchmode -quit -projectPath “/XXX/workspace/YYY/ZZZ" -logFile "/XXX/workspace/YYY/Editor.log" -executeMethod Builder.BuildFromCommandLine -CustomArgs:Mode=Debug;Target=iPhone;OutputPath=/XXX/workspace/YYY/Build/iOS_XCode If I open the log file at /XXX/workspace/YYY/Editor.log I can see the lines following the pipe broken error (Updating Assets - GUID: 1000... etc.), so Unity is definitely outputting that to the log. For whatever reason the Unity plugin's stream reader seems to think that the log stream gets broken there and bails out. I don't know if the stream times out or what the heck is going on there? Please let me know if you need any more info. PS. The same error happened without -logFile as well, albeit it seemed to happen more often (could be because concurrent builds could overwrite the same log in that scenario). But even when building ONE build at a time, using -logFile or not using it can still invoke the same pipe broken error. Tommi 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi edited a comment on JENKINS-23958 Pipe Broken Please also note that the log file itself does contain the portions after the point where Jenkins bails out, so it is not a matter of log truncation or similar. I'm suspecting this might be a timeout in the log stream reader, as that step takes quite a long time and Unity doesn't output anything in the log there during that time. 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi edited a comment on JENKINS-23958 Pipe Broken Hi lacostej! We are currently using Jenkins 1.574 (newest stable), and this has happened with pretty much every Jenkins version for the last couple of months. Yes, we are using -logFile (to prevent multiple concurrent builds from overwriting the same log). Here's the argument to the Unity plugin: -noGraphics -batchmode -quit -projectPath “/XXX/workspace/YYY/ZZZ" -logFile "/XXX/workspace/YYY/Editor.log" -executeMethod Builder.BuildFromCommandLine -CustomArgs:Mode=Debug;Target=iPhone;OutputPath=/XXX/workspace/YYY/Build/iOS_XCode If I open the log file at /XXX/workspace/YYY/Editor.log I can see the lines following the pipe broken error (Updating Assets - GUID: 1000... etc.), so Unity is definitely outputting that to the log. For whatever reason the Unity plugin's stream reader seems to think that the log stream gets broken there and bails out. I don't know if the stream times out or what the heck is going on there? Please let me know if you need any more info. PS. The same error happens without -logFile as well, albeit it seems to happen more often (could be because concurrent builds could overwrite the same log in that scenario). But even when building ONE build at a time, using -logFile or not using it can still invoke the same pipe broken error. Tommi 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi edited a comment on JENKINS-23958 Pipe Broken Hi lacostej! We are currently using Jenkins 1.574 (newest stable), and this has happened with pretty much every Jenkins version for the last couple of months. Yes, we are using -logFile (to prevent multiple concurrent builds from overwriting the same log). Here's the argument to the Unity plugin: -noGraphics -batchmode -quit -projectPath “/XXX/workspace/YYY/ZZZ" -logFile "/XXX/workspace/YYY/Editor.log" -executeMethod Builder.BuildFromCommandLine -CustomArgs:Mode=Debug;Target=iPhone;OutputPath=/XXX/workspace/YYY/Build/iOS_XCode If I open the log file at /XXX/workspace/YYY/Editor.log I can see the lines following the pipe broken error (Updating Assets - GUID: 1000... etc.), so Unity is definitely outputting that to the log. For whatever reason the Unity plugin's stream reader seems to think that the log stream gets broken there and bails out. I don't know if the stream times out or what the heck is going on there? Please let me know if you need any more info. PS. The same error happens without -logFile as well, albeit it seemed to happen more often (could be because concurrent builds could overwrite the same log in that scenario). But even when building ONE build at a time, using -logFile or not using it can still invoke the same pipe broken error. Tommi 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi updated JENKINS-23958 Pipe Broken Change By: Tommi Kiviniemi (24/Jul/14 1:24 PM) Environment: * MacOSX , * SlavenoderunningonsamemachineasJenkins(connectedviaSSHtolocalhost,samejenkinsuserrunningeverything) *UnityCacheserver(runningonsamemachineasJenkinsandUnityslavenode) 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi created JENKINS-23958 Pipe Broken Issue Type: Bug Assignee: lacostej Components: unity3d-plugin Created: 23/Jul/14 6:59 PM Description: We get a pipe broken exception in the Jenkins Unity plugin about 50% of the time. It ALWAYS happens at the exact same step: ... Refresh: trashing asset 2197dcffa7f1e4295a0f8e83fed9f5bf Refresh: trashing asset bca6eeff7c4924a429da9a1b3450b036 Refresh: trashing asset 6b4a9fff255e844c999a4bcd6105d894 Refresh: trashing asset d63cefffccda34624843a84caddbb852 Failure on remote java.io.IOException: Pipe broken at java.io.PipedInputStream.read(PipedInputStream.java:322) at java.io.PipedInputStream.read(PipedInputStream.java:378) at java.io.InputStream.read(InputStream.java:101) at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) When it succeeds, the next line is ALWAYS Updating Assets - GUID: 1000... done. Time: 18.743246 ms So IF the build fails, then it is ALWAYS right after the last asset being trashed. If it makes it to the next line (updating asset with GUID 1000), then the build will ALWAYS succeed. I think that the frequency of the error is dependent on how large the project is, as we didn't get the error nearly as much in the beginning phases of the project. Now that the project is large we get the pipe broken error about 50% of the time. This is of course conjecture and the frequency of the error could be caused by something else entirely. Also, errors tend to happen multiple times in a row. Conversely, once it succeeds it tends to succeed for several consecutive builds. This is of course very much a showstopper for us, so I'd be extremely grateful if someone could have a look at this issue. Thanks! Tommi Kiviniemi VP Technology, Co-founder Seriously Digital Entertainment Ltd. Environment: Mac OS X Project: Jenkins Priority: Blocker Reporter: Tommi Kiviniemi 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi commented on JENKINS-23958 Pipe Broken Please note that this is not a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-22492 as the cause is very different in #22492. 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi commented on JENKINS-23958 Pipe Broken Please also note that the log file itself does contain the portions after the point where Jenkins bails out, so it is not a matter of log truncation or similar. 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi updated JENKINS-23958 Pipe Broken Change By: Tommi Kiviniemi (23/Jul/14 8:44 PM) Environment: MacOSX ,SlavenoderunningonsamemachineasJenkins(connectedviaSSHtolocalhost,samejenkinsuserrunningeverything) 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.
