Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Macos-Runner cannot use personal licence #60

Open
Yaski opened this issue Sep 22, 2023 · 2 comments
Open

Macos-Runner cannot use personal licence #60

Yaski opened this issue Sep 22, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@Yaski
Copy link

Yaski commented Sep 22, 2023

Orb version

game-ci/[email protected]

Execution environment

  • Executor: 'unity/macos-runner'
  • Target platform: iOS
  • Unity Editor version: '2021.3.27f1'

Bug description

I created personal licence file (Job doesn't run with default licence installed on PC)
And I pass licence as base64 encoded file in 'unity-license-var-name'

When I start the job I get the error:
"No serial detected. Extracting it from the encoded license.
Password:
Too long with no output (exceeded 20m0s): context deadline exceeded"

Expected behavior

I expect that job start with licence provided and without error

@Yaski Yaski added the bug Something isn't working label Sep 22, 2023
@Yaski
Copy link
Author

Yaski commented Sep 22, 2023

I looked at the code and extracted serial code myself. Then passed it in serial variable. But I still get the error:
Detected OS: macOS. Detected Unity serial. Password: Too long with no output (exceeded 20m0s): context deadline exceeded

I guess the reason is using commands "sudo mkdir -p "$unity_license_file_path" in prepare-env.sh script
So it needs to run from superuser for this commands to work.
It is strange because I had licence file installed on PC and I don't need any prepare-env work that is executing each time.
Can we have option to disable "prepare-env" step in that case?

@Yaski
Copy link
Author

Yaski commented Sep 22, 2023

Yes when I changed the daemon to run from 'root' It works ok now. But I am not sure that it is a good idea to run jobs from superuser. At least it is needed only for installing unity and hub and applying licence. It is rare case and can be optimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant