Open GabLeRoux opened 3 weeks ago
Here is a relevant merge request on a related project on gitlab: https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/merge_requests/95
The following section should help in providing details on how to fix activation for new GameCI docker image version 3: https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/merge_requests/95#how-to-extract-your-unity-serial-from-your-unity-license-file
This script might be useful as well: https://gitlab.com/game-ci/unity3d-gitlab-ci-example/-/blob/cc50193350429ee6d27cb11e026ea826a54bd331/ci/before_script.sh
To summarize this, the technique is pretty much to extract a serial number out of the personal license file.
Here are the currently configured secrets for the orb:
UNITY_ENCODED_LICENSE_2020
UNITY_ENCODED_LICENSE_2021
UNITY_PASSWORD
UNITY_USERNAME
I have the permissions to update their values. In comparison, here are the environment variables used in our other projects (github-actions):
UNITY_EMAIL
UNITY_LICENSE
UNITY_PASSWORD
UNITY_SERIAL
It might be a good idea to get closer to the Github Actions ones.
Orb version
After 1.7.0
Execution environment
Bug description
The activation process for Unity changed a bit concerning personal licenses and GameCI images in version 3. To properly support new Unity versions, we need to solve the activation issues.
How to reproduce
Expected behavior
With valid env variables, good credentials and a valid license, activation should pass.
Additional details
https://app.circleci.com/pipelines/github/game-ci/unity-orb/322/workflows/53a92683-693b-4590-96af-e637609074c6/jobs/4081