Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] Remote builds (Re: SVN server - What hardware do I need?)

Derek Atkins writes:

> Jenkins is pretty cool for system builds, but I'm not sure how well it
> works for developer build & test builds.  Unless you have Jenkins set up
> such that each developer has their only build chain I still feel (as a
> developer) that I need more control over my local build & test prior to
> "commit/push".  I.e., I want to be able to do a "local" build and run my
> own local tests and debugging before I push my changes to a place where
> others pick them up.  I have not seen a Jenkins install/configuration
> that supports that.
> Jenkins is great for building feature branches, release branches, and
> running automated packaging and testing.  But I don't think it works
> well for a developer build+test cycle where you might need to run
> through a dozen or two compile & test cycles to make sure you've fixed
> your bug.
> In short, I think developers still need their own build (and test)
> environments locally.

I totally agree with all of this.  In my environment we
enthusiastically use Jenkins for our
official/nightly/feature/etc. builds, but, for my day-to-day work
(feature development, unit-testing, etc.) I (the human, not Jenkins)
am the one who invokes our defined build-process.


--!kdc /
GnuPG: D87F DAD6 0291 289C EB1E 781C 9BF8 A7D8 B280 F24E

And the Army Ants, they leave nothin' but the bones...
   -- Tom Waits

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /