It is well within the Jenkins use model to use it to automate all sorts of other tasks. We've even gone so far as to have some of our tasks learn how to write more detailed information in JUnit format so that we can monitor results from portions of the task while still allowing the task to complete.
On Thu, Nov 21, 2013 at 12:55 PM, Yasir <yasir...@gmail.com> wrote: > I am contemplating whether to use Jenkins for non-build related things. > It seems like a lot people are doing that, however, what I want to ask is > that does it go against the principle of Jenkins? I would love to automate > certain daily tasks that a team member has to perform using jenkins. But I > don't want to use it if by doing so will bastardize jenkins and it will be > used incorrectly. any thoughts? > > Yasir > > On Wednesday, August 29, 2012 12:24:58 AM UTC-5, Manglu 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 >> >> >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
