[JIRA] [publish-over-ftp] (JENKINS-16681) Publish Over FTP 1.8 not working with spaces in filename/path of source files
Alex Klein commented on JENKINS-16681 Publish Over FTP 1.8 not working with spaces in filename/path of source files Okay, it should have been obvious but I didn't find it right away: it now works, but one has to change the separator pattern in the advanced options from ", +" to ",+". Otherwise the whitespace is still interpreted as a possibility to split the string into multiple parts. Perhaps the default pattern should be changed? 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/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-17544) Promoted Build Plugin shows 404 on promotion log.
Alex Klein commented on JENKINS-17544 Promoted Build Plugin shows 404 on promotion log. I've also run into this problem, very problematic. 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/groups/opt_out.
[JIRA] (JENKINS-6721) Provide Link to VirtualBox Cloud Setup Documentation
Alex Klein commented on JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation Hi Henri, well, getting it all running took me a couple of days and a lot of research. Maybe it is related to my setup because I wanted the nodes to run on a windows server and have vboxwebsrv run as a scheduled task (so it gets fired up when the server is rebooted). As far as I get it, one has to: Create the node in Jenkins first (otherwise the java web start stuff later on won't work). Then manually (i.e. with GUI) launch the virtual box instance on the windows server In that instance go to jenkins webpage and then somewhere (forgot where) click on that link to get the java web start stuff installed within the virtual box. then shutdown the virtual machine and create the scheduled task to start vboxwebsrv One fun part is that when vboxwebsrv is started as a scheduled task, one will not see the UI at all (because it as run under the service account). So before setting up the scheduled task, one first has to get the JAVA web start up and running. Also, non of the other start up methods seemed to be able to connect from Jenkins to virtual box correctly! I always got the node to fire up the virtual box but never to actually start the build. I believe there were also problems as the scheduled task runs under the service account and therefore cannot access the usually virtualbox configuration folder (I remember something about having to create a virtual link). Also there seems to be no proper console output if the node is running in headless mode. Speaking of which, I did not find a proper explanation what the specific start up modes do. Plus there were some refresh issues where the vboxwebsrv was correctly detected but there were no machines in the list below it to select. I first had to save it without setting anything, then go back to the page and there the machine was suddenly listed. All in all, it was extremely difficult and frustrating! Granted, I haven't really done much with Jenkins before, but getting everything except for the virtualbox-plugin running was pretty easy. I hope to someday find the time to re-create all the steps at home and write a step-by-step guide and post it in my personal blog. But at my company, everything is working right now so I unfortunately don't have time to de-install everything just for the purpose of documentation. Alex 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-15318) Launch Slave Agent test does not shutdown VM on failure
Alex Klein commented on JENKINS-15318 Launch Slave Agent test does not shutdown VM on failure Also does not seem to shut down when one of the build steps fails. In my case, I did add a windows batch execute step which was not able to launch the correct problem due to some errors. The VirtualBox.exe process kept on running... 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-6721) Provide Link to VirtualBox Cloud Setup Documentation
Alex Klein commented on JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation I also have a lot of problems on getting this up and running. I managed to get jenkins to start up the VM, but still haven't managed for the second part of the connect where it is actually supposed to do something. A completed guide (not just the VirtualBox part) would be very helpful... One problem I ran into was to get the vboxwebsrv to find the VMs when starting as a scheduled windows task. The solution to this was creating a link as described here: http://code.google.com/p/phpvirtualbox/wiki/Windows2008Service But all the documentation of actually getting the Jenkins Slave Agent to run inside the VM seems to be obsolete/incorrect. Still haven't managed to figure this one out. 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-15318) Launch Slave Agent test does not shutdown VM on failure
Alex Klein created JENKINS-15318 Launch Slave Agent test does not shutdown VM on failure Issue Type: Bug Assignee: godin Components: virtualbox Created: 26/Sep/12 11:22 AM Description: I currently haven't set up the jenkins slave agent, so creating a new node and doing the launch test succeeds in starting the VM but fails to connect. At some point "VirtualBox Maximum number of attempts reached" happens but the VirtualBox seems to stay running (at least the windows process VirtualBox.exe is still there). I also just noticed that the log of the launch test shows "maximum number..." but still keeps the progress indicator spinning. Maybe for the plug-in the launch is still stuck? Environment: Jenkins 1.480 running on a Windows Server 2003, VirtualBox 4.2, Virtual Box Plugin 0.5.0, FireFox 15.0.1 Project: Jenkins Priority: Major Reporter: Alex Klein 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
