@emaste you are correct / needs escaping in regex pattern groups.

Change the regex for both OSRELEASE and VOLUME_LABEL.

In D54277#1240322, @emaste wrote:

This seems a bit strange - BRANCH should be coming out of newvers.sh and be something like BRANCH="CURRENT" (unless BRANCH_OVERRIDE is set). How is pull/XXXX making its way in?

I think CIRRUS-CI also has an environment variable named BRANCH.

Just in case I created PR and it was fired into our persistent worker.

In D54247#1239853, @lwhsu wrote:

There is no tar cvf ${tardev} -C ${metadir} . part in the "$freebsdci_type" = "smoke" path, will that be a problem?

Address the issue brought by @lshsu. Get env output in CI for smoke tests too.

In D54247#1239856, @lwhsu wrote:

In D54247#1239853, @lwhsu wrote:

There is no tar cvf ${tardev} -C ${metadir} . part in the "$freebsdci_type" = "smoke" path, will that be a problem?

Other than this I think this is fine. I would prefer separating the logic of handling meta file/device to other routines, but that can be done later.

1. Updating D54220: .cirrus.yml: Add persistent worker #
2. Enter a brief description of the changes included in this update.
3. The first line is used as subject, next lines as comment. #
4. If you intended to create a new revision, use:
5. $ arc diff --create

While committing please add the MFH marker. Like MFH: 2025Q4. And also remove the dots at the end of the DEPRECATED.

DEPRECATED without EXPIRATION_DATE is pointless. Please follow this procedure:

1. Starting with the oldest one put an EXPIRATION_DATE of 30 days ahead. Like openjdk18 30D+NOW. OpenJDK19 60D+NOW and onwards.
2. Make sure that every ports has a PORTREVISION bump. So that any users who needs/uses this also needs to reinstall the ports and get a notification that their used ports are getting removed.
3. Also merge quarterly.