Download as PDF, PPTX
Uploaded bySimon Dittlmann
Tooling Matters - Development tools
This document discusses development tooling and provides an overview of the tools used at tado° for various stages of development including collaboration, development, build, test, deployment, production, and logging/monitoring. It recommends tools like Google Apps, Github, Jenkins, Gradle, AWS, Packer.io, Logstash, and CloudWatch and provides examples of how they are used at tado° for tasks like source control, continuous integration, deployment, and analytics. It also includes information about the presenter and an invitation to learn more about job opportunities at tado°.
More Related Content
Similar to Tooling Matters - Development tools
Tooling Matters - Development tools
- 1.
- 2. Who am I? SimonDittlmann at tado° since 2013 previous Payback, WISI, Mivitec... Developer, DevOp Preferred Language: JS Contact SimonDittlmann github.com/Pindar
- 3. What’s tado°? The appthat controls your heating and saves energy. With a Connector kit for your home.
- 4.
- 5. What are tools? •a thing used to help perform a job: computers are an essential tool | the ability to write clearly is a tool of the trade.
- 6. What are tools? •Computing: a piece of software that carries out a particular function, typically creating or modifying another program.
- 7.
- 8.
- 9.
- 10.
- 11. Everywhere! To manage ● Ideas ●Feature Request ● Requirements ● Development ● Deployment ● Production
- 12.
- 13. A tool shouldsupport the optimal process.
- 14. A tool hasto reduce the overall lead time and not just a single step.
- 15. A third partytool should be backed by a big community
- 16.
- 17. From an ideato production Requirements Deployment Development natural language, charts Puppet, JS, Bash Idea / Feature Request Zendesk, Sticky-Notes, Paper Chart Google Apps deployJS, Packer.io, Jenkins, AWS... Production Logstash, Cloudwatch, statsd, AWS... Java, Groovy, JavaScript, C, Python, PHP, JSON, CoAP, HTTP, Cloudformation, Puppet Git / Github, Gradle Grunt, Less-CLI, IDEA-IntelliJ, Vagrant, Rake, mvn, npm, Jenkins, Gem, Guard, Composer, Sticky-Notes, task- board, make, hangouts... natural language
- 18. Let’s take acloser look at DevOps
- 19. Collaboration ● Google Hangoutfor quick chats ● Google Apps for documentation (Office Suite) ● Github to comment on Issues + Pull Requests ○ Powerful collaboration, code review, and code management ● Task Board ○ Sticky Notes
- 20. Development / Debugging ●Git for source code versioning ● Idea IntelliJ as an IDE ● Sublime / VI(M) / Textmate etc. as text editor ● Chrome Developer Tools for FE Debugging ● Spring Boot, Yeoman to speed up development setup ● Vagrant to simulate environments and speed up setups
- 21. Build ● Gradle/Maven forJava build automation ● Grunt for JS build automation ● Composer for PHP build auto/dep mgmt ● Rake for Puppet task management ● Jenkins for Continuous Integration (CI) ● Bower for Front End dependency mgmt ● LESS-CLI to transform less to CSS
- 22. Test / QA ●Spock-Specs to test Groovy/Java ● CodeNarc validates Groovy code ● Protractor to test AngularJS E2E ● karma + PhantomJS for JS unit testing ● JSHint validates JS code
- 23. Deployment ● Packer.io tocreate AMIs (Amazon Machine Image) / Vagrant boxes ● AWS (Amazon Web Services) Cloudformation to describe the infrastructure ● AWS SDK + Custom Software to do the deployment
- 24. Production ● Logstash forlog file monitoring ● Cloudwatch for performance monitoring ● statsd to aggregate data points
- 25. Logstash log shippingprocess shipper (instance) shipper (instance) shipper (instance) Queue (Redis) indexing (elastic search) processi ng (logstash) kibana (JS-view) Backup S3 Cluster
- 26.
- 27.
- 28.
- 29. Deployment Flow Application Infrastructure Virtual MachineDeployment AWS Grails, Java Puppet Cloud formation deploy.js aws sdk/cli packer.io vagrant jenkins jenkins CloudWatch Logstash Statsd
- 30.
- 31.