I have used Jenkins in the past to schedule report delivery for business stakeholders, run maintenance tasks on the database and reload search caches. It's centralized, easy to access, doesn't require permissions on the server, provides a log of the console, gives you the duration of each task run, and you can easily set up email alerts or other kinds of notifications when a script fails. All this in addition to using it for daily development.
Thanks, topher On Tue, Aug 28, 2012 at 11:33 PM, Benjamin Lau <benjamin.a....@gmail.com>wrote: > I do. While I use Jenkins for build and release type tasks I also have > quite a few "maintenance" scripts that I manage inside it as well. I > find this is a better way to keep track of them than keeping them in > cron jobs (or System Scheduler on Windows). You can quickly check if > they are running and it also allows you to manage multiple machines > from a single place is you make use of slaves. > > Ben > > On Tue, Aug 28, 2012 at 10:24 PM, Manglu <man...@gmail.com> wrote: > > I encountered an operations team which had built a number of jobs in > Jenkins > > and all it does was kickstart scripts in the OS. > > > > This sounded a bit strange to me as they are effectively using Jenkins > as a > > glorified UI for these tasks. > > > > Are there others who do similar stuff? > > > > Thanks > > > > Manglu > > > > > > > > >
