1519867 - Staging deployment with RFC0128 manifest/references/schemas

Status: RESOLVED FIXED

(Taskcluster :: Services, enhancement)

Description

[Pete Moore [:pmoore][:pete]]

In order to work on taskcluster-client updates for RFC 0128, we need a (staging) deployment of taskcluster that declares a coherent set of manifest/references/schemas using the new file formats.

The latest staging deployments have yet to use the new syntax. Notably, some manifests are missing (such as manifest-v3.json), and the service manifest is still using manifest-v2.json format rather than manifest-v3.json.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

I think this just needs a redeployment. I'm working on doing so in my dev environment now (something has broken tc-notify and bug 1519848 yet to deal with) then I'll deploy to staging. The v3 manifest is present in the latest tc-references.

Comment 2

[Brian Stack [:bstack]]

removing NI since dustin is deploying

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

https://taskcluster-staging.net/schemas/common/ looks better now.

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

Pete, let me know if anything else is amiss with this deployment.

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

Per today's meeting, the issues noted in the description are no longer the case. I'm sure there will be more fixes, but let's worry about those in subsequent bugs.

Comment 6

[Pete Moore [:pmoore][:pete]]

All good now, thanks!