QA (public)

New template generator features requires PSQL to be present. A convenient one is already deployed inside a container environment on qam2. As old qam server should no longer be used, it is probably a good time to finally migrate template generator to new machine. So far, following items needs to be reviewed, evaluated and dealt with:

1. Connection to SVN service (test template storage)
2. Cron configuration (time based runs)
3. Companion scripts (wrappers and mail reminders from qam-script folder)

Initial evaluation¶

1. SVN repository is already accessible on both machine via NFS mount

2. A few cron entries with scripts from the repository exist:

   • qam_add_templates_to_svn.sh /srv/svn/checkouts/testreports 2>> /srv/svn/logs/generator.errors >> /srv/svn/logs/generator.out
   • check_for_unsent_reports.sh
   • update_git_repo.sh

   The first one is relevant to this issue and needs to be changed.

3. From all scripts inside the repository, only qam_add_templates_to_svn.sh interacts directly with the template generator (invoking it), the rest is just interacting with the SVN repository. The script was simplified once (during the last template generator major update) and could be simplified more. It is also possible to integrate it inside the template generator wrapper itself.
   The functionality includes:

   • making sure only one instance is running via PID file
   • retrieving RRs via osc --apiurl https://api.suse.de review list
   • checking log file existence
   • generating log file via invoking /usr/bin/qam_template (template generator wrapper)
   • adding the newly generated directory into svn via svn add

Setting due date based on mean cycle time of SUSE QE Tools

I found a few regressions (mainly in svn access parts). All should be fixed and the new version is reenabled. Let's wait and see if any issue resurfaces.