Enable Travis and Appveyor builds about collada2gltf

[outofcontrol]

@lasalvavida is correct, we just need to update the tokens to be not using his. I've not gotten to it yet.

[outofcontrol]

PR just submitted. Let me know if I did things correctly. You might want to update your wiki page by removing --add from the first token generation. At least on macOS automatically adding the token with travis encrypt really messes up the line breaks in the .travis.yml file. Suggest manually adding the new token.

[pjcozzi]

@outofcontrol could you please follow the above instructions so we can have CI (e.g., automated builds) for this repo? Thanks!

[KhronosWebservices]

Both Travis and Appveyor are enable. Badges are:

[![Build Status](https://travis-ci.org/KhronosGroup/COLLADA2GLTF.svg?branch=master)](https://travis-ci.org/KhronosGroup/COLLADA2GLTF)   

--

[![Build status](https://ci.appveyor.com/api/projects/status/3xtpxjohflwd5t1p?svg=true)](https://ci.appveyor.com/project/Khronoswebmaster/collada2gltf)     

[pjcozzi]

Nice, thanks @lasalvavida @Khronoswebmaster!

@lasalvavida can you please do final testing and add the badges to README.md?

[lasalvavida]

@Khronoswebmaster, this should be the last thing. The encrypted tokens in the config currently are set up for my credentials; they should be regenerated by the owner of the repo.

I've put up some instructions for this process on the wiki. These will also be helpful for people who want to set up CI on their own forks.

I would appreciate it if you could follow those instructions to update the configs and let me know if you have any issues.

[outofcontrol]

What am I missing here? None of the other repos we have using Travis us tokens. Why does this repo need tokens?

[lasalvavida]

For deployment to GitHub releases and updating the latest tag on successful build

[outofcontrol]

The other repos are deploying builds without tokens. When we link travis with our repos, we already give permission to have write access. I'll look into this further and see what's needed here.

[lasalvavida]

Of course, do whatever you need to for verification. I did just do a quick survey of some of the other Khronos repos with Travis configs and none of the ones I saw were using the Travis deployment feature, so I can only assume they are doing their releases manually.

[outofcontrol]

The following are using Travis. Some appear to push the build to the repository. I'm not sure if they update the latest tag. Not trying to be difficult here, just trying to understand the process so we can get this repo setup in the best manner.

KhronosGroup/glslang
KhronosGroup/SPIRV-Cross
KhronosGroup/SPIRV-Tools
KhronosGroup/Vulkan-LoaderAndValidationLayers
KhronosGroup/WebGL
KhronosGroup/Vulkan-Samples
KhronosGroup/Vulkan-Hpp
KhronosGroup/SPIRV-LLVM
KhronosGroup/KTX

[lasalvavida]

Which ones do you see pushing builds? I just looked at the repos you listed and I don't see that in any of their configs.

[pjcozzi]

@outofcontrol is this a permissions issue?

[lasalvavida]

@outofcontrol, any idea when you'll be able to take a look at this?

[lasalvavida]

Noted and updated

[lasalvavida]

Updating the latest tag doesn't seem to work, but I checked my fork and it looks like its broken there as well. Maybe github changed their api permissions, but it was kind of clunky anyway, so I've removed it. If you generated a second GH_TOKEN key, you can remove it, as it won't be used.

[lasalvavida]

@outofcontrol, travis deployment looks fine, but appveyor is erroring out with a 401 - Unauthorized, could you double check the encrypted key?

[outofcontrol]

Verified that key is correct when generated from the public_repo token.

[lasalvavida]

Looks like it's working now, thanks @outofcontrol. I'm going to close this.

[pjcozzi]

This is great, thanks @lasalvavida @outofcontrol!