023 iPhreaks Show – Build Automation with Patrick Burleson

    0
    105

    Panel

    Patrick Burleson (twitter github blog)
    Rod Schmidt (twitter github infiniteNIL)
    Ben Scheirman (twitter github blog NSSreencast)
    Andrew Madsen (twitter github blog)
    Jaim Zuber (twitter Sharp Five Software)
    Pete Hodgson (twitter github blog)
    Charles Max Wood (twitter github Teach Me To Code Rails Ramp Up)

    Discussion
    00:27 – Going Rogue Video
    00:42 – Patrick Burleson Introduction

    BitBQ
    MartianCraft
    Briefs

    01:23 – Build Automation
    02:10 – Continuous Integration

    Changes
    xcodebuild
    Ben: Running objective-c tests from the command line (with color)

    07:51 – Testing

    xctool

    10:29 – Automation on a development machine
    11:04 – Things to Automate
    14:14 – XCode 5 Build Automation
    20:08 – Automation

    Bamboo
    Version Numbers
    agvtool
    cupertino (and friends)

    29:50 – Certification
    33:21 – Build Time

    Screenshot Lightning
    guard-xctool-test

    Picks

    iOS Background Fetch example (Andrew)
    sprint.ly (Andrew)
    ASCIIwwdc (Ben)
    Blues Junior™ III: Hot Rod (Ben)
    guitarjamzdotcom (Ben)
    iOS 7 by Tutorials (Ben)
    Pappy's Smokehouse (Pete)
    Go (Pete)
    Bombay By Boat – Moonlight (Pete)
    xcoder (Pete)
    xcodebuild-rb (Pete)
    Paulaner Oktoberfest Bier® (Jaim)
    Pitching Radar (Rod)
    Rich Hickey (Rod)
    ShareMouse (Chuck)
    Tweetbot (Chuck)
    Michael Vey (Chuck)
    Fogo de Chao (Patrick)
    Briefs (Patrick)
    Black Bar (Patrick)
    Test iOS Apps with UI Automation: Bug Hunting Made Easy by Jonathan Penn (Patrick)
    Bamboo (Patrick)
    Alfred App (Patrick)

    Next Week
    64-Bit with Mike Ash
    Transcript

    CHUCK: Hey everybody and welcome to Episode 23 of the iPhreaks Show! This week on our panel, we have Rod Schmidt.

    ROD: Hello from Salt Lake!

    CHUCK: Ben Scheirman.

    BEN: Hello from Houston!

    CHUCK: Andrew Madsen.

    ANDREW: Hi from Salt Lake!

    CHUCK: Jaim Zuber.

    JAIM: Hello from Minneapolis!

    CHUCK: Pete Hodgson.

    PETE: Hello from a very warm conference room.

    CHUCK: I’m Charles Max Wood from DevChat.tv. Before we get going, I want to briefly just remind you that I have put up the GoingRogueVideo.com, where I put up the video talking about how I went freelance. If you’re interested in that, you can go check it out there.

    We also have a special guest, and that’s Patrick Burleson.

    PATRICK: Hello from Dallas, Texas!

    CHUCK: Do you want to introduce yourself since you haven’t been on the show before?

    PATRICK: Sure! My name is Patrick Burleson. I run BitBQ software, which is BitBQ.com. I also do quite a bit of consulting with MartianCraft, and also MartianCraft.com – they are the makers of the design application called Briefs.

    CHUCK: Cool!

    BEN: That was a previous pick of the show!

    CHUCK: Yup!

    PATRICK: Awesome!

    PETE: We should do an episode about Briefs.

    PATRICK: You should! I will probably get your wrap on the show.

    CHUCK: That’d be awesome. Then we could do one on boxers.

    BEN: Yup, quite a history.

    PATRICK: Yes, Briefs has a very long history.

    CHUCK: That’d be really interesting. We brought you on to talk about “Build Automation”.

    PATRICK: Yeah! Build Automation is something that I think everyone should probably definitely look into even if you’re on a team or even a solo developer. That sounds crazy to some people why would a solo developer want to have a build automation…The way I look at it is, on my solo stuff, I want a computer doing as much of the work as I can make it to without me having to get in the way. Automating your build is one of those things where with a click of a button, I can update and ship a new version of any of my products or ship out a beta or whatever. It makes it very, very easy and also reduces the number of mistakes you can make. You don’t have to do anything manually; there’s a chance for a mistake.

    CHUCK: So it’s just kind of like continuous integration?

    PATRICK: Yeah, it is a lot like continuous integration. You can use it 2 different ways.