Implementation of Azure Pipelines for building *.WGT files and releasing them to Github

[robinkruyt]

This pull request allows automatic releases of dev-signed wgt files.

These builds cannot be deployed to TVs directly, but instead need to be resigned. It does however remove the requirement that people build their own version of jellyfin-web and jellyfin-tizen.

This pull request requires manual setup of Azure Pipelines. The following steps must be followed:

• Setup an Azure project
• Attach a Github account with access to this repo
• In the Pipeline settings, add a variable called "CERTIFICATE". This must be a single line, base64 encoded version of the author.p12 file generated by Samsungs Certificate manager. This does not have to be a "Samsung Certificate" as it is meant to be resigned by others. Be sure to mark the variable "secret". [1]
• Setup another variable called "CERTIFICATE_PASSWORD", this too must be secret and refers to the password used to create the author.p12 file.
• For releases, a Github connection must be setup and its name must be setup in the pipeline file.

(I would be willing to set this up if someone adds me to an Azure project)

[1] This file could be converted to base64 using the following command on Linux or MacOS: openssl base64 -A -in author.p12 -out author.base64.txt (-A makes the output singleline)

[dkanada]

Can you head over to the license PR at some point and confirm you're okay with a certain license, we forgot to add one here when pulling the repository into the organization. :smile:

[dmitrylyzo]

@dkanada I still have no answer from Samsung about GPL-3 compatibility with Samsung Apps Store ToS. Currently, "In progress"

[robinkruyt]

About the license, for me any license that is compatible with release on Samsung TV would generally be ok.

[Artiume]

any progress on this and the licensing?

[EraYaN]

For this and for WebOS, we might want to run our own agent so we don't have to install the whole SDKs on each commit. That would simplify the pipeline by a lot.

[spali]

Sorry to hijack this, but It's kind of related to the pipeline stuff and would like to share it. I made progress on an automated build including deploy to the Samsung TV. Maybe my work can be reused somehow in the project. My plan is to use it scheduled to automatically deploy the latest build to my TV's including preset server address. I tried to make it customizable and reusable, so please copy whatever can help here (maybe the certificate part in the deploy.sh is interesting at least for the README.md here, because that's what most struggle with when trying to deploy to a TV for personal use). https://github.com/spali/jellyfin-tizen-deploy Basically it's composed of a tizen sdk docker image that gets jellyfin-web injected from the artifact docker image, builds this repo and creates the certificate stuff each time executed to sign the new package and optionally deploy it to the TV.

Some improvements that would help to make it better and (I assume) would anyway be part of the pipeline, would be to create a artifact image for this repo analog to jellyfin-web which includes everything ready for wgt packaging. Looking forward to a prebuild artifact that I could just reuse without anything else except the wgt signing and deploy part 😉

[G-eos]

Thanks @spali your deploy script works well for me. This is not my preferenced solution having this PR merged or moreover official Samsung repo would be great but waiting for, the script you made make me happy :)

[lcha78]

Thanks @spali it works for me too !

[P3pit0r]

Thanks @spali ! I finally could make it works thanks to you :)

[bdovaz]

@dmitrylyzo any news on this PR?