On Fri, Aug 26, 2016 at 12:33 AM Ravalika wrote:
>
> Is there anyway we can debug, why the slow performance apart from
> jenkins.log?
>
>
>
You can increase the logging level of the various classes in the git plugin
and the git client plugin in hopes that the logging time stamps and
messages will
Hi Mark,
Thank you,
answers inline
On Thursday, August 25, 2016 at 6:09:53 PM UTC+5:30, Mark Waite wrote:
>
> The job in the original picture showed only 7 items in its history. Are
> some of your jobs retaining many, many history entries? If so, that will
> slow the Jenkins startup time, an
The job in the original picture showed only 7 items in its history. Are
some of your jobs retaining many, many history entries? If so, that will
slow the Jenkins startup time, and might slow the time to compute changes.
The configuration slicing plugin is very effective at showing (and
changing)
I have tried applying the workaround mentioned for SECURITY-243, but no luck
When i click on recent changes, still takes approx 15 min to display the
messages.
Thank you
Renuka
On Thursday, August 25, 2016 at 11:26:13 AM UTC+5:30, Ravalika wrote:
>
> Thank you,
> Old Jenkin version is 1.6.3 migr
Thank you,
Old Jenkin version is 1.6.3 migrated to jenkins stable version 2.7.1
On Monday, August 22, 2016 at 4:54:44 PM UTC+5:30, Daniel Beck wrote:
>
> When asking about a possible regression, it helps to mention both the
> version you're using now, as well as the version you were using before
When asking about a possible regression, it helps to mention both the version
you're using now, as well as the version you were using before.
Try applying the workaround mentioned for SECURITY-243 here:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11
> On 22.0
Hi,
We have migrated recently to Jenkins new stable version. After migration,
Jenkins takes too long for displaying the changes of the current job
(approx. 15min).
Can you please provide me some suggestions to improve the speed?
Thanks,
Renuka
--
You received this message because you are s
