|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Sorry if my language sounded bad.
There is another serious issue with jenkins-SVN that u might want to take a look at the same time. It freaks me out to the point I was thinking to switch to something else or write my own scripts to do all that without using jenkins (I'm just trying to use jenkins for the first time for some basic stuff).
So, I set up jenkins to do regular svn updates (no revert, no clean checkout which are completely broken IMO, I use plain svn update and run a build script on each svn change).
After a day or two java.exe takes more than 2GB (WTF?!), so I need to restart it regularly, still even on start up it already takes like 500MB (WTF?!). It could easily be done within 10-20MB, and with some proper codding it could easily be a 1MB process that starts to take ram only when there is an svn update and jobs are started. I'm not a java-genius, so I have no clue how to tell java not to treat my ram like I don't care about it. This is weird problem with jenkins that it takes way too much ram and it grows to multi gig sizes without any reason for it. I reported a bug and it was closed as "not enough info", well, there isn't much I can tell other than it takes gigs of ram and I didn't do anything special with it.
Now I want to describe giant freaking BUG with jenkins svn. When jenkins grows to a few gigs I restart it, yes I'm very clever![]()
After I start it again, I open dashboard in a web browser and manually schedule builds of two svn repos that I set up with jenkins. Now, please tell me, how is it possible that jenkins/svn plugin that comes with it checks out these repos from scratch. Kind of deletes files and checks them out again?! I wouldn't care much if it was slow as hell on small svn update, but because of broken implementation it decides to delete everything that was previously checked out and do new checkout and it takes hours on my repo, while it shouldn't have taken any time at all. My questions still stands.. is it possible to simply use regular svn client? I'd even prefer if jenkins allowed me to run my script regularly and the script would return status if jenkins should start a build job or not. Something like that.