Change site-scan cron job output

[sebb <se...@gmail.com>]

All the cronjobs apart from site-scan redirect stdout/stderr to a log file.

This makes it tricky to log anything from the job.

I'd like to change it to behave more like the other jobs, i.e. the
first parameter is the output file name.

I think this can be done without breaking the existing parameter handling:

If the first parameter contains a '/' or a '.' then assume it is a
file name (it cannot be a committee name)

I will try that out and once it has deployed the cronjob can be
changed accordingly.

Re: Change site-scan cron job output

[Shane Curcuru <as...@shanecurcuru.org>]

We have other groups who rely on the public/*.json files being present
and complete, from a variety of sources, not all of which are obvious.

As long as that stays stable, then big +1 on any changes that also make
the PMC's job easier of debugging things.

As Sam said to me earlier: don't be afraid to break something with your
improvement, just be sure to fix the publicly viewable bits quickly (or
revert).  8-)


sebb wrote on 5/15/17 6:37 PM:
> All the cronjobs apart from site-scan redirect stdout/stderr to a log file.
> 
> This makes it tricky to log anything from the job.
> 
> I'd like to change it to behave more like the other jobs, i.e. the
> first parameter is the output file name.
> 
> I think this can be done without breaking the existing parameter handling:
> 
> If the first parameter contains a '/' or a '.' then assume it is a
> file name (it cannot be a committee name)
> 
> I will try that out and once it has deployed the cronjob can be
> changed accordingly.
> 


-- 

- Shane
  https://www.apache.org/foundation/marks/resources

Re: Change site-scan cron job output

[sebb <se...@gmail.com>]

FTR: this has now been implemented

On 15 May 2017 at 23:37, sebb <se...@gmail.com> wrote:
> All the cronjobs apart from site-scan redirect stdout/stderr to a log file.
>
> This makes it tricky to log anything from the job.
>
> I'd like to change it to behave more like the other jobs, i.e. the
> first parameter is the output file name.
>
> I think this can be done without breaking the existing parameter handling:
>
> If the first parameter contains a '/' or a '.' then assume it is a
> file name (it cannot be a committee name)
>
> I will try that out and once it has deployed the cronjob can be
> changed accordingly.