How Yipit deploys from Github with multiple private repos

Re:How Yipit deploys from Github with multiple private repos by mey on Thursday September 06, 2012 @03:28PM (#4485760)

I was looking at this sideways until I read the last statement about the future. There is something bothersome to me about deploying code directly from a code repository. Things I can think of that bother me about it, not clear what code has and has not been deployed, code is not explicitly validated (automatically, manually, on a build/test lab), and it isn't clear who triggered the release.

I think it also bothers the side of me coming from compiled languages where there is more to a code release then copy files from a to b.

[ Parent | on HN ]

Re:How Yipit deploys from Github with multiple private repos by maratd on Thursday September 06, 2012 @04:30PM (#4486076)

Not if you structure your repo correctly.

> not clear what code has and has not been deployed

You can have your production machines deploy from specific branches. In other words, master is the development branch, some-version-branch is the production branch. You can also do it vice versa. You can use tags. Lots of solutions.

> code is not explicitly validated (automatically, manually, on a build/test lab)

If you use the structure above, you wouldn't commit to a production branch unless you did that. Another solution is to force validation/testing using hooks before allowing a commit to a production branch on your development machine.

> and it isn't clear who triggered the release.

Not sure what you mean here ... every commit is recorded, so you always know who did what.

[ Parent | on HN ]

Re:How Yipit deploys from Github with multiple private repos by mey on Friday September 07, 2012 @02:24PM (#4490468)

I guess it depends on your deployment system, if there is an automated system watching that branch on a central repo, you assume any commit is rolled out and who ever pushed triggered it via commit.

[ Parent | on HN ]

Re:How Yipit deploys from Github with multiple private repos by andrewgross on Thursday September 06, 2012 @03:40PM (#4485821)

I know where you are coming from with compiled languages. A big reason for creating this flow was for working with repositories that are not our primary code repository. We have several internal tools and forks that don't have a complex deployment process. We wanted the simplicity of being able to push to master and knowing that it will be out in ~30 minutes. Our primary code base is rolled out with Fabric instead of Chef (for now) but Fabric will still need to execute a pull from Github at some point during the rollout.

[ Parent | on HN ]