JamesThorpe Posted February 25, 2013 Report Share Posted February 25, 2013 Hi all, We use Plastic alongside Jenkins with the Jenkins plugin. Initially the setup worked fine, but we're seeing more and more build failures to the point where they now outnumber the successful builds. Quite often just running the build again will work. The issue we see is that after the plugin has invoked cm to get the files out, we get this error in the jenkins logs: FATAL: Executable returned an unexpected result code [1] ERROR: null We've turned on and compared the actual cm logs against a successful build and can't see anything out of the ordinary, so looks to be an issue with the plugin itself. Would appreciate any thoughts or extra logging we can turn on anywhere? Thanks, James. Link to comment Share on other sites More sharing options...
JamesThorpe Posted February 25, 2013 Author Report Share Posted February 25, 2013 I've been looking through as much as I can on the server - I've just come across this in the logs for the individual builds. It produces a build.xml with information about the build - part of the xml for a successful build is this: <scm plugin="plasticscm-plugin@2.0" class="com.codicesoftware.plugins.hudson.ChangeSetReader"/> whereas in a build where we see the above error, we get this: <scm class="hudson.scm.NullChangeLogParser"/> Link to comment Share on other sites More sharing options...
manu Posted February 25, 2013 Report Share Posted February 25, 2013 Hi James! Thanks for the info! we'll try to reproduce your situation. Link to comment Share on other sites More sharing options...
JamesThorpe Posted February 25, 2013 Author Report Share Posted February 25, 2013 Thanks Manu, If there's any other info I can provide that will help, let me know. Link to comment Share on other sites More sharing options...
manu Posted February 25, 2013 Report Share Posted February 25, 2013 Hi, yes! Can you please provide the Plastic SCM version and the Hudson installation version? If you find a pattern to reproduce the situation please report it. Link to comment Share on other sites More sharing options...
JamesThorpe Posted February 26, 2013 Author Report Share Posted February 26, 2013 Plastic is 4.1.10.268 - we've not updated for a while. Jenkins is 1.502, but we've seen it on a range of versions Plastic plugin for jenkins is v2 There doesn't really seem to be a pattern - we just check something in and have the plastic plugin polling, sometimes it will build, sometimes not. We see the same thing if we trigger the build manually in Jenkins also - sometimes works, sometimes not. It does seem to be getting worse, in that we seem to have more failures in a row before it then succeeds, though I don't have any quantitative figures on that. Link to comment Share on other sites More sharing options...
manu Posted February 26, 2013 Report Share Posted February 26, 2013 Thank you very much, we'll start testing it ASAP. Link to comment Share on other sites More sharing options...
JamesThorpe Posted February 26, 2013 Author Report Share Posted February 26, 2013 One final thing just in case it makes a difference - we check out in the region of 11,000 files totalling around 470mb. Also if we use the "update" option on the plugin rather than recreating the workspace from scratch, I don't think we see the issue (certainly not as frequently), but I'm not sure if that affects our build process by having files left behind from a previous build - I need to test further. On that note - if we remove a file, should the update option remove it from the local workspace, or will it only do changes and additions? Link to comment Share on other sites More sharing options...
manu Posted February 26, 2013 Report Share Posted February 26, 2013 Hi, it should remove the file. At the end of the day the operation should be a Plastic SCM "update" operation. It should be faster than regenerating the full workspace. Link to comment Share on other sites More sharing options...
JamesThorpe Posted February 26, 2013 Author Report Share Posted February 26, 2013 Thanks - we'll run it in this mode for a while and see if it helps Link to comment Share on other sites More sharing options...
manu Posted February 28, 2013 Report Share Posted February 28, 2013 Any updates? Link to comment Share on other sites More sharing options...
JamesThorpe Posted February 28, 2013 Author Report Share Posted February 28, 2013 We've not seen the issue since running with the Update checkbox ticked, and our processes still appear to be working ok Link to comment Share on other sites More sharing options...
calbzam Posted February 28, 2013 Report Share Posted February 28, 2013 Ok good, let us know if you have more problems Regards, Carlos Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.