For play2 it needs no extra files at all to build.
https://buildhive.cloudbees.com/
As I said above, it is in early beta - so we are looking for feedback
and it may not work 100% just yet. However I have a play2 app building
on it :)
- Ivan, CloudBees Engineering
> --
> You received this message because you are subscribed to the Google Groups
> "play-framework" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/play-framework/-/3TjrtFW8vU4J.
>
> To post to this group, send email to play-fr...@googlegroups.com.
> To unsubscribe from this group, send email to
> play-framewor...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/play-framework?hl=en.
[info] Resolving play#play_2.9.1;2.0 ... [info] Resolving play#templates_2.9.1;2.0 ...
Hi Ivan!
SORRY: I mixed myself and my 'second' answer has been posted while I actually failed to send first reponse... which I include now. Sorry, I think I better have to read Google Groups Help, but it's time to sleep now :-/
Thank you for the announcement. BuildHive/GitHub integration is smooth, quite similar as Travis/GitHub. Nice concurrence in perspective!
I actually tested 3 Projects (1 Play2 and 2 pure Scala) with following results:
Configuration auto-detection are nice features, but anyway it is a must to let user override/reconfigure default settings... Travis-CI is already quite mature, BuildHive can for sure take some good influences from it :-).
on https://buildhive.cloudbees.com/template/, I see that the list of build templates is already quite nice (sbt, maven, gradle, bundler/rake, ...). I would recommend you to setup a Play2 template, and then BuildHive wins one point in the race with Travis ;-)
I am looking forward a new discussion thread about BuildHive upcoming features !
Cheers, Gilles
Hi Matthieu,
Thank you very much for the feedback! Yeah, missing 'x' permission is common pitfall when doing copy-paste of shell script content. Actually, I created this extra script 'travis/setup' in a Don't Repeat Yourself and clean code spirit, but it's not straightforward and maybe error-prone...
I thus created another variant where the complete Travis settings fit in main .travis.yml (no more extra shell script to integrate into project). Check it here: https://github.com/gildegoma/travis-ci-ScalaOnPlay-sample/blob/travis.yml-only/.travis.yml (not yet merged into master)
Let me know which variant you find better... My current feeling: +1 for this new variant (everything in .travis.yml).
Precision: Comments from Ivan Meredith show how Play projects can auto-download the Play dependency via Maven/Ivy/sbt. This is also quite nice way to do it, and it works fine either on BuildHive/Jenkins or Travis. My idea here was merely to save download time/traffic, with only a single file to download (play-2.0.zip release), which is also matches with Installation Guide of Play Framework (see http://www.playframework.org/documentation/2.0/Installing)
Regards, Gilles
SBT detection sucks atm because I only made it work for play2. Ive
updated it a bit and now it detects akka and maybe others.
I will work on getting things going. However, your play2 app should be
working, unsure why its not.
> --
> You received this message because you are subscribed to the Google Groups
> "play-framework" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/play-framework/-/d7_bLE5ZEkQJ.
On 25 April 2012 11:19, gildegoma <gilles...@gmail.com> wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "play-framework" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/play-framework/-/d7_bLE5ZEkQJ.