Taskcluster

GENERAL

▶ [patch] [6237](https://github.com/taskcluster/taskcluster/issues/6237)
Fix the case where a generic worker won't upload its log on a malformed payload error. This has been broken since v48.2.0 from PR [6107](https://github.com/taskcluster/taskcluster/pull/6107).

GENERAL

▶ [minor]
Migrate [d2g](https://github.com/taskcluster/d2g) to `tools/d2g`.

▶ [patch]
Stop running docker-worker tests in the CI.

The tests will remain in the monorepo because we'll look into using them with generic worker once d2g is integrated.

▶ [patch]
Upgrade Node.js version to 18.16.1 (security release).

More information can be found [here](https://nodejs.org/en/blog/vulnerability/june-2023-security-releases).

ADMINS

▶ [minor] [6142](https://github.com/taskcluster/taskcluster/issues/6142)
Worker manager stops instances that are not active in queue after short timeout.
This is to prevent instances from running when worker fails to start claiming work or dies and does not reclaims task.

USERS

▶ [minor] [5994](https://github.com/taskcluster/taskcluster/issues/5994)
Generic Worker: Adds `task.payload.feature.loopbackVideo` for loopback video device support on Linux.

The `v4l2loopback` kernel module must be installed on the host system for this feature to work, although it does not _need_ to be loaded. Generic Worker loads the module with `modprobe` and generates the virtual video device with a `v4l2loopback` command. Under the multiuser engine, it also manages file ownership of the device with `chown` to ensure that only tasks with suitable scopes have read/write access to the virtual device.

For tasks that enable the feature, the virtual video device location will be provided to the task commands via the environment variable `TASKCLUSTER_VIDEO_DEVICE`. The value of the environment variable depends on deployment configuration, and therefore tasks should not assume a fixed value. Its value will however take the form `/dev/video<DEVICE_NUMBER>` where `<DEVICE_NUMBER>` is an integer between 0 and 255. The Generic Worker config setting `loopbackVideoDeviceNumber` may be used to change the device number. Future releases of Generic Worker may provide the capability of having more than one virtual video device; currently only one virtual video device is supported.

▶ [patch] [6326](https://github.com/taskcluster/taskcluster/issues/6326)
Running `taskcluster group list` without a task group ID now outputs error message:


Error: list expects argument <taskGroupId>


Previously, it incorrectly outputted:


Error: list expects argument <taskId>

GENERAL

▶ [minor]
This essentially reverts the change in [6279](https://github.com/taskcluster/taskcluster/pull/6279).

We learned from RelOps that the simple engine is useful for running generic worker inside a VM and inside of docker containers.

▶ [patch]
Upgrade to go 1.19.10.

> go1.19.10 (released 2023-06-06) includes four security fixes to the cmd/go and runtime packages, as well as bug fixes to the compiler, the go command, and the runtime.

ADMINS

▶ [minor] [6247](https://github.com/taskcluster/taskcluster/issues/6247)
Revert worker-manager from quarantining workers on removal that was introduced in [PR 6267](https://github.com/taskcluster/taskcluster/pull/6267).

USERS

▶ [MAJOR]
Rework the interactive feature for generic worker allowing to run interactive commands in it

▶ [patch]
Introduced `github.renderTaskclusterYml` endpoint to render provided `.taskcluster.yml` file for various events.
This might be used for debug purposes or to validate the .taskcluster.yml file
and make sure that resulting tasks and scopes produce expected values.

DEVELOPERS

▶ [patch]
Enables CORS for API for local docker-compose development.

OTHER

▶ Additional change not described here: [6280](https://github.com/taskcluster/taskcluster/issues/6280).

GENERAL

▶ [MAJOR] [6277](https://github.com/taskcluster/taskcluster/issues/6277)
Generic Worker Simple engine is no longer _released_. It can still be built from source, but since it was never intended to be used as a production engine, and was only intended to support development (e.g. for running unit tests or running in a simple dev deployment) the simple engine binaries are no longer released.

WORKER-DEPLOYERS

▶ [patch] [5006](https://github.com/taskcluster/taskcluster/issues/5006)
Generic Worker on macOS now dumps the output of the `last` command when it is not able to determine the logged in console user. This doesn't solve issue 5006 but it may provide additional troubleshooting information.

USERS

▶ [patch] [6278](https://github.com/taskcluster/taskcluster/issues/6278)
Fix UI issue showing "Response code 404" for missing `public/actions.json` artifact.

▶ [patch] [5807](https://github.com/taskcluster/taskcluster/issues/5807)
Fixes escape sequence parsing in logs that are attached to github check runs.

ADMINS

▶ [minor] [6247](https://github.com/taskcluster/taskcluster/issues/6247)
Worker manager now also quarantines worker on `removeWorker` call. This is used to prevent some race conditions when worker is still polling for new work and is removed/shutdown at the same time.

USERS

▶ [patch]
The new (unused in production) indexed artifacts feature of Generic Worker was broken in release 51.0.0. This has (hopefully) been fixed.

DEVELOPERS

▶ [patch]
New `.taskcuster.yml` linter added in UI to help validate github integration.

▶ [patch]
Taskcluster YAML validator can load file from URL.