Live data from Hacker News

Deploying at GitHub

github.com

41–50 of 61 posts

Re: Deploying at GitHub

#41
post #10
post #6

Encouraging to know this model scales to 100 employees at least. Purely out of intellectual interest, I wonder if a company the size of Google or Facebook could also ship in this way, or if the whole release manager/team is essential.

Amazon generally doesn't have release teams (except for the retail website). I can't find it right now, but I know someone gave a talk on Apollo, which is how Amazon does deployments.

I think you might be looking for this: http://www.youtube.com/watch?v=dxk8b9rSKOo

Re: Deploying at GitHub

#42
post #13

How do you deal with the github enterprise version of your software? Does it have a separate QA cycle? How often do you ship new releases of that? I am hoping that Github could shed more light on the how they ship an enterprise version along with the SAASy web version that we all know and love.

Yes, the testing/deployment cycle for Enterprise is totally different. We usually release a major version with new features every two/three months, and 2 or 3 minor versions with bug fixes in between.

We always keep the version of github synchronized with master for development/testing, although we only release master directly in major releases. For minor releases we avoid to include major features from github to keep it as much stable as possible.

Re: Deploying at GitHub

#43
post #24

If you're looking for a less complex model of this, you should try our Continuous Integration and deployment service: https://circleci.com . Over time, we'll be providing the sort of complexity that GitHub provides here, now we do about 70% of it.

You look awesome. I think I'll be setting this up on Friday. Do you have webhooks for pass/fail on the horizon? Or better yet, straight up git push with ssh key support when all the tests pass?

Re: Deploying at GitHub

#44
post #43
post #24

If you're looking for a less complex model of this, you should try our Continuous Integration and deployment service: https://circleci.com . Over time, we'll be providing the sort of complexity that GitHub provides here, now we do about 70% of it.

You look awesome. I think I'll be setting this up on Friday. Do you have webhooks for pass/fail on the horizon? Or better yet, straight up git push with ssh key support when all the tests pass?

Yes to web-hooks.

Straight up git push with ssh git key support - yes, but might be slightly beta.

Re: Deploying at GitHub

#45
post #26

Earlier quoted context omitted.

I'd love to hear the backstory behind this. Company hackday, or a day spent shipping a major set of new features?

We don't do "company hack days". If you feel like hacking on something, hack on it. We do have days where multiple people will be waiting in line waiting for their chance to deploy their tweak. That particular day consisted of staff deploys on multiple in-progress branches, some performance tuning, bug fixes, etc. Nothing crazy. I'm also quite sure the number counts deploys across all of our applications. For instanc…

We did have a pretty amazing week right after the summit, where everyone was on fire to ship things and there were a lot of people "in line" to get things deployed. It was pretty awesome, actually, seeing so many things land within a week of the whole team gathering and discussing the future.

Re: Deploying at GitHub

#46
post #44
post #43

Earlier quoted context omitted.

You look awesome. I think I'll be setting this up on Friday. Do you have webhooks for pass/fail on the horizon? Or better yet, straight up git push with ssh key support when all the tests pass?

Yes to web-hooks. Straight up git push with ssh git key support - yes, but might be slightly beta.

Send me an email (email in profile) -- this may be a really cool use case for Zapier.

Re: Deploying at GitHub

#47
post #24

If you're looking for a less complex model of this, you should try our Continuous Integration and deployment service: https://circleci.com . Over time, we'll be providing the sort of complexity that GitHub provides here, now we do about 70% of it.

Looks interesting. Is it free? It seems like it probably is but I'm not sure. Also when it leaves beta how much will it cost? I don't want to end up depending on something I can't afford.

Re: Deploying at GitHub

#48
post #6

Encouraging to know this model scales to 100 employees at least. Purely out of intellectual interest, I wonder if a company the size of Google or Facebook could also ship in this way, or if the whole release manager/team is essential.

Sarbanes-Oxley puts a big damper on production deployments at big companies. I don't fully understand it so I won't try to explain it. (I will complain though: the law says developers shouldn't have control over production systems. If that's a requirement, who's going to write the software?)

I believe you're somewhat mistaken. SOX generally applies to finance systems and financial reporting at public companies. So if you're publicly traded you couldn't use this process for your accounting system. But if Facebook wants to let a junior engineer push out new code without independent review, SOX isn't stopping them.

Re: Deploying at GitHub

#49
post #24

If you're looking for a less complex model of this, you should try our Continuous Integration and deployment service: https://circleci.com . Over time, we'll be providing the sort of complexity that GitHub provides here, now we do about 70% of it.

Looks interesting. Is it free? It seems like it probably is but I'm not sure. Also when it leaves beta how much will it cost? I don't want to end up depending on something I can't afford.

14 day free trial, then $19 for 1 project, $49 for 10 projects, and $149 to run tests twice as fast.

Feedback on anything, including pricing, very welcome.

Re: Deploying at GitHub

#50
Interesting, I saw something like this by looking at the https://github.com/mozilla/pdf.js/ project. Take a look at the closed pull requests. They have some bots listening for commands in comments and do stuff like unit testing and previewing. The result gets posted as comment from the responsible bot. Another one is checking master branch for changes and automatically builds and pushes at gh-pages. Seems to work very well, but don't know how they build/did it.
Post reply on HN