CI: Add Steam build uploader

[derrod]

Description

Adds a GitHub actions workflow as well as necessary files for Steam build to be uploaded directly from this repo.

This is version 1 of this workflow, which does not yet account for M1/Apple Silicon builds. Once we get closer to starting the beta phase of the next release and have decided on a naming scheme for builds, whether to use universal builds for Steam, etc. the action will be updated to a "v2".

Motivation and Context

OBS is now on Steam, we don't want to have to deal with manually uploading builds. As originally proposed in obsproject/rfcs#30 this adds the necessary automation via GitHub actions.

Thanks to OpenTTD whose workflow has served an inspiration for this version.

How Has This Been Tested?

A number of runs of various iterations on my own repo: https://github.com/derrod/obs-studio/actions/workflows/steam.yml

A run with the version in this PR at the time of submission is here: https://github.com/derrod/obs-studio/actions/runs/2021121357

I'm sure some people have ideas to optimise it further as I'm not exactly experienced with writing github actions.

Types of changes

• New feature (non-breaking change which adds functionality)

Checklist:

• My code has been run through clang-format.
• I have read the contributing document.
• My code is not on the master branch.
• The code has been tested.
• All commit messages are properly formatted and commits squashed where appropriate.
• I have included updates to all appropriate documentation.

[derrod]

Updated to get a more recent 7zip from a Ubuntu PPA and replaced all the ugly temporary json files with using variables that are piped into jq.

[PatTheMav]

Startled the witches of nitpick forest, but looks fine overall.

Do we have to use batch scripts (i.e. prescribed by Steam)? I'd prefer Powershell, but with Windows preventing user-initiated Powershell scripts by default I wouldn't know if it works out of the box.

[derrod]

The batch script were simply adapted from the existing virtualcam install script. Since powershell is blocked by default that probably wouldn't work, and iirc I tried running a powershell script in an earlier iteration but that didn't work for some reason (maybe steam does a bit more than just telling the OS to run a file and didn't recognise .ps1?).

[PatTheMav]

The batch script were simply adapted from the existing virtualcam install script. Since powershell is blocked by default that probably wouldn't work, and iirc I tried running a powershell script in an earlier iteration but that didn't work for some reason (maybe steam does a bit more than just telling the OS to run a file and didn't recognise .ps1?).

Yeah I'm worried that Windows will just block execution and batch scripts are just the way to go.

[RytoEX]

Did a quick review.

[RytoEX]

Seems fine. I left a comment on the frequency of the cron timing. Approved otherwise.

[PatTheMav]

Where does Steam install the app bundle to on macOS? Did anyone test this already?

[derrod]

From memory it should be in ~/Library/Application Support/Steam/steamapps/OBS Studio

[PatTheMav]

From memory it should be in ~/Library/Application Support/Steam/steamapps/OBS Studio

Ugly, but should cause no issues.

[derrod]

From memory it should be in ~/Library/Application Support/Steam/steamapps/OBS Studio

Ugly, but should cause no issues.

Well it did cause the issue of browser source not loading, which was fixed in 269d48f :P

Fun fact: Epic puts stuff into /Users/Shared/Epic Games/<stuff>.

[RytoEX]

@PatTheMav If this is still good to go, I'll land it.

[PatTheMav]

In the best tradition of our joint indulgence of nitpicking, I added a few picked nits of my own.

[RytoEX]

@PatTheMav Re-requesting review until we get to an approval.