4 ms·
One of the main reasons the Play! framework didn't get a lot of traction, IMHO, was the lack of a proper build tool (Continuous Integration anyone?). The plan t
by koevet 15y ago
One of the main reasons the Play! framework didn't get a lot of traction, IMHO, was the lack of a proper build tool (Continuous Integration anyone?). The plan to use SBT as a build tool is a welcome news. Same goes for the Akka integration.
- dabeeeenster 15y agoYou can do CI with play projects, it just feels wrong if you look at it from a Java perspective as there are no build files like .war files. You can do it by triggering source code repo updates and then play restarts...
- scompt 15y agoThere's a continuous integration server called calimoucho (https://github.com/guillaumebort/calimoucho https://github.com/guillaumebort/calimoucho) written by the author of the Play framework. I don't have any experience with it though.
- nesbot 15y agoI actually just did a poll on the google group to see what others were using for CI. Most are using a combination of: Calimoucho Jenkins with the play plugin https://wiki.jenkins-ci.org/display/JENKINS/play-plugin https://wiki.jenkins-ci.org/display/JENKINS/play-plugin Teamcity Bamboo So there are currently many options.