Support other platforms by not increasing image size

[robinryf]

Currently only Mac and Windows player support are included in the images. It makes sense to provide images which also contain iOS, Android, WebGL, etc. build support.

Just adding all these components would blow up the image size and thus slow down every build using the image.
Probably providing separate images for each platform or platform category (mobile, web, standalone) would make sense

A nice maintainable solution with a modular component selection strategy would be nice here.

[angusmf]

Once you have Unity installed and licensed, can you run the install again to add components without having to re- license? If so, maybe don't include more than one build target per image. When a build is triggered, I'd want to start one container for each build target needed.

[Genteure]

@angusmf I'm pretty sure you can do that on Windows.

And I can confirm that you can rerun the installer to install component to existing Editor.

Maybe something like this:

• 2018_1_0f2_base: install unity editor only. this will include Linux build support.
  • 2018_1_0f2_windows: install Windows build support.
  • 2018_1_0f2_mac: install Mac build support.
  • 2018_1_0f2_webgl: same as above
  • 2018_1_0f2_android
  • 2018_1_0f2_ios
  • 2018_1_0f2_facebook
• 2018_1_2f1_base
  • 2018_1_0f2_windows
  • etc ..

Given that much tag, I think maybe put all the files for different tags in the same branch is a better solution than keep every tag on its own branch. The only branch can have an up-to-date README file, and you don't have to update twenty difference README if you want to change something.

• README.md
• nuget
  • latest
    • Dockerfile
• unity3d
  • 2018_1_0f2_base
    • Dockerfile
  • 2018_1_0f2_windows
  • 2018_1_0f2_mac
  • ...