Releases: taskcluster/generic-worker
v13.0.3
In v13.0.3 since v13.0.2
v13.0.2
In v13.0.2 since v12.0.0
The backwardly incompatible change for version 13 is that AWS provisioner worker type definitions no longer
store generic-worker secrets. Instead, the secrets should be placed in a taskcluster secrets secret called
worker-type:aws-provisioner-v1/<workerType>. The secret could look something like this:
config:
livelogSecret: <secret key>
files:
- content: >-
<base64>
description: SSL certificate for livelog
encoding: base64
format: file
path: 'C:\generic-worker\livelog.crt'
- content: >-
<base64>
description: SSL key for livelog
encoding: base64
format: file
path: 'C:\generic-worker\livelog.key'
The secrets section of the AWS provisioner worker type definition should be an empty json object:
"secrets": {}Now the userdata section of the worker type definition should contain the remaining (non-secret) configuration, e.g.
"userData": {
"genericWorker": {
"config": {
"deploymentId": "axlvK6p9SNa-HJgPCVXKEA",
"ed25519SigningKeyLocation": "C:\\generic-worker\\generic-worker-ed25519-signing-key.key",
"idleTimeoutSecs": 60,
"livelogCertificate": "C:\\generic-worker\\livelog.crt",
"livelogExecutable": "C:\\generic-worker\\livelog.exe",
"livelogKey": "C:\\generic-worker\\livelog.key",
"openpgpSigningKeyLocation": "C:\\generic-worker\\generic-worker-gpg-signing-key.key",
"shutdownMachineOnInternalError": false,
"subdomain": "taskcluster-worker.net",
"taskclusterProxyExecutable": "C:\\generic-worker\\taskcluster-proxy.exe",
"workerTypeMetadata": {
"machine-setup": {
"maintainer": "pmoore@mozilla.com",
"script": "https://raw.githubusercontent.com/taskcluster/generic-worker/53f1d934688f9e9c6ba60db6cc9185e5c9e9c0ce/worker_types/nss-win2012r2/userdata"
}
}
}
}
},
v13.0.1
v13.0.0
v12.0.0
In v12.0.0 since v11.1.1
The backwardly incompatible change for version 12 is that you need to create both a openpgp signing key
and an ed25519 signing key before running the worker.
generic-worker new-ed25519-keypair --file ED25519-PRIVATE-KEY-FILE
generic-worker new-openpgp-keypair --file OPENPGP-PRIVATE-KEY-FILE
Note, both are required.
The config property signingKeyLocation has been renamed to openpgpSigningKeyLocation and the new config property
ed25519SigningKeyLocation is needed. For example, could changes could look like this:
- "signingKeyLocation": "C:\\generic-worker\\generic-worker-gpg-signing-key.key",
+ "openpgpSigningKeyLocation": "C:\\generic-worker\\generic-worker-gpg-signing-key.key",
+ "ed25519SigningKeyLocation": "C:\\generic-worker\\generic-worker-ed25519-signing-key.key",v11.1.1
In v11.1.1 since v11.1.0
v11.1.0
In v11.1.0 since v11.0.1
v11.0.1
In v11.0.1 since v11.0.0
v11.0.0
In v11.0.0 since v10.11.3
The backwardly incompatible change for version 11 is that you need to specify --configure-for-aws
at installation time, if the workers will run in AWS. Previously, this was assumed to always be
the case.
generic-worker install service [--nssm NSSM-EXE]
[--service-name SERVICE-NAME]
[--config CONFIG-FILE]
[--configure-for-aws]
v10.11.2alpha1
WIP