On Wed Jan 16, 2013 at 12:39:30 +0200, Florian Heigl wrote: > From this thread it seems the buildbot fraction (I loved that posting, > really. Pure admin pr0n) and one of the Jenkins users have that much > of automation, and the other group is mostly concerned with > auto-validating their puppet configs. Right?
I see two distinct usage patterns in this thread: CI (as in the traditional software engineering sense), and batch job scheduling (where you are interested in the side-effects of the jobs). It was interesting to read about CI systems being used as cron replacements. As a BuildBot user, I would not recommend it as a replacement for cron. It's simply not designed to be used a batch job scheduler. For true continuous integration, however, where you want to repeatedly test some process or product against variable inputs (code, environment), BuildBot gets my thumbs up. > Also, from a planning point of view, I'd love to know if you allocate > a defined amount of time for the maintenance of your automation > system, or just do it adhoc with every thing that needs to be done. Over time, you will get a general feel for how much of your week is consumed maintaining your automation. I deduct this time from the total time I have to spend on current project work. If my TV remains green throughout that week, great! If it turns red, no biggie, I have already accounted for the time I'm going to spend debugging the problem, and I should still meet my other deadlines. _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
