[JIRA] [git-plugin] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Jan Prach commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields We have run the script. I was suspicious if keeping only getLastBuiltRevision() is the right thing to do. It is not. At least not in combination with multijob plugin. It has triggered to rebuild all the branches again. Thousands of builds. Luckily I did it no 30 seconds sanity job. If I would have done it on all our jobs it would trigger about 20k 30 minutes long builds. The only safe option is to remove the git branches and keep build history short. The script is not good enough. 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] [git-plugin] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Jan Prach commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields This has quadratic memory complexity for modern workflows! Nicolas De Loof any progress fixing this upstream? Can I help? Thank you for the workaround Scott Hebert! This is very bad. It renders jenkins unusable. In our case jenkins lazy.BuildReference took 95% heap. But actually 91% heap is the git.util.BuildData. Those builds are by default hold as soft references. It sounds good. Problem is once those deserialized build.xml files take more than a heap it will deserialize gigabytes of data on every job view. It will not OOM because it is freeing those softreferences within a single request. But it can be extremely slow. It can read GB of data on every request. It is not ok. It cause timeouts and get progressively worse with every branch and/or every record in job history. I would be surprised if some (many) people would not leave jenkins for this issue. It is not easy to say for most people why page load takes 20 seconds or more. 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] [hp-application-automation-tools-plugin] (JENKINS-25087) Unable to execute BPT on remote UFT machine with Quality Center 11.52
rachel liu commented on JENKINS-25087 Unable to execute BPT on remote UFT machine with Quality Center 11.52 Hi, I have the same issue. But just to update some more information. Our machine has very strict security control . We have a temporary account with administrator access to local machine but in a different domain. All helpdesk approved application will be pushed to local machine automatically. What I found is , by default, the Jenkin service is started using "local user". If I run the ALM test case from Jenkin web console, I will receive the "Could not lock the host. Another test may be running. Try later" error msg . But, if I run the test case using command line, (launch cmd using local user), then run C:\Jenkins\workspace\POC\HpToolsLauncher.exe -paramfile props19032015110329904.txt Then it works. I don't know the difference between running it from cmd and running it from web console. If I run it from command line, the result will be published to ALM also, but the Jenkin web console is not updated, it still showing the previous fail log. This has been block us using Jenkin for months, hope it can be solved. Thanks. 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.
