On Sat, Jun 10, 2017 at 11:10 AM, John D. Ament <johndam...@apache.org> wrote: > Unless someone objects, I'm going to introduce a shell script that executes > the contents of the cron jobs. I'm then going to raise a PR to infra to > update this section > https://github.com/apache/infrastructure-puppet/blob/deployment/modules/whimsy_server/manifests/init.pp#L70 > to > include a call to said script.
Not an objection, but thinking out loud. Some of those cronjobs are lightning fast. Others may take a while and consume network or CPU resources. For the fast ones, I find it mildly amusing that they use whimsy/asf library functions and capture the result in JSON, and you are parsing the JSON instead of using the same library functions. What this means is that you get stale data when you have ready access to fresher data. For the slow ones, I don't think it is appropriate to run then after every push. What I would suggest instead is a CGI script that lists the cron jobs that are runnable under the apache web server user id, and gives you a button that you can push that will run that specific job on request. What this would enable is for anybody (or perhaps just ASF members?) to rerun the script at will. I'd start by parsing the whimsy_server/manifests/cronjobs.pp. > John > > On Sat, Jun 10, 2017 at 8:58 AM John D. Ament <johndam...@apache.org> wrote: > >> I just pushed up a change that requires a change to the podlings.json >> file. However, that file is only generated in cron. I was wondering if it >> made sense that on deploy, to run a script that would regenerate the static >> files? >> >> John - Sam Ruby
