Hi Vincent, Currently, Jenkins caused me a lot of trouble while I do not use it much. I have no idea if TC would be better. From your analysis, there is a lot of question marks on TC, which means it could be the right tool but we do not have enough time to fully check it. I agree that its licensing could be also an issue.
So, TC or improved Jenkins ? I don't care, but we definitely need a more stable and efficient tool. On Mon, Aug 11, 2014 at 12:01 PM, [email protected] <[email protected]> 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/ContinuousIntegrationSoftware > > 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 > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > -- Denis Gervalle SOFTEC sa - CEO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
