Make a plan to move this project to the new community deployment.

Notes:
simple PR should do it, including some badge links

https://github.com/MozillaReality/FirefoxReality/pull/1809

https://github.com/MozillaReality/FirefoxReality/issues/2059

@owlish let me know yesterday that they are focusing on some other work and I will be working on this. As @owlish mentioned, that means some changes to .taskcluster.yml, and before that lands we'll make some changes in https://github.com/mozilla/community-tc-config/ to create the resources (roles, worker pools, secrets, etc.) that you need.

Apologies for the churn of who's responsible for what -- we'll get it done :)

OK, this should take care of FirefoxReality:

• https://github.com/MozillaReality/FirefoxReality/pull/2086
• https://github.com/mozilla/community-tc-config/pull/39

Note that I've renamed secrets so that they all fall under the same project, firefoxreality, but have a fr or frpc prefix depending on the repo they are assigned to. I'm happy to rename them further if something else makes sense.

A few next-steps there:

• I've assigned admin scopes to the org owners of MozillaReality. Is there a smaller GH team that would be more appropriate?
• Otherwise, the next step to landing these will be to add https://github.com/apps/community-tc-integration and remove the existing TC integration from the repository. As you can see, until that's done there are errors from the existing integration because the worker pools have changed names

As for FirefoxRealityPC, it looks like the CI for it is still being set up. The above should provide a good template for the changes required.

I see from this directory and from slack conversations that there is a worker image set up for FirefoxRealityPC. I'm curious at the name, since the image is based on Windows 2012 :)

At any rate, @petemoore has built a GCP image for that, which I can add to the community-tc-config repo once I know the image ID :)

That (In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #3)

I see from this directory and from slack conversations that there is a worker image set up for FirefoxRealityPC. I'm curious at the name, since the image is based on Windows 2012 :)

That comes from https://github.com/taskcluster/generic-worker/pull/249 and yes, the that is indeed a mistake that the name says win10 yet it is a Windows Server 2012 R2 worker type.

I've attempted to deploy a Windows 10 image, but it is looking like that won't be possible outside of OCC, as our deployment tools do not currently support custom Windows AMIs, since they appear as Linux AMIs in EC2.

Phil, if a client version of Windows (such as Windows 7 or Windows 10) is required instead of a Windows Server edition (such as Windows Server 2012 R2 or Windows Server 2016) it will probably be best for your worker types to be managed by the Release Operations team.

We're in the midst of a migration that means we currently don't have a great deal of bandwidth to set up support for client versions of Windows at the moment, but Release Operations already may have a solution for you.

I'll raise in our team meeting today.

We discussed a bit in the meeting today, and rather than having the workers managed by release operations, it seems the best short-term options for client versions of Windows are:

• run a worker manually on hardware you control
• run a worker manually in a VM in Azure (we haven't tried this, but think that Azure supports Windows 10)
• run windows 2012 or 2016

I'm happy to talk more about those options.

Randall, IIRC you're responsible for FirefoxReality. Do you want to take a look at https://github.com/MozillaReality/FirefoxReality/pull/2086 and make the necessary changes (comment 3)?

We are in the middle of preparing for a release and I would rather not change the build infrastructure out from under us until after the build is out the door and we can afford to have taskcluster builds go down for a little while.

(In reply to Randall Barker [:rbarker] from comment #7)

We are in the middle of preparing for a release and I would rather not change the build infrastructure out from under us until after the build is out the door and we can afford to have taskcluster builds go down for a little while.

Randall: what's the timing on your release? Do you rely on Win10 for your release process, or is this a new requirement? We don't want to derail your ongoing efforts, but please understand we're also under the gun here for this migration.

PSA: The existing (https://taskcluster.net) deployment will be shut down a week from today, on November 9. After that point, any CI not migrated to the new community cluster will stop functioning. The TC team is ready and eager to help get everything migrated by that time, but the deadline is firm.

Apologies for failing to communicate this as broadly and loudly as necessary, and for the bugspam now.

(In reply to Chris Cooper [:coop] pronoun: he from comment #8)

(In reply to Randall Barker [:rbarker] from comment #7)

We are in the middle of preparing for a release and I would rather not change the build infrastructure out from under us until after the build is out the door and we can afford to have taskcluster builds go down for a little while.

Randall: what's the timing on your release? Do you rely on Win10 for your release process, or is this a new requirement? We don't want to derail your ongoing efforts, but please understand we're also under the gun here for this migration.

The Win10 is for the desktop build. I work on the standalone FxR build for android based devices and it uses a linux image to build. To be honest I don't really even understand what or even why this is being done. The complete lack of communication and coordination is really frustrating. To find out we have until Friday to convert is really not acceptable since this is the first I've even heard of this.

Hey Randall -- just checking in if there's anything remaining here? If so, let me know ASAP so I can address it before tomorrow :)

We seem to be good right now. The email notifications started showing up yesterday and the live log seems to also be working.

Awesome! We're still happy to help with whatever you need, but I'll call this finished.