This presentation describes Gradle ways to address Node.js and Play framework automation.

1. Polyglot Gradle with Node.js and Play
Evgeny Goldin
Gradle eXchange, London
October 28, 2013

6. Device per need

7. Language per need

8. Build tool per need?

9. The One

10. A year with Node.js

11. Dev => CI => Prod

12. Dev => CI => Prod

13. Dev => CI => Prod

14. npm install

15. node server.js

16. forever start server.js

17. Easy?

18. Automate this!

19. Bootstrap and versioning

20. npm install

24. Before and After listeners

25. Verified start and stop

26. Jenkins?

27. Chef?

28. Jenkins + Chef + Gradle

29. Can Gradle provision?

30. ./gradlew

31. ghost.org

33. ./gradlew -i start / stop / test / help

34. build/*.sh

35. npm install?

36. package.json

37. checksum

38. npm install

39. node_modules
=>
<checksum>.tar.gz

40. ~/.npm
PUT / GET

42. MongoDB / Redis

43. github.com/fzaninotto/uptime

44. Grunt / Cake

45. ./gradlew -i start / test / run

46. Where does it lead?

52. Polyglot Gradle

53. Ghost
Uptime
Zentasks

54. Node.js / MongoDB
Play / sbt
grunt

55. Bash is a new JavaScript

56. Build tool per need

57. The One?

58. “Be water, my friend”
~ BRUCE LEE

59. Thank You

60. @evgeny_goldin
bitbucket.org/evgenyg/gradle-exchange
github.com/evgeny-goldin/gradle-plugins