Page MenuHomePhabricator

[CI] Introduce GitHub Actions CI job for keyserver releases
ClosedPublic

Authored by ashoat on Aug 19 2024, 10:30 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Sep 25, 1:30 AM
Unknown Object (File)
Wed, Sep 25, 1:30 AM
Unknown Object (File)
Wed, Sep 25, 1:30 AM
Unknown Object (File)
Wed, Sep 25, 12:26 AM
Unknown Object (File)
Sep 10 2024, 5:19 PM
Unknown Object (File)
Sep 10 2024, 5:06 AM
Unknown Object (File)
Sep 6 2024, 3:32 AM
Unknown Object (File)
Sep 6 2024, 12:22 AM
Subscribers

Details

Summary

This addresses ENG-9048.

We'll use the same image for keyserver, web, and landing.

For now, I'll continue to handle the creation of entries in the GitHub Releases page manually. This is how we do it for most workflows, with the exception of desktop_release.yml.

@will will follow-up with some changes here as part of ENG-8839.

Test Plan

I'm not sure how to test this yet. I could land it and try testing from the master branch directly. From my research, it seems like the main alternative would be to test from a fork, but that would rewuire duplicating all relevant GitHub Secrets there

Diff Detail

Repository
rCOMM Comm
Branch
ashoat/github
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

This revision is now accepted and ready to land.Aug 19 2024, 11:20 AM

Going to land this and test on master