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.
Deploying at GitHub
41–50 of 61 posts
Re: Deploying at GitHub
#42How 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.
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
#43If 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.
Re: Deploying at GitHub
#44If 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?
Straight up git push with ssh git key support - yes, but might be slightly beta.
Re: Deploying at GitHub
#45Earlier 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…
Re: Deploying at GitHub
#46Earlier 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.
Re: Deploying at GitHub
#47If 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.
Re: Deploying at GitHub
#48Encouraging 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?)
Re: Deploying at GitHub
#49If 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.
Feedback on anything, including pricing, very welcome.