ci: use the latest OBS in Docker image #133
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andreykaipov
force-pushed
the
andrey/docker
branch
from
53f17e6 to
39fbc93
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Whenever obs-websocket releases a new minor version, the client library is auto generated, but if the minor version has new requests, the tests will fail because we're testing against the older version of the server, e.g. #131
Since obs-websocket is bundled with OBS now, this PR gets the latest artifact from obsproject/obs-studio's push workflow and uses that instead of the PPA because it could be weeks until it's updated.
It also builds the image before bumping instead of on a weekly cadence. Hopefully the next time there's a minor version bump with new requests, this will automatically build the image, the generated protocol PR will be created, and the tests can pass.
This PR also changes the retention policy on our ghcr images (TBD).No need to do this as I only remove untagged images.