Quote:
Originally Posted by dijetlo
Well apparently they got bored on the multi-threaded maven infrastructure. You can pick them out of the crowd by their intense desire to slather Jenkins on everything (Apparently Jenkins has no ssh functionality which makes it an odd choice for managing virtual environments) also... Isn't that why we chased Chef off these nodes? Jenkins comes with the added bonus of distributing the build process across every node with an agent, you can imagine the impact that has on scaling algorithms...
Still, some are clever and quick to learn, most don't think it's worth the time. The smart ones will hang around and contribute, the dumb ones will get MBAs and become our bosses... It's the circle of life...
|
YMMV, but after dealing with maven and gradle, I'd prefer to use gradle. (That's even after dealing with grails for a couple of years which has poisoned groovy in my mind.) I'm quite comfortable with XML, BTW, so that's not the issue. (I've written documentation in DocBook and enjoyed it, as a minor example.)
