Release

The release data processes roll up all the test summary data into pass/fail/na/unknown counts per release. A release is a single version of a distribution. So, for every release to CPAN, the release data is a summary of the test report grades. This data is very useful for showing a quick sanity check, like MetaCPAN does on their distribution information sidebar.

This process has multiple steps:

1. Populate the release_data table from the cpanstats table.
2. Roll up the counts into the release_summary table.

Populate release_data

This table is created from the cpanstats.cpanstats table by /var/www/reports/toolkit/reports-release-create.sh, which in turn calls /var/www/reports/toolkit/reports-release.pl in "Create" mode (which uses the Labyrinth::Plugin::CPAN::Release module located in /var/www/reports/cgi-bin/plugins).

This process should run for a few hours and then exit. It is run every few hours by cron.

Logs

• /var/www/reports/toolkit/logs/release-create-cron.log
• /var/www/reports/toolkit/logs/release-create.log

Update release_summary

Once the release_data table is complete, it is summed up into the release_summary table. This is done by /var/www/reports/toolkit/reports-release.sh, which calls /var/www/reports/toolkit/reports-release.pl in "Update" mode (which uses the Labyrinth::Plugin::CPAN::Release module located in /var/www/reports/cgi-bin/plugins).

Logs

• /var/www/reports/toolkit/logs/release-run.log
• /var/www/reports/toolkit/logs/release-cron.log

Troubleshooting

Released versions not appearing

If a module released more than 2-3 days ago is not yet appearing in the release API, check to see if /var/www/reports/toolkit/reports-release-create.sh is running. This script can hang, I suspect on very long queries, and if it's running for more than a few days, it's okay to kill it and wait for it to run again.