jobs

I am in the process of cleaning up Jenkins (it was setup incorrectly) and I need to delete builds that are older than the latest 20 builds for every job. Is there any way to automate this using a script or something? I found many solutions to delete certain builds for specific jobs, but I can't seem to find anything for all jobs at once. Any help is much appreciated. Dave Bacher You can use the Jenkins Script Console to iterate through all jobs, get a list of the N most recent and perform some action on the others. import jenkins.model.Jenkins import hudson.model.Job MAX_BUILDS = 20 for (job

I'm using delayed job in a setup where I run multiple workers. For the sake of my question, it doesn't really matter, but let's say I run 10 workers (doing that in development mode currently). The problem I am having is that two different workers sometimes start working on the same job, calling the perform method on my job object. To the best of my understanding Delayed Job is using pessimistic locking to prevent this from happening, but it seems it sometimes still have enough time to lock steal the job before the first worker has time to actually lock it. I'm just asking to see if anyone else

Is there a way to get the retry count for the current job? I want the job to stop, not crash, after x retries. I would like to ask the retry count in the perform method so I could simply return if the retry count equals x. def perform(args) return if retry_count > 5 ... end Using Sidekiq 2.12. Edit I (not the OP) have the same question but for a different reason. If the job is being retried I want to do additional sanity checking to make sure the job is needed and to quit retrying if it is no longer expected to succeed because something external changed since it was queued. So, is there a way

The JobScheduler calls onStartJob() multiple times, although the job finished. Everything works fine, if I schedule one single job and wait until it has finished. However, if I schedule two or more jobs with different IDs at the same time, then onStartJob() is called again after invoking jobFinished() . For example I schedule job 1 and job 2 with exactly the same parameters except the ID, then the order is: onStartJob() for job 1 and job 2 Both jobs finish, so jobFinished() is invoked for both of them After that onStartJob() is called again for both jobs with the same ID My job is very basic

My question is very similar to this one except that my background process was started from a script. I could be doing something wrong but when I try this simple example: #!/bin/bash set -mb # enable job control and notification sleep 5 & I never receive notification when the sleep background command finishes. However, if I execute the same directly in the terminal, $ set -mb $ sleep 5 & $ [1]+ Done sleep 5 I see the output that I expect. I'm using bash on cygwin. I'm guessing that it might have something to do with where the output is directed, but trying various output redirection, I'm not

Under the Single Node Setup I try to run a single node example The jobtracker start however fails with exception : 2013-04-30 17:12:54,984 INFO org.apache.hadoop.metrics2.impl.MetricsConfig: loaded properties from hadoop-metrics2.properties 2013-04-30 17:12:54,994 INFO org.apache.hadoop.metrics2.impl.MetricsSourceAdapter: MBean for source MetricsSystem,sub=Stats registered. 2013-04-30 17:12:54,995 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period at 10 second(s). 2013-04-30 17:12:54,995 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: JobTracker metrics