GitHub Satellite 2017, 10 Oct 2012

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Building Interconnected Workflows - GitHub Satellite 2017

Description

Hosted by:
Vitor Monteiro, Solutions Engineer GitHub

Featuring:
Andrew Homeyer, Waffle.io
Danielle Tomlinson, CircleCI
Jaime Jorge, Codacy
Cory Virok, Rollbar

Oftentimes we're shown how single a given tool improves your development process by addressing a specific element of your workflow. Wouldn't it be great if we could see a complete toolchain covering planning, build, automatic review, and proactive production error detection with some of the most exciting tools in the market for each of these areas? We hosted the folks from Waffle.io, CircleCI, Codacy, and Rollbar who walked us through a day in a developer's life combining all these tools in a simple to setup yet productive and fun workflow.

At Satellite 2017, attendees came to exchange cutting edge practices on how to bring together the people and tools you need to build great software. Watch the recordings to find out what GitHub's been working on, and hear how other teams use the GitHub ecosystem to customize the way they work.

We'll be getting together again in San Francisco on October 10th-12th for GitHub Universe. We hope you'll join us for three days filled with the creativity and curiosity of the largest software community in the world.

For more information, go to githubuniverse.com.

A

Good morning, thanks for joining our session and I hope, everyone has been enjoying satellites. My name is Vitor and I work for the github solutions. Engineering team this morning, I'm very humbled and happy to host four amazing people that are going to teach us how to use their tools to build an interconnected workflow. So before we go into that, I would like to ask each of the panelists to introduce themselves and very quickly to have a glimpse of your tools.

A

To tell us one thing: you, you feel developers quickly fall in love with when, when starting to use your tools, Andrew, hey.

B

Guys, wow, that is loud, I'm Andrew, homier, the the founder of waffle. The reason teams will have waffle is it's the first time that project management has been made for developers. So we believe that project management has always been made for project managers and we're actually turning that upside down, so that waffles, when the first tools that integrates deeply with github, so that project management is actually fun for for engineers again.

C

Hello, hi I'm, Danielle I work on the Mac platform at circle, CI and people really like having the control of that build and its environment, as well as our like UI and experience around viewing and controlling your build.

D

Everyone um Mike's not working I, think so hi everyone, I'm James from coda, C, CEO and co-founder. So one thing that makes us really excited is that our platform allows developers to be much more optimized in the way that we review code, but really on the way that they focus their attention. So we allow for teams and developers to ship and really concentrate on what matters while developing developing the software.

E

Hi I'm Cory, co-founder CTO of roll bar roll bar is a full-stack error, monitoring solution and the thing that I really love about it is the security that I have is every time I deploy. I know that I'm going to find something and I'm going to be able to fix it quickly, because we provide all the information we need to do that. Thank.

A

You everyone, and thanks thanks for joining us, so today we're going to put ourselves in the shoes of a developer that works on this web app Web Store and one thing that strikes is missing. There is that we don't have any feature any any rating feature.

A

So if I won't see how users have been classifying a book, I really don't have a way to see that so we're going to use waffle to Planet track our work circle to build and test our code coda, C to automatically code review that code and after we deploy to production, we're going to use robots to analyze and debug any runtime issues that are our co-pending, so starting with Andrew, and you if, if I'm that developer starting to work on on these features, how can Warfel help me plan and track that with my team, yeah.

B

So let me just show you awful waffle takes all of your issues and for requests. They live on all your repositories and you have been put into a simple board interface, so you're looking at here, is a the repository that Mona our developer and I and there's the team our working in inside waffle. If you look at a URL, it's the same as what the github repo URL would look like to.

B

So, let's say that: there's many many different repositories and all those different repos can be pulled into a single board and that's what you're looking at here is all those issues. So, as you can see in progress, we have this card where we're adding that that ranking feature so that you, as a user, can go and give a star rating to to a book on a list. So I've been pairing with Mona on this feature and we gave it a size of five, which can mean one day can mean five days.

B

This is point estimation, so awful adds a layer on top of github to add some some agile flavor to it, and this is part of the bigger milestone coding shining stars.

B

So we bought the finish working on this feature and we're going to open up or request so going to get. Heaven opens paw request always say is that it fixes fixes number one. So issue was number one when you open this poor request. What we'll see is this within waffle? It's then moved to the to the review column and that for class has been nested under that issue, and we see that it builded that it builds in progress. Now, it's really cool is that Mona didn't actually move that issue to the review column.

B

Waffle was working behind the scenes. Do that for you? So if you look at that flora quest again we'll see that the wafflebot is actually adding this label which moves the issue and moves up for request to the review column and the wafflebot also assigned assigned one of us as the owner of that floor request. So waffle is actually automating the way that the developers track work. So, instead of having to go to a separate interface or a separate project management tool, you can stay within github.

B

You can stay within for requests and just use waffle as a visual layer, so that your whole team knows exactly what someone's working on they know when something is ready for review. They also know what to work on next, so you have like a ready column in a backlog column. You can customize that workflow to be whatever you want, and it's totally automated by using waffle.

B

I just pull the information out of github, so your whole team can can't see what you're working on this works great for for all sorts of sizes, our customers, we, whether you're open source startup for an enterprise.

B

So you look a little bit closer at that floor request and that issue will see that there's a build in progress so my hand this back to the tour and circle to talk about what's happening behind the scenes.

A

Thank You Angie I, really like the statuses on the carpeting, the bottom. That's really sleek Demi thanks for joining us now that we have the feature in the way. How can how can circle build and test my code and make my team transparent about those changes? So, let's.

C

Take a look so raise your hand if you already are familiar with continuous integration and how many are familiar with circle, CI cool. So for those of you didn't raise your hands circle.

C

Ci is a continuous delivery integration tool that helps teams ship, better code faster and so, as we saw before, Mona has committed a code on github and because of the integration with circle CI, it automatically kicked off a build using the web hooks, and so we really want to help engineering teams be more productive through great tools and through the process of continuous integration, we can consistently build and run tests on every change you make to help find and correct issues as soon as they happen, and that helps you get better products to your users faster and so, as part of this here we see the monist has to fail and because we passed the genuine output from the build, we can show you straight away exactly what test failed and how it failed, and so, rather than having to come through, like your giant, build log and find the like cryptic message from whatever like testing tool, you use.

C

You can just like see it and it's great, and so she can immediately go back to github and to the code and see the really obvious change of like we just forgot to assign the thing, because we wrote the validation and not the actual code, and so she pushes the code and we run another build. This build is running on our 2.0 platform, which is currently in beta, and there are some really nice features of this.

C

You can configure the size of your build like environment and also have full control over your actual, like build image itself, and so here you can see an example for this, like we try and automate a lot of the small and harder tasks you have while giving you a lot of control over your configuration, and so if you've ever had to like wait for someone to provision a build machine for you like adding, like version 2.3 X of this thing, because 2.4 breaks everything's or like you update your build machine and then this break some other teams, CI like in the other part of this company, and then you get an email being like yo.

C

You broke my build or if you're the person, that's actually provisioning the phone machine I'm. Sorry, it's painful people send a lot of email, and so this is a really nice change like you can just provide like your docker image, your tag and away you go, and so now you see, we've got a green build and everything is pretty great, and so things are looking good from our side. But motive team is trying to generally improve the quality of the code, and so one way they're doing this is through code review and off security.

A

So, thank you. Thank you very building, essentials I'm. But as a developer is we spend most of our big part of our time doing code reviews so I'm really excited to understand how cold is he can reduce that load and improve overall code quality of.

D

Course: well thanks thanks anything sweeter, so super excited to be here so at code C, we're focused at really empowering you to optimize as much as we can. Your time and I mean really to allow you to review less, improve quality and merge faster, and we do this by centralizing one place for very important metrics, which are static, analysis issues, test coverage, code, implication and also code code complexity, and so back into the same example. We were looking at some when I screen the pull request and trying to review as much as possible.

D

So we already have that planned. We passed already to a build and we wanted to make sure now that we everything is in check, and so we want to review all the most important parts of the pull requests. So courtesy comes in and injects into that pull request all the most important things that you have to do. We have to review in some way shape or form, but with Curtis you don't have to do any more so, for instance, best practices, basic security code style, all of those get automatically injected in your pull request.

D

So you can really focus on what matters which is really what we aim to do. Furthermore, we introduced pull request status that allows you to say: can we merge or shouldn't? We merge right now right, and so these things get automatically pushed in your workflow in get github as you're developing your features.

D

If you click at that link, you get then emerged into into into coda, see where you can see what we call the pull request: quality impact, so you can see all the Delta in terms of the four main metrics that I've already introduced and then jump and detail every single one of them right.

D

We spent a lot of a lot of time documenting all the issues, all the problems, all the rules, really that we identify with courtesy and this actually serves the purpose of onboarding new developers or teaching best practices or teaching really new junior developers. So you don't have to do that job yourselves.

D

So really, the idea really is to allow you to focus on your functionality and focus on shipping code and allow you to optimize as much as you can the code review process while maintaining a very good standard of quality. We have other really amazing features like our quality dashboard allows you to Street historic of any single one of these metrics throughout time, including prediction of your pull request. As soon as I emerge. All my open pull requests. Where is quality going to be that be yet?

D

And finally, we have what we call the security dashboard that centralizes in one place all the most important security analysis, results and alerts, so you can actually be safe while you're producing your software and your projects, and so this is a little bit of what we are as a product and as a platform. We're super excited to be integrated and they get sub marketplace and with this kotas it gives you as soon as you check everything that courtesy provides. As a result, you can see that now you're ready to merge.

D

You ready, put your coding to production, Thank.

A

You time so, assuming you've been through this process now we have the the rating the ratings in the bookstore and also that's all. We wanted to begin with so I believe that this feature has superior color quality because it was well-planned. It ran our test here and are built and we use coda C for a lot of the code review and, unfortunately, we know not all bugs can be caught in this manner. Right so Cory we've deployed the the new version of the book starts production.

A

How can robot help me track and debug all those remaining issues in production thanks.

E

A

E

Right so Bob our is a full-stack error, monitoring solution and I'll get into that a little bit more in a second. But there's some there's a few things that every developer really should know when deploying code to production. First, are they going to know when it breaks so tailing log files looking at emails, that get sent in for every single occurrence is just infeasible for really large distributions? Second, are you going to know that you going to have enough information to fix the problem when it does break?

E

And third, are you going to be able to reach out to the customers who are affected and are they even going to mention that the feature broke? Are they going to know so? Rollbar is a full-stack error, monitoring solution, which means that we monitor on the client and the server side.

E

We provide integrations for dozens of languages and all the popular frameworks. We have real-time alerts where you need them, so that means slack data dog HipChat and many more. We provide detailed contextual data for every single error so for web requests. That's not just stack traces. That's all the request, parameters, post bodies, headers local variable data host info bra info operating from some operating system info and a lot more.

E

We hook into your deployed tracking, so wherever you're deploying whether that be circle, maybe of a custom fabric script you send that information over to us and we can help you use that to assign and triage you bugs and finally, obviously, we integrate with github source control and issues.

E

So getting back to the example, we've deployed into production awesome. However, one of our users, Joe, has found a bug, so they found a bug when they were trying to rate one of the books on their screen here and the server returned. A 500 response, so rollbar captured that error, both on the client side and the server side, and the first thing that happens is the slack notification gets sent out to your team.

E

The slack notification has a link back into rollbar and at the same time, we created a github issue so that the rest of your team can follow along with the fix in woful great. So when you come into roll bar, we try to show you the information that you need to fix. It really quickly. So here there's a lot on the screen, but I'll just highlight a few things, so we linked into github at the proper commits revision.

E

We show you all the information regarding all the people who are affected, detailed, contextual data on all the requests that went into all the occurrences for this error. We also show you the deploy that the error started happening after so if one of your engineers is deploying on the weekend, you can like you can point at that, and we also show you related items, so this is actually really useful. If you have a error, that's happening as part of a complex interaction of requests that are coming in great.

E

So when you come into github, rollbar has highlighted the line for you and using this, along with the context data that we've provided, the fix becomes obvious and in this example, mona forgot to handle the case where there is no request parameter sent in for the ratings cool. So we've got to fix. All you got to do is mention the roll bar error in the commit message and on the next deploy. The rollbar error will be automatically resolved along with the github issue.

E

And finally, one thing: a lot of people, don't really think about is contacting the users who are affected. Users love this and when you do it really quickly, they really love it. So rollbar provides you information about every single person who was affected by a particular error, along with all of the other errors that they were affected that affected them. So with that, we've finished going through those three stages of finding bugs fixing bugs and affected, contacting the affected users, and we can go back to developing features. Yeah.

A

Thank you very MACC is, as you creates an issue just there to to highlight the area it goes back to awful and it can be tracked by the team and so on to circle and sakoda, see and so on. Before we move on to a few questions, I would like you to join me in the round of applause to our to our beautiful panel.

A

So a few questions, starting now with you Korean all the way up to Andrew what compelled you to join marketplace on days you and how do you think that will help developers build more of these integrated workforce, yeah.

E

For us, it was obvious to integrate with marketplace as soon as we could github is where developers are and we build developer tools, so that was obvious. Also github marketplace makes it really easy to integrate between one developer tool to the next one and technically github marketplace was great for us, because it allows us to reduce the scope of requested permissions for each of the repos when a user installs our app pretty.

D

Good, okay, those are really good points. I would I, would I would add that the seamless transition between github, where you code and review to getting in our case all the most important metrics and you know, although they all the KPI- is to make great code decisions that allows us to be really close to where you developed your source code. So that was a great point for us and we're super excited to be part of the marketplace.

A

C

Perez, it's we want to build and like provide access to tools that make like two really great tools to improve your developer, workflow and being part of something that makes it easier for people and lowers that barrier to integrate. With all of these great tools, it's something we definitely want to support so.

B

In terms of thousands of engineers have adopted all of our tools, I think a story that we're telling today is that we work better together, so I think having a consistent story where we know that our products work really well together in this in a Seco system that it's better for for you all to adopt our tools together at all, because we're giving you a better experience, so I think it's for all this. This marketplace is is amazing because it's amazing for you it's!

B

It makes it so much easier for you to adopt all these things and make it very consistent.

A

Thank you before we finish Andrew and any one or two aspects of the waffle that we weren't able to cover that you like to highlight before yeah.

B

So I mentioned that the waffle makes project management better for developers, but we can't just forget about project managers right, so waffle also gives developers tools to empower their project managers. So we give you metrics, so you can see how your team performs over time and also on where you're you're doing work towards the right goal for the right deadline. So waffle isn't just for developers. It's also for for project managers who want to empower their engineering teams.

C

So I'm Skippy a little bit biased because I work on a Mac platform which, like we recently like, did a bunch of work on to make your like builds for iOS and Mac apps, really fast and really stable, which you don't really get to see in something like this, because Java land, but yeah like I left NCI, is something that not many people offer in a way that is really great and reliable.

C

So I'm pretty proud of that. It's great thank.

D

You thank you Vinnie, okay, so we offer as a platform not only isazo caduceo column but also coda, see Enterprise, which can be served on premise for most languages out there. So you know Ruby, Java, JavaScript, PHP, Python cetera, but there's two main features that I really loved. One is what we call quality gates that allows you to define settings for your project like say: I, don't want coverage to be X amounts over 60% or quality a number of issues to be below a range. So that's a really cool feature.

D

Another one is the way that we essentially allow you to clean code. In let's say, for instance, you have a sprint just for cleaning. We have just a number of views that allow you to sort all your code for a number of issues for a number of you know, coverage number and so forth, and so this is really designed for that time. A really rare time that you have to clean your code. So these are a couple of things that really excited about platform.

D

Thank you. Jim, curry, yeah.

E

I love this part, so last month or earlier yeah last month we released the first and only compliant air monitoring solution, SAS product. So we're really excited about that. So if you're, a financial company or a health tech company or if you just really have PII that you're concerned about, then we can send a BA for you and get you running with the latest and greatest tools. The second one is actually a feature we really last week, it's the best-in-class, instant merging feature, and so I'm really pumped about that.

E

Come talk to me about it after this. If you have any questions very.

A

Quickly instantly we do Cori when, when I go to look for it to like rollbar online one of the first things I check is language and framework compatibility. So can you highlight a few a few of the popular ones, sure.

E

Yeah, so we as I mentioned, we support, you, know dozens of popular languages, so that's Python, Ruby JavaScript on both the client and a server side closure haskell java, iOS android. The list goes on great.

D

And the most, if not all of them, so we support also almost all languages for PHP Java, JavaScript, Python Scala. Unless it's College well I mean we have big big list very recent. Also c-sharp go me CoffeeScript talking, longtime need.

A

Any in terms of languages in platforms, like you mentioned MUC, obviously yeah.

C

So where's our 2.0 platform, we support anything that you can provide a docker container for so be that like Haskell Ruby JavaScript, if you want it to be like fancy, you could probably put like MATLAB or something on there. You know like do all your things and then on LS. Can we primarily support sort of like objective-c Swift, electron, apps react native apps like these kind of things, yeah thank.

A

You Andrew, this is a tricky one for you, yeah.

B

Waffles language, agnostic, which is awesome, we support all of them, guys awful works great for open source. We have open source teams in the the US federal government who track their work out in the open, because they're hired by the government to serve citizens. We have startups that use waffle. We have enterprises that use waffle on premises with waffle takeout.

B

We have startups who actually use an open-source repo to to track just-just-just issues out in the open so that there they can do customer support. You think get a bish use as well, so waffle can be used for any project. Thank.

A

You again another round of applause for our panel.