Move to VSTS Public Projects and setup builds etc. there about cfpexchange HOT 7 CLOSED

Just got word that I will receive more info on more build minutes as part of the public projects, so let's wait for that. Then I will make a plan on how and what.

But the CI build on AppVeyor for build minutes is indeed an option! Didn't think of that yet.

from cfpexchange.

Not sure if it is the best place for a project like this. The code is easier to find on github. Maybe you can move it to the cfpexchange organization on Github instead?

We could use appveyor as build engine instead. It seems to support a lot of .NET stuff that one might need in order to deploy to azure with deployment slots etc.

from cfpexchange.

While typing I thought the same thing: “how am I going to keep my graph green?!”, that’s why I added to maybe just use the build engine on VSTS.

For you last part, you say appveyor, but you mean vsts? Appveyor is in place now, but indeed for staging and arm, etc. vsts is much easier to use.

from cfpexchange.

You could set it up to still have AppVeyor do the CI stuff and set up a new branch called something like deploy which triggers VSTS's build, which triggers a release pipeline to deploy the stuff.
I'm using such a flow myself on a different project.
It might not be a perfect flow, but it'll save you the precious build minutes :-)

Not sure if VSTS can also use AppVeyor as an artifact source. If so, you can skip the VSTS Build.

from cfpexchange.

You've got unlimited build minutes yet?

from cfpexchange.

I should have, yes! 🎉 actually going for the extended Azure credits now as well... ;)
Only thing left is to move over the build to VSTS with the whole ARM templates and stuff

from cfpexchange.

Building and deploying through ARM and Azure DevOps, I'd say this is done for now/

I would like to introduce some testing environment as well. But that's for later.

from cfpexchange.