Play框架2.0连续集成设置 [英] Play framework 2.0 continuous integration setup

问题描述

我在寻找Play 2.0连续集成设置的想法。它将包含典型的工作，如git push后构建，每晚构建，部署到测试Heroku实例等。代码质量和测试覆盖率指标生成会很方便。

I am looking for ideas for a Play 2.0 continuous integration setup. It would contain typical jobs like build after a git push, nightly builds with deployment to a test Heroku instance etc. Also code quality and test coverage metrics generation would be handy.

现在堆栈看起来像Play 2.0与Java，但可能改变为Scala。

At the moment the stack looks like Play 2.0 with Java but that might change to Scala.

对于传统的Java Web应用程序，我会使用Hudson / Jenkins。我找到了 Google Hudson插件，但它似乎不支持Play 2.0。一般来说，Hudson是否适合使用这个工具，或者您在Play 2.0应用程式中的设定是什么？

For "traditional" Java web app I would use Hudson/Jenkins. I found a Hudson plugin for Play but it doesn't seem to support Play 2.0. Is Hudson suitable tool here in general or what is your setup for Play 2.0 applications?

推荐答案

Play 2.0的建置工具 SBT 附近的薄封套。您应该可以使用Hudson的 sbt插件执行相当于

Play 2.0's build tool is just a thin wrapper around SBT. You should be able to use Hudson's sbt plugin to execute SBT build commands that are the equivalent of the Play commands you would execute from the console.

我们在Bamboo下执行下面的命令：

We execute the following under Bamboo for our builds:

SBT_OPTS="-Dsbt.log.noformat=true"
sbt clean compile test

（SBT_OPTS变量关闭颜色格式，使测试输出在日志文件中清晰可见。）

(The SBT_OPTS variable turns off the colour formatting, making test output legible in log files.)

这篇关于Play框架2.0连续集成设置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！