search

clean-development / engine

Game Engine
Apache License 2.0
2 stars 3 forks source link

Setup CI pipeline #3

Closed smudge202 closed 8 years ago

smudge202 commented 9 years ago

AppVeyor would be the de facto choice, but I'm open to suggestion.

Assuming appveyor, we just need the appveyor.yml and any associated build scripts. I'll get an account setup for the organisation in due course.

herecydev commented 9 years ago

If you script the majority and bundle that into your source code, you will keep the vendor-specific stuff minimal. This helps inclusion of travis or other CI tools. That way you can setup all of them to run and just let it be a free-for-all.

With minimal extra cost you get faster feedback (first return will suggest a positive result), more consistency (A failing build on 1 CI indicates "it worked on my machine" problem), and failover.

smudge202 commented 9 years ago

Agreed; I want all the important stuff in build scripts. However, should we find ourselves using API keys or something of that nature that requires the use of secrets manager that will have to be bespoke to the build agent acounts.

smudge202 commented 9 years ago

Blocked by #2