Play framework 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 with Java，但可能会更改为 Scala.

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

对于传统"Java Web 应用程序，我会使用 Hudson/Jenkins.我找到了一个 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 framework 2.0 持续集成设置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！