This repository has been archived by the owner on Dec 1, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 30
Setup CI/CD to ensure consistent builds #19
Comments
LucaBernstein
added a commit
to LucaBernstein/jellyfin-react-client
that referenced
this issue
May 29, 2019
To satisfy jellyfin-archive#19
@anthonylavado is it something you could look into? I'm not sure if it's you who has all those creds. |
I don’t have those creds, no. Paging @nvllsvm and @joshuaboniface |
It might be a good idea to stick to Azure Pipelines, since we already use them for the main project. And they also have windows, mac and linux. |
Since GitHub actions are publicly available now I guess they are also an option. I can write some GitHub workflows to test and build the client for every pull request. |
We use Azure so that would be the ideal solution I think. |
What would the desired steps be? Do the tests work headless? Want just tests run or would you like the builds run as well? |
You need the build for the tests, so both? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
CI/CD tools like TravisCI, ...
#16 shows that it might become handy if builds are run (automatically) before merging.
Run all
The text was updated successfully, but these errors were encountered: