queue

type AzureArtifactRequest struct {

	// Artifact mime-type, when uploading artifact please use the same
	// `Content-Type`, consistently using the correct mime-type make
	// tooling a lot easier, specifically, always using `application/json`
	// for JSON artifacts.
	//
	// Max length: 255
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[1]/properties/contentType
	ContentType string `json:"contentType"`

	// Date-time after which the artifact should be deleted.
	// Note, that these will be collected over time, and artifacts may
	// remain available after expiration. Azure based artifacts are
	// identified in azure table storage and explicitly deleted in the
	// azure storage container after expiration.
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[1]/properties/expires
	Expires tcclient.Time `json:"expires"`

	// Artifact storage type, in this case `azure`
	//
	// Possible values:
	//   * "azure"
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[1]/properties/storageType
	StorageType string `json:"storageType"`
}

type AzureArtifactResponse struct {

	// Artifact mime-type, should be specified with the
	// `x-ms-blob-content-type` when committing the block.
	//
	// Max length: 255
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[1]/properties/contentType
	ContentType string `json:"contentType"`

	// Date-time after which Shared Access Signature (SAS) will
	// seize to work.
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[1]/properties/expires
	Expires tcclient.Time `json:"expires"`

	// Shared Access Signature (SAS) with write permissions, see
	// [Azure REST API]
	// (http://msdn.microsoft.com/en-US/library/azure/dn140256.aspx)
	// reference for details on how to use this.
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[1]/properties/putUrl
	PutURL string `json:"putUrl"`

	// Artifact storage type, in this case `azure`
	//
	// Possible values:
	//   * "azure"
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[1]/properties/storageType
	StorageType string `json:"storageType"`
}

type ClaimWorkRequest struct {

	// Number of tasks to attempt to claim.
	//
	// Default:    1
	// Mininum:    1
	// Maximum:    32
	//
	// See http://schemas.taskcluster.net/queue/v1/claim-work-request.json#/properties/tasks
	Tasks int `json:"tasks"`

	// Identifier for group that worker claiming the task is a part of.
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/claim-work-request.json#/properties/workerGroup
	WorkerGroup string `json:"workerGroup"`

	// Identifier for worker within the given workerGroup
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/claim-work-request.json#/properties/workerId
	WorkerID string `json:"workerId"`
}

type ClaimWorkResponse struct {

	// List of task claims, may be empty if no tasks was claimed, in which case
	// the worker should sleep a tiny bit before polling again.
	//
	// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks
	Tasks []struct {

		// Temporary credentials granting `task.scopes` and the scope:
		// `queue:claim-task:<taskId>/<runId>` which allows the worker to reclaim
		// the task, upload artifacts and report task resolution.
		//
		// The temporary credentials are set to expire after `takenUntil`. They
		// won't expire exactly at `takenUntil` but shortly after, hence, requests
		// coming close `takenUntil` won't have problems even if there is a little
		// clock drift.
		//
		// Workers should use these credentials when making requests on behalf of
		// a task. This includes requests to create artifacts, reclaiming the task
		// reporting the task `completed`, `failed` or `exception`.
		//
		// Note, a new set of temporary credentials is issued when the worker
		// reclaims the task.
		//
		// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/credentials
		Credentials struct {

			// The `accessToken` for the temporary credentials.
			//
			// Min length: 1
			//
			// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/credentials/properties/accessToken
			AccessToken string `json:"accessToken"`

			// The `certificate` for the temporary credentials, these are required
			// for the temporary credentials to work.
			//
			// Min length: 1
			//
			// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/credentials/properties/certificate
			Certificate string `json:"certificate"`

			// The `clientId` for the temporary credentials.
			//
			// Min length: 1
			//
			// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/credentials/properties/clientId
			ClientID string `json:"clientId"`
		} `json:"credentials"`

		// `run-id` assigned to this run of the task
		//
		// Mininum:    0
		// Maximum:    1000
		//
		// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/runId
		RunID int `json:"runId"`

		// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/status
		Status TaskStatusStructure `json:"status"`

		// Time at which the run expires and is resolved as `exception`,
		// with reason `claim-expired` if the run haven't been reclaimed.
		//
		// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/takenUntil
		TakenUntil tcclient.Time `json:"takenUntil"`

		// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/task
		Task TaskDefinitionResponse `json:"task"`

		// Identifier for the worker-group within which this run started.
		//
		// Syntax:     ^([a-zA-Z0-9-_]*)$
		// Min length: 1
		// Max length: 22
		//
		// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/workerGroup
		WorkerGroup string `json:"workerGroup"`

		// Identifier for the worker executing this run.
		//
		// Syntax:     ^([a-zA-Z0-9-_]*)$
		// Min length: 1
		// Max length: 22
		//
		// See http://schemas.taskcluster.net/queue/v1/claim-work-response.json#/properties/tasks/items/properties/workerId
		WorkerID string `json:"workerId"`
	} `json:"tasks"`
}

type CountPendingTasksResponse struct {

	// An approximate number of pending tasks for the given `provisionerId` and
	// `workerType`. This is based on Azure Queue Storage meta-data API, thus,
	// number of reported here may be higher than actual number of pending tasks.
	// But there cannot be more pending tasks reported here. Ie. this is an
	// **upper-bound** on the number of pending tasks.
	//
	// Mininum:    0
	//
	// See http://schemas.taskcluster.net/queue/v1/pending-tasks-response.json#/properties/pendingTasks
	PendingTasks int `json:"pendingTasks"`

	// Unique identifier for the provisioner
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/pending-tasks-response.json#/properties/provisionerId
	ProvisionerID string `json:"provisionerId"`

	// Identifier for worker type within the specified provisioner
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/pending-tasks-response.json#/properties/workerType
	WorkerType string `json:"workerType"`
}

type ErrorArtifactRequest struct {

	// Date-time after which the queue should stop replying with the error
	// and forget about the artifact.
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[3]/properties/expires
	Expires tcclient.Time `json:"expires"`

	// Human readable explanation of why the artifact is missing
	//
	// Max length: 4096
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[3]/properties/message
	Message string `json:"message"`

	// Reason why the artifact doesn't exist.
	//
	// Possible values:
	//   * "file-missing-on-worker"
	//   * "invalid-resource-on-worker"
	//   * "too-large-file-on-worker"
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[3]/properties/reason
	Reason string `json:"reason"`

	// Artifact storage type, in this case `error`
	//
	// Possible values:
	//   * "error"
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[3]/properties/storageType
	StorageType string `json:"storageType"`
}

type ErrorArtifactResponse struct {

	// Artifact storage type, in this case `error`
	//
	// Possible values:
	//   * "error"
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[3]/properties/storageType
	StorageType string `json:"storageType"`
}

type ListArtifactsResponse struct {

	// List of artifacts for given `taskId` and `runId`.
	//
	// See http://schemas.taskcluster.net/queue/v1/list-artifacts-response.json#/properties/artifacts
	Artifacts []struct {

		// Mimetype for the artifact that was created.
		//
		// Max length: 255
		//
		// See http://schemas.taskcluster.net/queue/v1/list-artifacts-response.json#/properties/artifacts/items/properties/contentType
		ContentType string `json:"contentType"`

		// Date and time after which the artifact created will be automatically
		// deleted by the queue.
		//
		// See http://schemas.taskcluster.net/queue/v1/list-artifacts-response.json#/properties/artifacts/items/properties/expires
		Expires tcclient.Time `json:"expires"`

		// Name of the artifact that was created, this is useful if you want to
		// attempt to fetch the artifact.
		//
		// Max length: 1024
		//
		// See http://schemas.taskcluster.net/queue/v1/list-artifacts-response.json#/properties/artifacts/items/properties/name
		Name string `json:"name"`

		// This is the `storageType` for the request that was used to create
		// the artifact.
		//
		// Possible values:
		//   * "s3"
		//   * "azure"
		//   * "reference"
		//   * "error"
		//
		// See http://schemas.taskcluster.net/queue/v1/list-artifacts-response.json#/properties/artifacts/items/properties/storageType
		StorageType string `json:"storageType"`
	} `json:"artifacts"`

	// Opaque `continuationToken` to be given as query-string option to get the
	// next set of artifacts.
	// This property is only present if another request is necessary to fetch all
	// results. In practice the next request with a `continuationToken` may not
	// return additional results, but it can. Thus, you can only be sure to have
	// all the results if you've called with `continuationToken` until you get a
	// result without a `continuationToken`.
	//
	// See http://schemas.taskcluster.net/queue/v1/list-artifacts-response.json#/properties/continuationToken
	ContinuationToken string `json:"continuationToken,omitempty"`
}

type ListDependentTasksResponse struct {

	// Opaque `continuationToken` to be given as query-string option to get the
	// next set of dependent tasks.
	// This property is only present if another request is necessary to fetch all
	// results. In practice the next request with a `continuationToken` may not
	// return additional results, but it can. Thus, you can only be sure to have
	// all the results if you've called `listDependentTasks` with
	// `continuationToken` until you get a result without a `continuationToken`.
	//
	// See http://schemas.taskcluster.net/queue/v1/list-dependent-tasks-response.json#/properties/continuationToken
	ContinuationToken string `json:"continuationToken,omitempty"`

	// Identifier for the task whose dependents are being listed.
	//
	// Syntax:     ^[A-Za-z0-9_-]{8}[Q-T][A-Za-z0-9_-][CGKOSWaeimquy26-][A-Za-z0-9_-]{10}[AQgw]$
	//
	// See http://schemas.taskcluster.net/queue/v1/list-dependent-tasks-response.json#/properties/taskId
	TaskID string `json:"taskId"`

	// List of tasks that have `taskId` in the `task.dependencies` property.
	//
	// See http://schemas.taskcluster.net/queue/v1/list-dependent-tasks-response.json#/properties/tasks
	Tasks []struct {

		// See http://schemas.taskcluster.net/queue/v1/list-dependent-tasks-response.json#/properties/tasks/items/properties/status
		Status TaskStatusStructure `json:"status"`

		// See http://schemas.taskcluster.net/queue/v1/list-dependent-tasks-response.json#/properties/tasks/items/properties/task
		Task TaskDefinitionResponse `json:"task"`
	} `json:"tasks"`
}

type ListTaskGroupResponse struct {

	// Opaque `continuationToken` to be given as query-string option to get the
	// next set of tasks in the task-group.
	// This property is only present if another request is necessary to fetch all
	// results. In practice the next request with a `continuationToken` may not
	// return additional results, but it can. Thus, you can only be sure to have
	// all the results if you've called `listTaskGroup` with `continuationToken`
	// until you get a result without a `continuationToken`.
	//
	// See http://schemas.taskcluster.net/queue/v1/list-task-group-response.json#/properties/continuationToken
	ContinuationToken string `json:"continuationToken,omitempty"`

	// Identifier for the task-group being listed.
	//
	// Syntax:     ^[A-Za-z0-9_-]{8}[Q-T][A-Za-z0-9_-][CGKOSWaeimquy26-][A-Za-z0-9_-]{10}[AQgw]$
	//
	// See http://schemas.taskcluster.net/queue/v1/list-task-group-response.json#/properties/taskGroupId
	TaskGroupID string `json:"taskGroupId"`

	// List of tasks in this task-group.
	//
	// See http://schemas.taskcluster.net/queue/v1/list-task-group-response.json#/properties/tasks
	Tasks []struct {

		// See http://schemas.taskcluster.net/queue/v1/list-task-group-response.json#/properties/tasks/items/properties/status
		Status TaskStatusStructure `json:"status"`

		// See http://schemas.taskcluster.net/queue/v1/list-task-group-response.json#/properties/tasks/items/properties/task
		Task TaskDefinitionResponse `json:"task"`
	} `json:"tasks"`
}

type PollTaskUrlsResponse struct {

	// Date and time after which the signed URLs provided in this response
	// expires and not longer works for authentication.
	//
	// See http://schemas.taskcluster.net/queue/v1/poll-task-urls-response.json#/properties/expires
	Expires tcclient.Time `json:"expires"`

	// List of signed URLs for queues to poll tasks from, they must be called
	// in the order they are given. As the first entry in this array **may**
	// have higher priority.
	//
	// See http://schemas.taskcluster.net/queue/v1/poll-task-urls-response.json#/properties/queues
	Queues []struct {

		// Signed URL to delete messages that have been received using the
		// `signedPollUrl`. You **must** do this to avoid receiving the same
		// message again.
		// To use this URL you must substitute `{{messageId}}` and
		// `{{popReceipt}}` with `MessageId` and `PopReceipt` from the XML
		// response the `signedPollUrl` gave you. It is important that you
		// `encodeURIComponent` both `MessageId` and `PopReceipt` prior to
		// substitution, otherwise you will experience intermittent failures!
		// Note this URL only works with `DELETE` request.
		//
		// Syntax:     ^https://
		//
		// See http://schemas.taskcluster.net/queue/v1/poll-task-urls-response.json#/properties/queues/items/properties/signedDeleteUrl
		SignedDeleteURL string `json:"signedDeleteUrl"`

		// Signed URL to get message from the Azure Queue Storage queue,
		// that holds messages for the given `provisionerId` and `workerType`.
		// Note that this URL returns XML, see documentation for the Azure
		// Queue Storage
		// [REST API](http://msdn.microsoft.com/en-us/library/azure/dd179474.aspx)
		// for details.
		// When you have a message you can use `claimTask` to claim the task.
		// You will need to parse the XML reponse and base64 decode and
		// JSON parse the `MessageText`.
		// After you have called `claimTask` you **must** us the
		// `signedDeleteUrl` to delete the message.
		// **Remark**, you are allowed to append `&numofmessages=N`,
		// where N < 32, to the URLs if you wish to obtain more than one
		// message at the time.
		//
		// See http://schemas.taskcluster.net/queue/v1/poll-task-urls-response.json#/properties/queues/items/properties/signedPollUrl
		SignedPollURL string `json:"signedPollUrl"`
	} `json:"queues"`
}

type PostArtifactRequest json.RawMessage

type PostArtifactResponse json.RawMessage

type Queue tcclient.ConnectionData

type RedirectArtifactRequest struct {

	// Artifact mime-type for the resource to which the queue should
	// redirect. Please use the same `Content-Type`, consistently using
	// the correct mime-type make tooling a lot easier, specifically,
	// always using `application/json` for JSON artifacts.
	//
	// Max length: 255
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[2]/properties/contentType
	ContentType string `json:"contentType"`

	// Date-time after which the queue should no longer redirect to this URL.
	// Note, that the queue will and cannot delete the resource your URL
	// references, you are responsible for doing that yourself.
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[2]/properties/expires
	Expires tcclient.Time `json:"expires"`

	// Artifact storage type, in this case `reference`
	//
	// Possible values:
	//   * "reference"
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[2]/properties/storageType
	StorageType string `json:"storageType"`

	// URL to which the queue should redirect using a `303` (See other)
	// redirect.
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[2]/properties/url
	URL string `json:"url"`
}

type RedirectArtifactResponse struct {

	// Artifact storage type, in this case `reference`
	//
	// Possible values:
	//   * "reference"
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[2]/properties/storageType
	StorageType string `json:"storageType"`
}

type S3ArtifactRequest struct {

	// Artifact mime-type, when uploading artifact to the signed
	// `PUT` URL returned from this request this must given with the
	//  `ContentType` header. Please, provide correct mime-type,
	//  this make tooling a lot easier, specifically,
	//  always using `application/json` for JSON artifacts.
	//
	// Max length: 255
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[0]/properties/contentType
	ContentType string `json:"contentType"`

	// Date-time after which the artifact should be deleted. Note, that
	// these will be collected over time, and artifacts may remain
	// available after expiration. S3 based artifacts are identified in
	// azure table storage and explicitly deleted on S3 after expiration.
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[0]/properties/expires
	Expires tcclient.Time `json:"expires"`

	// Artifact storage type, in this case `'s3'`
	//
	// Possible values:
	//   * "s3"
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-request.json#/oneOf[0]/properties/storageType
	StorageType string `json:"storageType"`
}

type S3ArtifactResponse struct {

	// Artifact mime-type, must be specified as header when uploading with
	// the signed `putUrl`.
	//
	// Max length: 255
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[0]/properties/contentType
	ContentType string `json:"contentType"`

	// Date-time after which the signed `putUrl` no longer works
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[0]/properties/expires
	Expires tcclient.Time `json:"expires"`

	// URL to which a `PUT` request can be made to upload the artifact
	// requested. Note, the `Content-Length` must be specified correctly,
	// and the `ContentType` header must be set the value specified below.
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[0]/properties/putUrl
	PutURL string `json:"putUrl"`

	// Artifact storage type, in this case `'s3'`
	//
	// Possible values:
	//   * "s3"
	//
	// See http://schemas.taskcluster.net/queue/v1/post-artifact-response.json#/oneOf[0]/properties/storageType
	StorageType string `json:"storageType"`
}

type TaskClaimRequest struct {

	// Identifier for group that worker claiming the task is a part of.
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task-claim-request.json#/properties/workerGroup
	WorkerGroup string `json:"workerGroup"`

	// Identifier for worker within the given workerGroup
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task-claim-request.json#/properties/workerId
	WorkerID string `json:"workerId"`
}

type TaskClaimResponse struct {

	// Temporary credentials granting `task.scopes` and the scope:
	// `queue:claim-task:<taskId>/<runId>` which allows the worker to reclaim
	// the task, upload artifacts and report task resolution.
	//
	// The temporary credentials are set to expire after `takenUntil`. They
	// won't expire exactly at `takenUntil` but shortly after, hence, requests
	// coming close `takenUntil` won't have problems even if there is a little
	// clock drift.
	//
	// Workers should use these credentials when making requests on behalf of
	// a task. This includes requests to create artifacts, reclaiming the task
	// reporting the task `completed`, `failed` or `exception`.
	//
	// Note, a new set of temporary credentials is issued when the worker
	// reclaims the task.
	//
	// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/credentials
	Credentials struct {

		// The `accessToken` for the temporary credentials.
		//
		// Min length: 1
		//
		// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/credentials/properties/accessToken
		AccessToken string `json:"accessToken"`

		// The `certificate` for the temporary credentials, these are required
		// for the temporary credentials to work.
		//
		// Min length: 1
		//
		// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/credentials/properties/certificate
		Certificate string `json:"certificate"`

		// The `clientId` for the temporary credentials.
		//
		// Min length: 1
		//
		// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/credentials/properties/clientId
		ClientID string `json:"clientId"`
	} `json:"credentials"`

	// `run-id` assigned to this run of the task
	//
	// Mininum:    0
	// Maximum:    1000
	//
	// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/runId
	RunID int `json:"runId"`

	// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/status
	Status TaskStatusStructure `json:"status"`

	// Time at which the run expires and is resolved as `exception`,
	// with reason `claim-expired` if the run haven't been reclaimed.
	//
	// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/takenUntil
	TakenUntil tcclient.Time `json:"takenUntil"`

	// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/task
	Task TaskDefinitionResponse `json:"task"`

	// Identifier for the worker-group within which this run started.
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/workerGroup
	WorkerGroup string `json:"workerGroup"`

	// Identifier for the worker executing this run.
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task-claim-response.json#/properties/workerId
	WorkerID string `json:"workerId"`
}

type TaskDefinitionRequest struct {

	// Creation time of task
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/created
	Created tcclient.Time `json:"created"`

	// Deadline of the task, `pending` and `running` runs are
	// resolved as **exception** if not resolved by other means
	// before the deadline. Note, deadline cannot be more than
	// 5 days into the future
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/deadline
	Deadline tcclient.Time `json:"deadline"`

	// List of dependent tasks. These must either be _completed_ or _resolved_
	// before this task is scheduled. See `requires` for semantics.
	//
	// Default:    []
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/dependencies
	Dependencies []string `json:"dependencies,omitempty"`

	// Task expiration, time at which task definition and status is deleted.
	// Notice that all artifacts for the task must have an expiration that is no
	// later than this. If this property isn't it will be set to `deadline`
	// plus one year (this default may subject to change).
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/expires
	Expires tcclient.Time `json:"expires,omitempty"`

	// Object with properties that can hold any kind of extra data that should be
	// associated with the task. This can be data for the task which doesn't
	// fit into `payload`, or it can supplementary data for use in services
	// listening for events from this task. For example this could be details to
	// display on _treeherder_, or information for indexing the task. Please, try
	// to put all related information under one property, so `extra` data keys
	// for treeherder reporting and task indexing don't conflict, hence, we have
	// reusable services. **Warning**, do not stuff large data-sets in here,
	// task definitions should not take-up multiple MiBs.
	//
	// Default:    map[]
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/extra
	Extra json.RawMessage `json:"extra,omitempty"`

	// Required task metadata
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/metadata
	Metadata struct {

		// Human readable description of the task, please **explain** what the
		// task does. A few lines of documentation is not going to hurt you.
		//
		// Max length: 32768
		//
		// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/metadata/properties/description
		Description string `json:"description"`

		// Human readable name of task, used to very briefly given an idea about
		// what the task does.
		//
		// Max length: 255
		//
		// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/metadata/properties/name
		Name string `json:"name"`

		// E-mail of person who caused this task, e.g. the person who did
		// `hg push`. The person we should contact to ask why this task is here.
		//
		// Max length: 255
		//
		// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/metadata/properties/owner
		Owner string `json:"owner"`

		// Link to source of this task, should specify a file, revision and
		// repository. This should be place someone can go an do a git/hg blame
		// to who came up with recipe for this task.
		//
		// Max length: 4096
		//
		// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/metadata/properties/source
		Source string `json:"source"`
	} `json:"metadata"`

	// Task-specific payload following worker-specific format. For example the
	// `docker-worker` requires keys like: `image`, `commands` and
	// `features`. Refer to the documentation of `docker-worker` for details.
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/payload
	Payload json.RawMessage `json:"payload"`

	// Priority of task, this defaults to `normal`. Additional levels may be
	// added later.
	// **Task submitter required scopes** `queue:task-priority:high` for high
	// priority tasks.
	//
	// Possible values:
	//   * "high"
	//   * "normal"
	//
	// Default:    "normal"
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/priority
	Priority string `json:"priority,omitempty"`

	// Unique identifier for a provisioner, that can supply specified
	// `workerType`
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/provisionerId
	ProvisionerID string `json:"provisionerId"`

	// The tasks relation to its dependencies. This property specifies the
	// semantics of the `task.dependencies` property.
	// If `all-completed` is given the task will be scheduled when all
	// dependencies are resolved _completed_ (successful resolution).
	// If `all-resolved` is given the task will be scheduled when all dependencies
	// have been resolved, regardless of what their resolution is.
	//
	// Possible values:
	//   * "all-completed"
	//   * "all-resolved"
	//
	// Default:    "all-completed"
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/requires
	Requires string `json:"requires,omitempty"`

	// Number of times to retry the task in case of infrastructure issues.
	// An _infrastructure issue_ is a worker node that crashes or is shutdown,
	// these events are to be expected.
	//
	// Default:    5
	// Mininum:    0
	// Maximum:    49
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/retries
	Retries int `json:"retries,omitempty"`

	// List of task specific routes, AMQP messages will be CC'ed to these routes.
	// **Task submitter required scopes** `queue:route:<route>` for
	// each route given.
	//
	// Default:    []
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/routes
	Routes []string `json:"routes,omitempty"`

	// Identifier for the scheduler that _defined_ this task, this can be an
	// identifier for a user or a service like the `"task-graph-scheduler"`.
	// **Task submitter required scopes**
	// `queue:assume:scheduler-id:<schedulerId>/<taskGroupId>`.
	// This scope is also necessary to _schedule_ a defined task, or _rerun_ a
	// task.
	//
	// Default:    "-"
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/schedulerId
	SchedulerID string `json:"schedulerId,omitempty"`

	// List of scopes (or scope-patterns) that the task is
	// authorized to use.
	//
	// Default:    []
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/scopes
	Scopes []string `json:"scopes,omitempty"`

	// Arbitrary key-value tags (only strings limited to 4k). These can be used
	// to attach informal meta-data to a task. Use this for informal tags that
	// tasks can be classified by. You can also think of strings here as
	// candidates for formal meta-data. Something like
	// `purpose: 'build' || 'test'` is a good example.
	//
	// Default:    map[]
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/tags
	Tags json.RawMessage `json:"tags,omitempty"`

	// Identifier for a group of tasks scheduled together with this task, by
	// scheduler identified by `schedulerId`. For tasks scheduled by the
	// task-graph scheduler, this is the `taskGraphId`.  Defaults to `taskId` if
	// property isn't specified.
	//
	// Syntax:     ^[A-Za-z0-9_-]{8}[Q-T][A-Za-z0-9_-][CGKOSWaeimquy26-][A-Za-z0-9_-]{10}[AQgw]$
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/taskGroupId
	TaskGroupID string `json:"taskGroupId,omitempty"`

	// Unique identifier for a worker-type within a specific provisioner
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/create-task-request.json#/properties/workerType
	WorkerType string `json:"workerType"`
}

type TaskDefinitionResponse struct {

	// Creation time of task
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/created
	Created tcclient.Time `json:"created"`

	// Deadline of the task, `pending` and `running` runs are
	// resolved as **exception** if not resolved by other means
	// before the deadline. Note, deadline cannot be more than
	// 5 days into the future
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/deadline
	Deadline tcclient.Time `json:"deadline"`

	// List of dependent tasks. These must either be _completed_ or _resolved_
	// before this task is scheduled. See `requires` for semantics.
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/dependencies
	Dependencies []string `json:"dependencies"`

	// Task expiration, time at which task definition and status is deleted.
	// Notice that all artifacts for the task must have an expiration that is no
	// later than this. If this property isn't it will be set to `deadline`
	// plus one year (this default may subject to change).
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/expires
	Expires tcclient.Time `json:"expires,omitempty"`

	// Object with properties that can hold any kind of extra data that should be
	// associated with the task. This can be data for the task which doesn't
	// fit into `payload`, or it can supplementary data for use in services
	// listening for events from this task. For example this could be details to
	// display on _treeherder_, or information for indexing the task. Please, try
	// to put all related information under one property, so `extra` data keys
	// for treeherder reporting and task indexing don't conflict, hence, we have
	// reusable services. **Warning**, do not stuff large data-sets in here,
	// task definitions should not take-up multiple MiBs.
	//
	// Default:    map[]
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/extra
	Extra json.RawMessage `json:"extra"`

	// Required task metadata
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/metadata
	Metadata struct {

		// Human readable description of the task, please **explain** what the
		// task does. A few lines of documentation is not going to hurt you.
		//
		// Max length: 32768
		//
		// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/metadata/properties/description
		Description string `json:"description"`

		// Human readable name of task, used to very briefly given an idea about
		// what the task does.
		//
		// Max length: 255
		//
		// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/metadata/properties/name
		Name string `json:"name"`

		// E-mail of person who caused this task, e.g. the person who did
		// `hg push`. The person we should contact to ask why this task is here.
		//
		// Max length: 255
		//
		// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/metadata/properties/owner
		Owner string `json:"owner"`

		// Link to source of this task, should specify a file, revision and
		// repository. This should be place someone can go an do a git/hg blame
		// to who came up with recipe for this task.
		//
		// Max length: 4096
		//
		// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/metadata/properties/source
		Source string `json:"source"`
	} `json:"metadata"`

	// Task-specific payload following worker-specific format. For example the
	// `docker-worker` requires keys like: `image`, `commands` and
	// `features`. Refer to the documentation of `docker-worker` for details.
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/payload
	Payload json.RawMessage `json:"payload"`

	// Priority of task, this defaults to `normal` and the scope
	// `queue:task-priority:high` is required to define a task with `priority`
	// set to `high`. Additional priority levels may be added later.
	//
	// Possible values:
	//   * "high"
	//   * "normal"
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/priority
	Priority string `json:"priority"`

	// Unique identifier for a provisioner, that can supply specified
	// `workerType`
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/provisionerId
	ProvisionerID string `json:"provisionerId"`

	// The tasks relation to its dependencies. This property specifies the
	// semantics of the `task.dependencies` property.
	// If `all-completed` is given the task will be scheduled when all
	// dependencies are resolved _completed_ (successful resolution).
	// If `all-resolved` is given the task will be scheduled when all dependencies
	// have been resolved, regardless of what their resolution is.
	//
	// Possible values:
	//   * "all-completed"
	//   * "all-resolved"
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/requires
	Requires string `json:"requires"`

	// Number of times to retry the task in case of infrastructure issues.
	// An _infrastructure issue_ is a worker node that crashes or is shutdown,
	// these events are to be expected.
	//
	// Mininum:    0
	// Maximum:    49
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/retries
	Retries int `json:"retries"`

	// List of task specific routes, AMQP messages will be CC'ed to these routes.
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/routes
	Routes []string `json:"routes"`

	// Identifier for the scheduler that _defined_ this task, this can be an
	// identifier for a user or a service like the `"task-graph-scheduler"`.
	// Along with the `taskGroupId` this is used to form the permission scope
	// `queue:assume:scheduler-id:<schedulerId>/<taskGroupId>`,
	// this scope is necessary to _schedule_ a defined task, or _rerun_ a task.
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/schedulerId
	SchedulerID string `json:"schedulerId"`

	// List of scopes (or scope-patterns) that the task is
	// authorized to use.
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/scopes
	Scopes []string `json:"scopes"`

	// Arbitrary key-value tags (only strings limited to 4k). These can be used
	// to attach informal meta-data to a task. Use this for informal tags that
	// tasks can be classified by. You can also think of strings here as
	// candidates for formal meta-data. Something like
	// `purpose: 'build' || 'test'` is a good example.
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/tags
	Tags json.RawMessage `json:"tags"`

	// Identifier for a group of tasks scheduled together with this task, by
	// scheduler identified by `schedulerId`. For tasks scheduled by the
	// task-graph scheduler, this is the `taskGraphId`.  Defaults to `taskId` if
	// property isn't specified.
	//
	// Syntax:     ^[A-Za-z0-9_-]{8}[Q-T][A-Za-z0-9_-][CGKOSWaeimquy26-][A-Za-z0-9_-]{10}[AQgw]$
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/taskGroupId
	TaskGroupID string `json:"taskGroupId"`

	// Unique identifier for a worker-type within a specific provisioner
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task.json#/properties/workerType
	WorkerType string `json:"workerType"`
}

type TaskExceptionRequest struct {

	// Reason that the task is resolved with an exception. This is a subset
	// of the values for `resolvedReason` given in the task status structure.
	// **Report `worker-shutdown`** if the run failed because the worker
	// had to shutdown (spot node disappearing). In case of `worker-shutdown`
	// the queue will immediately **retry** the task, by making a new run.
	// This is much faster than ignoreing the issue and letting the task _retry_
	// by claim expiration. For any other _reason_ reported the queue will not
	// retry the task.
	// **Report `malformed-payload`** if the `task.payload` doesn't match the
	// schema for the worker payload, or referenced resource doesn't exists.
	// In either case, you should still log the error to a log file for the
	// specific run.
	// **Report `resource-unavailable`** if a resource/service needed or
	// referenced in `task.payload` is _temporarily_ unavailable. Do not use this
	// unless you know the resource exists, if the resource doesn't exist you
	// should report `malformed-payload`. Example use-case if you contact the
	// index (a service) on behalf of the task, because of a declaration in
	// `task.payload`, and the service (index) is temporarily down. Don't use
	// this if a URL returns 404, but if it returns 503 or hits a timeout when
	// you retry the request, then this _may_ be a valid exception. The queue
	// assumes that workers have applied retries as needed, and will not retry
	//  the task.
	// **Report `internal-error`** if the worker experienced an unhandled internal
	// error from which it couldn't recover. The queue will not retry runs
	// resolved with this reason, but you are clearly signaling that this is a
	// bug in the worker code.
	// **Report `superseded`** if the task was determined to have been
	// superseded by another task, and its results are no longer needed.  It is
	// convention in this case to create an artifact entitled
	// `public/superseded-by` containing the taskId of the task that superseded
	// this one.
	// **Report `intermittent-task`** if the task explicitely requested a retry
	// because task is intermittent. Workers can choose whether or not to
	// support this, but workers shouldn't blindly report this for every task
	// that fails.
	//
	// Possible values:
	//   * "worker-shutdown"
	//   * "malformed-payload"
	//   * "resource-unavailable"
	//   * "internal-error"
	//   * "superseded"
	//   * "intermittent-task"
	//
	// See http://schemas.taskcluster.net/queue/v1/task-exception-request.json#/properties/reason
	Reason string `json:"reason"`
}

type TaskReclaimResponse struct {

	// Temporary credentials granting `task.scopes` and the scope:
	// `queue:claim-task:<taskId>/<runId>` which allows the worker to reclaim
	// the task, upload artifacts and report task resolution.
	//
	// The temporary credentials are set to expire after `takenUntil`. They
	// won't expire exactly at `takenUntil` but shortly after, hence, requests
	// coming close `takenUntil` won't have problems even if there is a little
	// clock drift.
	//
	// Workers should use these credentials when making requests on behalf of
	// a task. This includes requests to create artifacts, reclaiming the task
	// reporting the task `completed`, `failed` or `exception`.
	//
	// Note, a new set of temporary credentials is issued when the worker
	// reclaims the task.
	//
	// See http://schemas.taskcluster.net/queue/v1/task-reclaim-response.json#/properties/credentials
	Credentials struct {

		// The `accessToken` for the temporary credentials.
		//
		// Min length: 1
		//
		// See http://schemas.taskcluster.net/queue/v1/task-reclaim-response.json#/properties/credentials/properties/accessToken
		AccessToken string `json:"accessToken"`

		// The `certificate` for the temporary credentials, these are required
		// for the temporary credentials to work.
		//
		// Min length: 1
		//
		// See http://schemas.taskcluster.net/queue/v1/task-reclaim-response.json#/properties/credentials/properties/certificate
		Certificate string `json:"certificate"`

		// The `clientId` for the temporary credentials.
		//
		// Min length: 1
		//
		// See http://schemas.taskcluster.net/queue/v1/task-reclaim-response.json#/properties/credentials/properties/clientId
		ClientID string `json:"clientId"`
	} `json:"credentials"`

	// `run-id` assigned to this run of the task
	//
	// Mininum:    0
	// Maximum:    1000
	//
	// See http://schemas.taskcluster.net/queue/v1/task-reclaim-response.json#/properties/runId
	RunID int `json:"runId"`

	// See http://schemas.taskcluster.net/queue/v1/task-reclaim-response.json#/properties/status
	Status TaskStatusStructure `json:"status"`

	// Time at which the run expires and is resolved as `exception`,
	// with reason `claim-expired` if the run haven't been reclaimed.
	//
	// See http://schemas.taskcluster.net/queue/v1/task-reclaim-response.json#/properties/takenUntil
	TakenUntil tcclient.Time `json:"takenUntil"`

	// Identifier for the worker-group within which this run started.
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task-reclaim-response.json#/properties/workerGroup
	WorkerGroup string `json:"workerGroup"`

	// Identifier for the worker executing this run.
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task-reclaim-response.json#/properties/workerId
	WorkerID string `json:"workerId"`
}

type TaskStatusResponse struct {

	// See http://schemas.taskcluster.net/queue/v1/task-status-response.json#/properties/status
	Status TaskStatusStructure `json:"status"`
}

type TaskStatusStructure struct {

	// Deadline of the task, `pending` and `running` runs are
	// resolved as **exception** if not resolved by other means
	// before the deadline. Note, deadline cannot be more than
	// 5 days into the future
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/deadline
	Deadline tcclient.Time `json:"deadline"`

	// Task expiration, time at which task definition and
	// status is deleted. Notice that all artifacts for the task
	// must have an expiration that is no later than this.
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/expires
	Expires tcclient.Time `json:"expires"`

	// Unique identifier for the provisioner that this task must be scheduled on
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/provisionerId
	ProvisionerID string `json:"provisionerId"`

	// Number of retries left for the task in case of infrastructure issues
	//
	// Mininum:    0
	// Maximum:    999
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/retriesLeft
	RetriesLeft int `json:"retriesLeft"`

	// List of runs, ordered so that index `i` has `runId == i`
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs
	Runs []struct {

		// Reason for the creation of this run,
		// **more reasons may be added in the future**.
		//
		// Possible values:
		//   * "scheduled"
		//   * "retry"
		//   * "task-retry"
		//   * "rerun"
		//   * "exception"
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/reasonCreated
		ReasonCreated string `json:"reasonCreated"`

		// Reason that run was resolved, this is mainly
		// useful for runs resolved as `exception`.
		// Note, **more reasons may be added in the future**, also this
		// property is only available after the run is resolved.
		//
		// Possible values:
		//   * "completed"
		//   * "failed"
		//   * "deadline-exceeded"
		//   * "canceled"
		//   * "superseded"
		//   * "claim-expired"
		//   * "worker-shutdown"
		//   * "malformed-payload"
		//   * "resource-unavailable"
		//   * "internal-error"
		//   * "intermittent-task"
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/reasonResolved
		ReasonResolved string `json:"reasonResolved,omitempty"`

		// Date-time at which this run was resolved, ie. when the run changed
		// state from `running` to either `completed`, `failed` or `exception`.
		// This property is only present after the run as been resolved.
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/resolved
		Resolved tcclient.Time `json:"resolved,omitempty"`

		// Id of this task run, `run-id`s always starts from `0`
		//
		// Mininum:    0
		// Maximum:    1000
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/runId
		RunID int `json:"runId"`

		// Date-time at which this run was scheduled, ie. when the run was
		// created in state `pending`.
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/scheduled
		Scheduled tcclient.Time `json:"scheduled"`

		// Date-time at which this run was claimed, ie. when the run changed
		// state from `pending` to `running`. This property is only present
		// after the run has been claimed.
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/started
		Started tcclient.Time `json:"started,omitempty"`

		// State of this run
		//
		// Possible values:
		//   * "pending"
		//   * "running"
		//   * "completed"
		//   * "failed"
		//   * "exception"
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/state
		State string `json:"state"`

		// Time at which the run expires and is resolved as `failed`, if the
		// run isn't reclaimed. Note, only present after the run has been
		// claimed.
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/takenUntil
		TakenUntil tcclient.Time `json:"takenUntil,omitempty"`

		// Identifier for group that worker who executes this run is a part of,
		// this identifier is mainly used for efficient routing.
		// Note, this property is only present after the run is claimed.
		//
		// Syntax:     ^([a-zA-Z0-9-_]*)$
		// Min length: 1
		// Max length: 22
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/workerGroup
		WorkerGroup string `json:"workerGroup,omitempty"`

		// Identifier for worker evaluating this run within given
		// `workerGroup`. Note, this property is only available after the run
		// has been claimed.
		//
		// Syntax:     ^([a-zA-Z0-9-_]*)$
		// Min length: 1
		// Max length: 22
		//
		// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/runs/items/properties/workerId
		WorkerID string `json:"workerId,omitempty"`
	} `json:"runs"`

	// Identifier for the scheduler that _defined_ this task.
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/schedulerId
	SchedulerID string `json:"schedulerId"`

	// State of this task. This is just an auxiliary property derived from state
	// of latests run, or `unscheduled` if none.
	//
	// Possible values:
	//   * "unscheduled"
	//   * "pending"
	//   * "running"
	//   * "completed"
	//   * "failed"
	//   * "exception"
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/state
	State string `json:"state"`

	// Identifier for a group of tasks scheduled together with this task, by
	// scheduler identified by `schedulerId`. For tasks scheduled by the
	// task-graph scheduler, this is the `taskGraphId`.
	//
	// Syntax:     ^[A-Za-z0-9_-]{8}[Q-T][A-Za-z0-9_-][CGKOSWaeimquy26-][A-Za-z0-9_-]{10}[AQgw]$
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/taskGroupId
	TaskGroupID string `json:"taskGroupId"`

	// Unique task identifier, this is UUID encoded as
	// [URL-safe base64](http://tools.ietf.org/html/rfc4648#section-5) and
	// stripped of `=` padding.
	//
	// Syntax:     ^[A-Za-z0-9_-]{8}[Q-T][A-Za-z0-9_-][CGKOSWaeimquy26-][A-Za-z0-9_-]{10}[AQgw]$
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/taskId
	TaskID string `json:"taskId"`

	// Identifier for worker type within the specified provisioner
	//
	// Syntax:     ^([a-zA-Z0-9-_]*)$
	// Min length: 1
	// Max length: 22
	//
	// See http://schemas.taskcluster.net/queue/v1/task-status.json#/properties/workerType
	WorkerType string `json:"workerType"`
}