Taskcluster

GENERAL

▶ [patch] [bug 1631824](http://bugzil.la/1631824)
The worker-manager azure provider now properly tracks and deletes all disks when a virtual machine has data disks created for it.

DEPLOYERS

▶ [patch]
A bug in the Azure provider which caused provisioning to fail when handling operations has been fixed.

▶ [patch]
Taskcluster services now include metadata at the top level of Fields for `generic.*` logging messages, rather than in `meta` or `fields` sub-properties.

WORKER-DEPLOYERS

▶ [patch] [2969](https://github.com/taskcluster/taskcluster/issues/2969)
Docker-worker now only considers itself idle if its call to `queue.claimWork` returns no tasks. This prevents the situation where a very short `afterIdleSeconds` causes the worker to shut down *while* calling `claimWork`.

▶ [patch] [2925](https://github.com/taskcluster/taskcluster/issues/2925)
Listing workers in the "stopping" state will no longer cause 500 errors.

USERS

▶ [patch] [bug 1632929](http://bugzil.la/1632929)
Taskcluster-Github now uses a release event's `target_commitish` property instead of the `tag` property to determine the SHA of the released commit. This is important in cases where tags are created as part of the release-creation call, as GitHub sends the release event before the tag is created.

DEVELOPERS

▶ [patch] [bug 1636167](http://bugzil.la/1636167)
CI tasks are now generated in a decision task by https://hg.mozilla.org/ci/taskgraph

OTHER

▶ Additional changes not described here: [bug 1640267](http://bugzil.la/1640267), [#2827](https://github.com/taskcluster/taskcluster/issues/2827), [#2890](https://github.com/taskcluster/taskcluster/issues/2890), [#2912](https://github.com/taskcluster/taskcluster/issues/2912), [#2913](https://github.com/taskcluster/taskcluster/issues/2913), [#2951](https://github.com/taskcluster/taskcluster/issues/2951), [#2952](https://github.com/taskcluster/taskcluster/issues/2952), [bug 1634376](http://bugzil.la/1634376).

USERS

▶ [patch]
An incorrect use of a relative path caused sign-ins to fail in v30.0.1. This has been fixed.

▶ [patch]
Fix docker worker not working in the latest release of Taskcluster. It was
previously throwing `taskVolumeBindings is not iterable`.

▶ [patch] [2876](https://github.com/taskcluster/taskcluster/issues/2876)
The purge cache UI view now allows filtering a search result by cache name.

OTHER

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

DEPLOYERS

▶ [patch]
A typo causing index service not to start up in 30.0.0 is now fixed.

GENERAL

▶ [patch] [bug 1638047](http://bugzil.la/1638047)
This release fixes a bug where the web UI opens the log viewer for any `text/plain` artifacts, which breaks for private artifacts. The web UI will now only use the log viewer for `text/plain` `*.log` files.

▶ [patch] [bug 1587145](http://bugzil.la/1587145)
taskcluster-client-web now only builds a single umd asset. This asset is
compatible with both cjs and esm.

DEPLOYERS

▶ [minor]
Database version 11 removes the `widgets` table that was used to test Postgres deployment. It contains no useful data.
The hidden `notify.updateWidgets` API method, but this method was never meant to be used so this removal is not considered a breaking change.

▶ [patch] [bug 1639913](http://bugzil.la/1639913)
Worker-manager now logs when a worker is removed, and includes debug logging of provisioning and scanning.

WORKER-DEPLOYERS

▶ [MAJOR] [bug 1636321](http://bugzil.la/1636321)
The generic-worker configuration parameters `livelogKey`, `livelogCertificate`, `livelogGETPort`, `livelogPUTPort`, and `livelogSecret` are no longer needed and are prohibited in the worker's configuration.

▶ [minor] [2861](https://github.com/taskcluster/taskcluster/issues/2861)
The unused and unmaintained docker-worker features balrogVPNProxy, balrogStagingVPNProxy, and relengAPIProxy have been removed.

▶ [patch] [bug 1638370](http://bugzil.la/1638370)
Azure provider no longer has a race condition between `registerWorker` and `checkWorker`.

▶ [patch]
Docker-worker will now fail early with a useful error message if the loopback audio or video devices are not available, but are configured.

▶ [patch]
The docker-worker version is now logged in the `serviceContext.version` property of its structured logs.

ADMINS

▶ [patch] [bug 1627769](http://bugzil.la/1627769)
Worker lifecycle defaults are now being properly applied.

USERS

▶ [patch] [1061](https://github.com/taskcluster/taskcluster/issues/1061)
In client-shell added flag --verbose/-v for getting log to stderr for all the commands.

▶ [patch]
The docker-worker payload format is now available in Taskcluster's online documentation.

DEVELOPERS

▶ [patch] [2844](https://github.com/taskcluster/taskcluster/issues/2844)
All services are now invoked from the root of the monorepo directory.

OTHER

▶ Additional changes not described here: [bug 1636164](http://bugzil.la/1636164), [bug 1636174](http://bugzil.la/1636174), [#2822](https://github.com/taskcluster/taskcluster/issues/2822), [#2838](https://github.com/taskcluster/taskcluster/issues/2838), [#2844](https://github.com/taskcluster/taskcluster/issues/2844).

USERS

▶ [minor] [bug 1638002](http://bugzil.la/1638002)
The Azure, AWS, and Google worker provisioners now use an instance's region or location as `workerGroup`, instead of the worker pool's `providerId`.

DEVELOPERS

▶ [minor] [2811](https://github.com/taskcluster/taskcluster/issues/2811)
The Queue schema now allows for ssh:// source urls.

▶ [patch]
An issue with building external urls with traceId'd clients has been fixed

OTHER

▶ Additional change not described here: [bug 1637982](http://bugzil.la/1637982).