Codit / practical-api-guidelines

Practical guidelines for building & designing APIs with .NET.
MIT License
16 stars 5 forks source link

Migrate CI to Azure DevOps #108

Closed tomkerkhove closed 5 years ago

tomkerkhove commented 5 years ago

Now that Azure DevOps has public builds I'm curious if we should move to that instead over using Travis CI given we're more used to it and will be easier to onboard new folks.

Thoughts?

tomkerkhove commented 5 years ago

It's not a must, I'm just curious.

fgheysels commented 5 years ago

I think it's a good idea to move to Azure Devops

tomkerkhove commented 5 years ago

I can pick this up if you guys are up for it.

@MassimoC I'd need to have a project to build them on and a connection towards GitHub.

tomkerkhove commented 5 years ago

Would YAML configuration be ok?

MassimoC commented 5 years ago

Go for YAML. I think is the best approach for OSS

tomkerkhove commented 5 years ago

This is done, but it only builds as debug - Otherwise we were having issues with SQL connection.

Can you have a look at this please @fgheysels ?

tomkerkhove commented 5 years ago

Build cleaned up via #119.

Remaining things open before closure:

With respect to build config, we used to build in debug for travis as well. Do we need release build or not? I think it's good practice but no expert

tomkerkhove commented 5 years ago

You can manually trigger CI for now via /azp run ci

tomkerkhove commented 5 years ago

Completed ✔️