blocks|key|1490930|text|非常有趣，但还不可能，AFAIK。我一直在谷歌代码中寻找这个选项，但没有成功。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1490931|我能想到的唯一解决方案是在您的机器上安装一些程序来检查SVN存储库中的更改。|1490932|我很高兴听到其他的方法。|1490933|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Very interesting, but not yet possible, AFAIK. I have been looking for that option in Google Code with no success.

The only solution I can figure out is to install something in your machine that checks for changes in your SVN repository.

I'll be happy to hear about other approaches.

blocks|key|1706012|text|对于我们这些正在使用Github的人来说，GAE团队的这个特性会让我们认真考虑切换到Google+Code……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1706013|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For those of us who are using Github, this feature from the GAE team would make us all seriously consider switching to Google Code...

blocks|key|1491004|text|您可能必须在另一台监视SVN提交并为您部署新版本的计算机上安装一些胶水。Google+Code还没有开发和发布API+(如果他们认真对待整个开发的事情，他们需要尽快完成)，但是GAE可以相对自动轻松地部署到，所以我不会认为这应该有那么困难。但是，每个项目的部署过程都会有所不同，所以这是您需要自己解决的问题(您可能想看看fabric部署系统)。然后，只需设置一个cron作业来更新中间机器上的本地SVN结帐，就完成了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1491005|entityMap|0|LINK|mutability|MUTABLE|url|http://www.nongnu.org/fab/^0|4G|6|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You'd probably have to have some glue on another computer which monitored SVN commits and deployed a new version for you. Google Code has yet to develop and release an API (which they need to do soon if they're serious about this whole development thing), but GAE can be deployed to with relative automated ease, so I wouldn't have thought it should be that difficult. The deployment process, however, will vary with each project, so that's something you need to sort out yourself (you might wanna take a look at the <a href="http://www.nongnu.org/fab/" rel="nofollow noreferrer">fabric</a> deployment system). Then, just set a cron job going which updates a local SVN checkout on the middle machine, and you're done.

blocks|key|1491059|text|Made+By+Sofa有一个关于他们使用Google+App+Engine的工作流程的blog+post。在倒数第二段中，他们有attached+a+subversion+hook，当有人提交代码时，它会自动部署到Google+App+Engine上。这将需要一些调整(因为它在服务器端工作，而不是在客户端)，但你可以做同样的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1491060|entityMap|0|LINK|mutability|MUTABLE|url|http://www.madebysofa.com/|1|http://www.madebysofa.com/#blog/appengine_hosting|2|http://www.madebysofa.com/media/downloads/appengine_deploy.sh^0|0|C|0|18|9|1|1T|Q|2|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]|$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]|N|$5|G|H|I|C|$J|O]]]]

<a href="http://www.madebysofa.com" rel="nofollow noreferrer">Made By Sofa</a> had a <a href="http://www.madebysofa.com/#blog/appengine_hosting" rel="nofollow noreferrer">blog post</a> about their workflow with Google App Engine. In the second last paragraph they have <a href="http://www.madebysofa.com/media/downloads/appengine_deploy.sh" rel="nofollow noreferrer">attached a subversion hook</a> that when when someone commits code it will automatically deploy to Google App Engine. It would take a little bit of tweaking (because it works on the server side not the client) but you could do the same.

blocks|key|1491119|text|谷歌代码项目托管现在支持Post-Commit+Web+Hooks，它在每次提交后ping项目所有者指定的网址。这将消除定期轮询您的Google代码存储库的需要。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1491120|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/support/wiki/PostCommitWebHooks^0|C|L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Google Code Project Hosting now supports <a href="http://code.google.com/p/support/wiki/PostCommitWebHooks" rel="nofollow noreferrer">Post-Commit Web Hooks</a>, which ping a project-owner-specified URL after every commit. This would eliminate the need to regularly poll your Google Code repository.

Anyone have any thoughts on how/if it is possible to integrate Google Code commits to cause a Google AppEngine deployment of the most recent code?

I have a simple Google AppEngine project's source hosted on Google Code and would love if everytime I committed to Subversion, that AppEngine would reflect the latest commit. I don't mind if things are broken on the live site since the project is for personal use mainly and for learning.

Anyone have any thoughts on how to tie into the subversion commit for the Code repository and/or how to kickoff the deployment to AppEngine? Ideally the solution would not require anything manual from me nor any type of server/listener software on my machine.

Possible to integrate Google AppEngine and Google Code for continuous integration?

服务器

有没有人对如何/是否有可能集成谷歌代码提交来导致最新代码的谷歌AppEngine部署有任何想法？我有一个简单的谷歌AppEngine项目的源代码托管在谷歌代码上，如果每次我致力于Subversion，AppEngine将反映最新的提交，我会很高兴。我不介意现场的东西坏了，因为这个项目主要是为了个人使用和学习。任何人都有...

问可以集成谷歌AppEngine和谷歌代码来实现持续集成吗？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问可以集成谷歌AppEngine和谷歌代码来实现持续集成吗？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问可以集成谷歌AppEngine和谷歌代码来实现持续集成吗？
EN