18 Aug
2014
18 Aug
'14
11:12 a.m.
Hello!
This server is actually a virtual machine, hosted on a dedicated server
provided by XWikiSAS, however, adding a SSD would not be possible due to
two reasons:
1. This server is an older tier, for which the provider might not support
upgrades anymore (as they completely redesigned their offer)
2. it also hosts Maven and Nexus on the same VM, which use an extremely
large amount of disk space (close to 1TB in total).
Please note that this problem is not hardware related, since when Jenkins
is slow, it's using about 750% cpu (as far as I could observe at certain
points), so almost all of the 8 cores available on the whole dedicated
server, which means that something is broken which causes it to go wild.
Adding better hardware is just sweeping the dust under the carpet, and then
grabbing a better, SSD-powered carpet, and putting that on top of the first
carpet :)
On Mon, Aug 18, 2014 at 11:57 AM, Guillaume "Louis-Marie" Delhumeau <
gdelhumeau(a)xwiki.com> wrote:
Hi devs.
Could it be a benefit to use SSD drive instead of a classic hard drive on
the server?
Thanks,
Guillaume
2014-08-17 14:09 GMT+02:00 vincent(a)massol.net <vincent(a)massol.net>et>:
not
--
Best Regards,
Daniel Patriche
XWiki SAS SysAdmin
FYI I’ve raised the following JIRA for Jenkins:
https://issues.jenkins-ci.org/browse/JENKINS-24294
Thanks
-Vincent
On 11 Aug 2014 at 12:02:17, vincent(a)massol.net (vincent(a)massol.net
(mailto:
vincent(a)massol.net)) wrote:
http://design.xwiki.org/xwiki/bin/view/Proposal/ContinuousIntegrationSoftwa…
Hi devs,
I’ve started doing an analysis of using TC instead of Jenkins for
XWiki’s CI at
I’ve started by listing the use cases that we use/need and started
explaining how
they are or can be implemented in both Jenkins and TC.
My feeling at this point, without going further, is:
* We’ve invested quite a lot already on Jenkins (configuration +
scriptler groovy
scripts + don’t send emails on false positives, etc)
* Jenkins is open source and even though we have
slowness issues ATM,
even if we switch to TC, I believe we’ll go back to Jenkins at
some point
> * TC has a nicer UI, more polished and better thought out but that’s enough to compensate for the plugin ecosystem,
the open source aspect and
what we’ve invested already in Jenkins
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Thus at this point my personal feeling is that we should invest in
diagnosing more
the slowness issues in Jenkins and work with the Jenkins
team/mailing list to find out the cause and fix it with them.
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs