Hi Greg, Thanks for the fine answer. It is hard for us the devs/maintainers to answer that kind of question, as we are a little bit biased. This is nevertheless a very good summary of the pros and cons of the two tools, and can only agree to all of that.
Pierre Le mar. 2 févr. 2016 à 22:32, Greg MacDonald <gmacdon...@trionworlds.com> a écrit : > Hi Jeremy, > > > > I have experience with both. Jenkins is more about providing canned > plugins that offer specific workflows whereas Buildbot is more of a toolkit > to build exactly what you need. With Jenkins you’ll spend a lot of time > looking around for plugins that may or may not be a fit. If those plugins > are buggy you’ll have to wait for a fix from the community or learn java > and dig in anyway. On the up side for Jenkins there are tons of plugins. > > > > Jenkins is easier to use initially but ultimately less powerful; BB is > more complicated to learn up front but very powerful. For example, BB > nine’s angular based UI plugin system is cutting edge and incredibly > powerful, but you’ll have to learn angular. On the up side angular is a > very popular and well-designed system worth learning. There is a lack of UI > plugins with BB, but I’m hoping to see more community contributed plugins > in py-pi after nine releases. > > > > Both are fine build systems, but in my opinion I think Jenkins is good for > smaller projects that aren’t too complex. Since you have a sophisticated > system I would tell your boss it’s not worth the effort to change. Jenkins > is far from perfect. And buildbot is composed with industry standard > technologies like python, nodejs, and angular. As well as solid libraries > like twisted. It’s also one of the most well designed projects I’ve ever > come across. > > > > -Greg > > > > *From:* users [mailto:users-boun...@buildbot.net] *On Behalf Of *Jeremy > Cornett > *Sent:* Sunday, January 31, 2016 2:00 PM > *To:* users@buildbot.net > *Subject:* [us...@bb.net] BuildBot versus Jenkins > > > > I’ve been an administrator of my company’s automated build system for > almost 4 years now, and for all of that time we’ve been using BuildBot. We > have a rather sophisticated system, with a lot of added functionality, and > I rather like BuildBot. My boss is wanting me to explore replacing our > BuildBot instance with Jenkins, with the reasoning that Jenkins is more of > an industry standard (more active development community) and it’s easier to > use from a developer/tester perspective. I really don’t know if his > reasoning is correct or not as I’ve never used Jenkins, but that aside, I > was wondering if anyone else has faced this question, “BuildBot versus > Jenkins,” and how did you answer it? > > > > [image: Description: > http://www.venafi.com/img/venafi_email_signature_logo.gif] > > | Jeremy Cornett | Configuration Management Engineer > > > > > _______________________________________________ > users mailing list > users@buildbot.net > https://lists.buildbot.net/mailman/listinfo/users
_______________________________________________ users mailing list users@buildbot.net https://lists.buildbot.net/mailman/listinfo/users