First build with Vsts and GitHub

I'm going to create simple build with different test frameworks the repository is already available on my GitHub. So Vsts will contain build definition and GitHub contains the code. I need to make a connection between them.



I already created project on Vsts now I navigate to Builds and create new empty build

I create empty build for GitHub. When new empty build is created it will inform you that there is no repository. There is also no repository that can be chosen because now we don't have any connections to GitHub. We need to add one - use Manage button.
 Manage button navigates to project settings to Service subsection. It's a place where you can find all services and other endpoints connected to your project. In the future I will add azure connection here. So lets choose GitHub and authenticate Vsts in GitHub:

 Now when the service is configured it can be use in any build definition.

This is enough to have the first really empty build definition. Save build definition and queue new build. When fired build agent will get repository from GitHub, then clean up and finish. That's it first empty build fired and finished successfully. Unfortunately export on empty build is not working so this time screenshots only.

And now the whole process in one gif thanks to ScreenToGif


Popular posts from this blog

Azure post deployment scripts

Image
Let's do a trick. After deploying application (that was easy with Ftp or Git ) it would be nice to take some action. For example send an email, or write release notes to release page. I will do much fancier thing - I will write some text to console output.
Read more

Mobile view lifecycle. Fixing Xamarin.Forms Page lifecycle

Image
For mobile applications the highest priority is user. What user can see and interacts with. Application should react not only on user interacting with it but also user interacting with operating system. That's why not only application has it's own lifecycle but also "view" has it's own lifecycle. In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is being suspended and reactivated. View know quite a lot about outside world and view lifecycle is very similar to application lifecycle. Compare below first application and then view lifecycle diagrams: In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is...
Read more

Mobile application life-cycle Android vs iOS vs Xamarin.Forms

Image
Lifecycle. One of the most common recruitment questions. No matter what technology you work with this is something that should be well known and understood. It's good to know how application behaves, what it is allowed depending on its state and when to react on specific lifecycle events. In mobile world lifecycle is even more complicated because there is no 1 answer but 3 in this case: Android. iOS. Xamarin.Forms. I use also Xamarin.iOS event names in my diagrams, but the sequence is the same. Lifecycle is the definition when your application have access to resources and when react on state change. For mobile the biggest priority is what user can see and interacts with, so active application have priority in using system resources. System has limited pool of resources, so  applications running in background (not visible to user) is limited by system in how much resources can it use and also system decides when application needs to release all resources (be closed/killed/end o...
Read more