www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jarek Jarcec Cecho <jar...@apache.org>
Subject Re: FYI - disabled timer triggers across the board on builds.apache.org
Date Fri, 21 Aug 2015 16:29:55 GMT
No worries, I completely get why we made this change across the board. I actually feel bad
that I didn’t realize the consequences yesterday when I read the email and had to spend
good half an hour figuring it out :)


> On Aug 21, 2015, at 9:17 AM, Andrew Bayer <andrew.bayer@gmail.com> wrote:
> Oops, sorry about that!
> On Aug 21, 2015 12:02, "Jarek Jarcec Cecho" <jarcec@apache.org> wrote:
>> I’ve noticed that this change has pretty much disabled Hadoop world
>> spefici precommit [1] hook as this job is running every 10 minutes and
>> fetching updates from JIRA, rather then following any repository. I’ve put
>> back the “run every 10 minutes”. This job is usually done in less then 30
>> seconds, so I’m assuming that it won’t be a problem :)
>> Jarcec
>> Links:
>> 1: https://builds.apache.org/job/PreCommit-Admin
>>> On Aug 20, 2015, at 10:32 AM, Andrew Bayer <andrew.bayer@gmail.com>
>> wrote:
>>> I noticed a lot of jobs that were running every day regardless of whether
>>> anything changed and eating up a lot of executors, so I bulk-removed all
>> of
>>> them, changing those jobs to poll for changes hourly instead. If your
>>> project has one or two jobs that you need to run daily whether there are
>>> code changes or not, you can re-enable the timer, but please do not do
>> that
>>> for more than a couple jobs, and please do not do it for jobs that take
>>> longer than half an hour.
>>> A.

View raw message