+1. We're even considering using Jenkins as the default light scheduler for
some of our customers.
Basically, use Jenkins to do anything repetitive. People's brains should be
used to do things machines can't.
Le 21 nov. 2013 20:59, "Mark Waite" a écrit :
> It is well within the Jenkins use model
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 complet
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 am working on text mining project that uses wikinews as a training corpus.
I use Jenkins for:
a) rebuilding my corpus every week (since wikinews just keeps growing)
b) rebuilding my text mining engine with the new corpus
c) testing the text mining engine and recording the results.
All are dri
On Thu, Aug 30, 2012 at 9:36 AM, Paul Weiss wrote:
> Rundeck looks interesting. It supports a use case that Jenkins doesn't,
> namely, running a job on _every_ slave. I would love to use this to, say,
> cleanup old workspace directories for Jenkins jobs that have been deleted.
Rundeck does look i
Jenkins does support this too:
https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin
/Domi
On 30.08.2012, at 16:36, Paul Weiss wrote:
> Rundeck looks interesting. It supports a use case that Jenkins doesn't,
> namely, running a job on _every_ slave. I would love to use this to
Rundeck looks interesting. It supports a use case that Jenkins doesn't,
namely, running a job on _every_ slave. I would love to use this to, say,
cleanup old workspace directories for Jenkins jobs that have been deleted.
-P
On Wed, Aug 29, 2012 at 12:32 PM, R. Tyler Croy wrote:
>
> On Tue, 28 A
On Wed, Aug 29, 2012 at 12:45 PM, David Weintraub wrote:
> I've always said one of the ways you know a tool is wonderful if it
> becomes useful for other tasks that were never anticipated by the
> original authors.
>
> The fact that people are using Jenkins in situations where there is no
> build,
I've always said one of the ways you know a tool is wonderful if it
becomes useful for other tasks that were never anticipated by the
original authors.
The fact that people are using Jenkins in situations where there is no
build, or even real development taking place is a great complement to
the J
On Tue, 28 Aug 2012, 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.
I've used this p
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
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
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
13 matches
Mail list logo
