Done, I’ve done it with a scriptlet script. It’s easy to roll back if need be.
Let’s see how it goes.
Note that new jobs won’t have the option disable by default so we’ll need to handle this
if it proves successful.
FTR
is really fast for me ATM, not sure if this was caused by my change (I
doubt it).
Thanks
-Vincent
On 25 Aug 2014 at 10:04:10, vincent(a)massol.net (vincent(a)massol.net) wrote:
FTR I’m going to try disabling artifact archiving in Jenkins since:
1) It takes an awufully long at the end of each build to do that
2) It takes a lot of disk space (even though we only keep the last 20 builds)
3) We shouldn’t need that since our build already pushes artifacts in the local maven
repository
Thanks
-Vincent
On 23 Aug 2014 at 21:40:05, Eduard Moraru (enygma2002(a)gmail.com) wrote:
I`ve also registered on the jenkins-users list hoping for a helpful reply.
This problem is happening now *too* often and it has become a problem.
Either there is something in our build that jenkins does not like, either
it's a slave, a plugin, some configuration or even the hardware, we
*really* need to get to the bottom of this since it's affecting out
productivity.
Crossing fingers... :)
-Eduard
On Sat, Aug 23, 2014 at 6:31 PM, vincent(a)massol.net <vincent(a)massol.net>
wrote:
FYI, since that issue was closed, I’ve raised the
issue on the jenkins
mailing list:
https://groups.google.com/forum/#!topic/jenkinsci-users/L6ZSESU5x6s
Thanks
-Vincent
On 17 Aug 2014 at 14:09:44, vincent(a)massol.net (vincent(a)massol.net(mailto:
vincent(a)massol.net)) wrote:
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@massol.net)) wrote:
> Hi devs,
>
> I’ve started doing an analysis of using TC instead of Jenkins for
XWiki’s CI
at
http://design.xwiki.org/xwiki/bin/view/Proposal/ContinuousIntegrationSoftwa…
>
> 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
not enough to compensate for the plugin ecosystem,
the open source aspect
and what we’ve invested already in Jenkins
>
> 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
_______________________________________________
devs mailing list
devs(a)xwiki.org