Skip to main content

2022-q4

A quiet quarter: safer output directory names, Jenkins runners configurable from environment variables, a cap on the size of tuning batches, and backend stability tweaks.

Project integration

Jenkins runner configuration from the environment

The Jenkins runner can now read its build URL and token from QA_RUNNERS_JENKINS_BUILD_URL and QA_RUNNERS_JENKINS_TOKEN, so they don't have to live in qaboard.yaml. The token is now optional.

Learn more →

Web app​

  • Tuning from the web app is now limited to 5000 runs per batch, and the form says so.
  • The CI integrations menu refreshes statuses as soon as it opens, and links to Jenkins builds open the build page.
  • Runs aborted before writing their file manifest now get one when you open them.
  • Logs with stray < characters are now displayed correctly.

CLI and project setup​

  • Output directory names derived from input paths are now always slugified, avoiding characters that cause problems on some filesystems. New runs of inputs with such characters get a different output directory.

Server and administration​

  • The backend recycles its workers after a number of requests, a maximum lifetime or too much memory use, and nginx waits up to 10 minutes for slow API calls.
  • Several API endpoints and webhooks read database rows in chunks to use less memory.
  • Exports to a folder now report when they fail to create symlinks.