1. 1 Rake as build management tool for developers and project managers Denis Lutz

2. Rake for Developers The Hyphothesis about Ant “Hello World” from Rake Ant Hypothesis proove 1 Rake for Project Managers Ant Hypothesis proove 2 Case Study “The Perfect Build” Riskmanagement 3 Improvements you can make with rake 2

4. deployments

5. initial project setup / configurations

8. domain specific language (DSL) for builds based on ruby

9. rake for ruby is like ant for java “the build management tool”

10. existing rake version in jruby

12. 7 What is rake? Calling a core ant task… rake is a plain mapping to the ant java classes ! We can call any task or target that ant has!

13. 8 What is rake? Create a task that is dependent on the unzip task It should create a folder and move the unzipped file into it

14. 9 Ant is not sufficient for what we want to do Back to Hypothesis… Ant is not sufficient for what we want to do. Not anymore since we have better choices. It was created as no scripting languages were supporting java. What are we usually doing with Ant?

16. deployments

17. initial project setup

18. data load (csv, fixtures)

19. cron job execution

20. moving / copying / deleting files or directories

21. writing to files

22. processing data sets

23. building dependencies on coditions

24. 11 Ant is not sufficient for what we want to do moving / copying / deleting files and directories Ant: Looks pretty simple right? Just couple lines, markup was always easy… Rake: I want to do operations as would it be in a unix environment, and rake realizes it:

25. 12 Ant is not sufficient for what we want to do processing a data set (Array) in a loop Ant: See, for anything that a normal language has, ant has a markup version of it Ant: So you will be always fine and be able to write what you want Rake: Well lets just take a scripting language then… like ruby Rake: and by the way, can you use unique ant syntax somewhere else ouside the build scripts?

26. 13 Ant is not sufficient for what we want to do Ant: Yea, conditions are definded on the tasks themselves, since its all about tasks.

27. 14 Ant is not sufficient for what we want to do Rake: that’s all we wanted:

28. 15 Ant is not sufficient for what we want to do Rake: How about some methods to don’t repeat yourself in the build? Ant: Methods??? Your kidding me right? Targets are your methods, or create a macrodef Ant: If it gets too complicated soo create your java class and call it from ant… Ant: Here is the macrodef syntax Rake: Dude, I just want a method ok? So attribute is clear … that’s what I need Whats the deal with the <element /> ? What is the <sequential/> suppose to mean? So I predefine what tasks I will call inside my new macro ? Should I always use sequential ?

29. 16 Ant is not sufficient for what we want to do Rake: Watch, that’s what I want..

30. 17 Ant is not sufficient for what we want to do Rake: I want to create some objects in my script… Ant: Objects??? Lets not exagerrate here ok? Ant: If its that complicated just create a custom ant task with a java class Rake: Yea, its like object orientation = elegance , so we should use it directly in the script…

31. 18 Ant is not sufficient for what we want to do Ant: LOL, it should not be that complicated Ant: unless you really want to fly to the moon… Rake: Well lets say I have a deployment script and I deal with servers… Rake: This is what I could do with object orientation, all this in one file, within mins

33. powerful

34. maintable

35. easy understanble

38. its mostly done by one dedicated person

39. everyone else is not familiar with ant and the build script

40. developers tend to do fast adjustments to the script using the ant api

41. you are good with ant if you worked with it for a longer time

42. the ant knowledge can not be used somewhere else

43. developers have no motivation to learn it properly

45. jruby can be declared as the core scripting language in each (java) project anyways

46. because we need ruby for: data import, front end, parsing, any scripting language tasks

47. the knowledge of rake ( = ruby ) is a good investment for developers

48. ruby is a great, simple, elegant and powerfull language

50. ruby knowledge is reused much more in projects with ruby if declared as scripting language

51. front ends can be written in ruby on rails

52. ruby knowledge can be reused much more on the US market

53. java scripting languages = languages that are running on jvm

55. 25 Ant is not sufficient for what we want to do Rails competes with JSF in the meanwhile, which indirectly shows the power and acceptance of the ruby language on the us market.

56. 26 Improvements we could reach by using rake Which parts of your java project can be improved by using rake? 1. Setting up the project initially and for any new team member 2. Working with the project everyday 3. Deployment management

58. knowledge is mostly party written on the wiki and outdated

59. no one really knows what the project setup steps are

60. the older the project the more out of sync is it

61. the project setup takes usually the time of the new person and one team memberAt the end you loose a lot of time, instead of initially investing little bit more!

62. 28 Improvements we could reach by using rake What the a new member feels at the project setup: What database do I need? What are the database properties? Where should I configure them? Who should I ask about it? Where is the wiki page about this project? I have a windows machine, are there any differences to a macs? What should I write into my “hosts” file? How do I start this special backend / front end / solr server?

64. Local database setup (setting up mysql/oracle + create database)

65. Unzipping of vendor files (commercial integrated systems, solr, patches)

66. Cofiguration files setup: user setting + default + environment

67. Build (starting automatically)

68. Database initialization (without entering any client)

69. different data imports (* n times)

70. other step by a cronjob (* n times)

71. server startup (front end, back end, solr, any other server)

72. commercial integrated system configuration

74. dedicated person in each project responsible for the build maintenance

75. project planned time investment for a complete project setup by a build

76. investment will immidiatelly pay off, with a new team member at the latest

77. thinking in a perspective of a beginner who has no project knowledge

80. Local database setup (setting up mysql/oracle + create database) (still potentially automatable)

81. Unzipping of vendor files (solr, patches)  DONE

82. Cofiguration files setup: user setting + default + environment  DONE

83. Build (starting automatically)  DONE

84. Database initialization (without entering the webclient)  DONE

85. different data imports (* n times)  DONE

86. other step by a cronjob (* n times)  DONE

87. server start up / which beanshell script should I call?  DONE started, informed the user how to do it

90. did he need to ask someone for something? No

91. did he need to look up a wiki page and wait till his account on it is created? No

92. even if there was a manual step we were exactly telling the user what to do at the right time

93. our assumtion for now was: he works on a mac / unix system

94. he had to be able to install mysql database by himself

96. we have the old ant build.xml still inside the project

97. we can go back to ant all the time, just by adding old ant targets

98. jruby is used anyways if this is the official project scripting language

100. the build is your source for any automation

101. server starts (back end/ sorl/ front end/ any server)

102. cronjob execution (instead of looking it up in a client and executing)

103. repetitive data load (you work on a data load and need repetitive execution)

105. same advantages as for the project setup apply

107. rake => great new option to use, has a lot of synergies and is fun

108. separate discussion needed for deployments strategy based on rake

109. start saving money and time today