v2025.11

This release has two new features:

For packages which are "prefailed", the reason for failing or skipping them (e.g. why the package is marked BROKEN) are recorded and shown. Click on a "prefailed" or "indirect-prefailed" package to see it. Note that this data will only be supported for builds after the release.

Maintainer email addresses are now clickable. The detail page for each mantainer is fairly basic now, mainly providing links to packages maintained by that person. Please share suggestions for how it could be improved.

v2025.9

This release has a few smaller changes and a security update:

• Bump xz library to resolve a security issue when decoding malformed xz files
• In the search field, the literal string you enter is now added after the autocomplete entries
• Some dependencies have been removed, for faster compilation and a smaller binary

v2025.6

Broaden sentinel package selector.

In addition to bulk-test-boost etc., there are also the bulk-small, bulk-medium and bulk-large meta packages.
Change the selector for sentinel packages to cover meta-pkgs/bulk-*, so that the status for these is also shown.

Also in this release: dependency updates

v2025.5.1

This contains a fix for issue #93. There should be fewer "deadline exceeded" errors when fetching build logs in the background -- and if there are, we show a nicer error message instead.

Thanks @acirep for your contribution!

2025.5

The previous release added an iframe for getting build logs. Unfortunately, it is not allowed to iframe HTTP URLs from an app served via HTTPS, so this did not always work.

In this release, @acirep added code (#92) to send build logs for failed builds as part of the response to circumvent this issue. Also, we only show log buttons for logs that actually exist. For instance, if the package failed during build, we do not show a link to the non-existent install.log.

Other changes:

• Updated dependencies
• Fixed some typos

v2025.3

• Better filters! On the "builds" page (https://releng.netbsd.org/bulktracker/builds) and on the result page for individual packages, you can now use structured filters for OS, version, branch and more.
• Simple iframe log viewer. When showing an individual build results, build logs now open in an overlay, with an option to open them in a new tab.

Both of these features were contributed by the wonderful @acirep, thank you!

In addition, there were some internal updates:

• Now built with Go 1.24
• some dependency updates
• bug fixes and cleanups

v2025.2.1

Fix display of bulk-test-* table by @acirep in #83

v2025.2

Headline feature of this release is support for package maintainers! The maintainer of each package, as it was when the package was built, is now shown in most package data. This was contributed by a new contributor to the project, @acirep. Thank you!

Other changes

• The version is now shown at the bottom of each page.
• Various dependencies were updated. Some of them have security fixes, but AFAICT they do not concern this code.
• Debug logs are less noisy.
• Some instructions for getting started in the README file.

New Contributors

• @acirep made their first contribution in #76

v2024.9

Correct counting of indirect-failed packages, matching what pbulk does. See #70 and #72 for details. This means you won't see "indirect-failed" packages under failed dependencies any more. At least for new builds! Old ones will still use the old method.

Other changes:

• Build requires Go 1.22 now.
• Lots of cleanups, removing obsolete code and unused dependencies.

v2024.8

• New feature: show status of "sentinel packages" (i.e. meta-pkgs/bulk-test-*) prominently on the build results page, along with links to their failed dependencies (#71).
• Invert the order of tables on the package results page: show failed dependencies above other packages broken by this one, since it's arguably more important.
• Fix one bug that would have caused tables to remain in "Loading" state forever when there are no results to show.
• Add an internal handler allowing to delete details of a bulk build.
• refactorings and internal cleanups