Comments you submit will be routed for moderation. If you have an account, please log in first.

Ticket #2189 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

Setup code-checks for VOTD process

Reported by: wehart Owned by: lafisk
Priority: major Milestone:
Component: Acro Projects Version: 1.0
Keywords: Cc:
Subcomponent: Configuration and Building


  1. The Acro download web page
  2. Cron job for creating VOTD tarballs
  3. Code check report to document the success of this process


Change History

comment:1 Changed 12 years ago by wehart

  • Owner changed from wehart to lafisk
  • severity changed from major to normal

I've setup a preliminary VOTD process, so I'm reducing the severity of this bug.

I'm reassigning this to Lee Ann, who is going to rework the scripts I've setup to make them more interactive, and to integrate error reporting/checks.

The VOTD download web page is:

comment:2 Changed 12 years ago by wehart

  • severity changed from normal to critical
  • Summary changed from Setup VOTD process to Setup code-checks for VOTD process

The last remaining element of this bug is to setup a code check in


that interrogates the VOTD directories to look for problems. For example, today I noted that the last VOTD was setup on 8/1, but there is not diagnostic info about why the VOTD wasn't setup today.

comment:3 Changed 12 years ago by lafisk

  • Status changed from new to closed
  • Resolution set to fixed

I added /acro/qa/checks/votds which looks at the age in days
of the VOTD tar files on software. "0" is a good age - that means
it's current. acro/packages/exact/src/db/db_code_checks writes
the results to the text file that gets mailed out nightly.

If we wanted to mail out an html file instead, we could have a
link to the log file that explains why votd creation failed
when the votds are out of date.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.