decentraland / builder / 36726765583

57%

master: 57%

Pull #3511

github

feat: deploy through the cdn-deploy action instead of the npm relay

Deploying went through four hops: oddish published the built `dist/` to npm,
that triggered a GitLab pipeline, the pipeline uploaded the tarball to the CDN
bucket, and a `deployment_status` webhook fired `set-rollout` to write the
Cloudflare KV record. Every hop needed a credential in this repository --
`GITLAB_CDN_DEPLOYER_TOKEN`, `GITLAB_CDN_DEPLOYER_URL`, `NPM_TOKEN` -- and a
failure in the middle left the site on the previous version with a green run.

`cdn-deploy` does the whole thing in one step: it settles the version, runs the
build, uploads to S3 and writes the rollout through a broker that authenticates
this repository by GitHub OIDC. No Cloudflare token and no IAM role live here
any more; the broker checks `decentraland/definitions` to confirm this
repository owns `@dcl/builder-site` before it will write anything.

Behaviour is preserved, not changed. A push to master still rolls out to zone
and today at 100%, which is what the two steps in `set-rollout` did. The build
keeps the same `CI` and `NODE_PATH` it had, at job level now because the build
runs inside a composite action and those do not inherit step `env:`.

The npm publish goes with it. `@dcl/builder-site` on npm existed to move bytes
to the CDN, which S3 now receives directly.

`set-rollout-manual.yaml` stays: it can set a version to 0%, which the new
`promote` job cannot express, and that is what a real rollback needs.

2636 of 5727 branches covered (46.03%)

Branch coverage included in aggregate %.

7629 of 12288 relevant lines covered (62.08%)

37.21 hits per line