You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@vaind Previously, libraries where checked into Git which meant I could for example download main and paste into our depot (And reconcile on Perforce), to get the latest version. Now, the dependencies are part of the packaging job, which I'd missed - So getting latest requires you to download the released version (Or via the Ci Job), there isn't anything indicating how to work from Main for example.
Compiled dependencies are available as GH Artifacts which means they can only be downloaded by the repo members. Building locally is an option though it's not exactly straightforward. Currently, the best solution I can think of is instructing users to fork the repo+branch they want and let them run CI on their fork. The only thing they would need to set up is a secret to access Unreal docker images. We could even update the CI to automatically skip this step on forks if the secret is not configured.
The text was updated successfully, but these errors were encountered:
@vaind Thanks for entering that, worth noting I can access https://github.com/getsentry/sentry-unreal/actions/runs/3051676430 and download artifacts from that - It's more is that the best way to get the libraries or is there a better way to work? Obviously, it's not the plan from my side to use the unreleased version all the time - It's more for testing fixes.
Compiled dependencies are available as GH Artifacts which means they can only be downloaded by the repo members. Building locally is an option though it's not exactly straightforward. Currently, the best solution I can think of is instructing users to fork the repo+branch they want and let them run CI on their fork. The only thing they would need to set up is a secret to access Unreal docker images. We could even update the CI to automatically skip this step on forks if the secret is not configured.
The text was updated successfully, but these errors were encountered: