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

Add bee script to pull down required mono-build-deps from stevedore #1064

Merged
merged 1 commit into from
Nov 7, 2018

Conversation

ashwinimurt
Copy link

@ashwinimurt ashwinimurt commented Nov 5, 2018

  • Add Bee.exe under mono/external/buildscripts/
  • Add Bee script to pull down required mono-build-deps from Stevedore "Testing" (this will be changed to production in upcoming PR when we promote the artifacts) and copy them to mono-build-deps directory.
  • Add buildDependencies.txt file with the details of stevedore artifacts that we should download. I was using XML previously but that references System.xml. So simply using a text file.

Upcoming PR:

  • Pull down artifacts based on platform we are building for - this PR pulls down everything in specified buildDependencies.txt
  • Gitlab CI config to use it

Note - This does not affect any builds running on Katana or locally, unless we explicitly run Bee.exe.

@ashwinimurt
Copy link
Author

I am testing this on use-stevedore-gitlab-ci branch.

use-stevedore...Unity-Technologies:use-stevedore-gitlab-ci

@ashwinimurt ashwinimurt merged commit 929ae6e into unity-master Nov 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants