Smart development environments
1 like594 views
The document discusses the importance of maintaining a smart development environment, highlighting the use of automation, version control with GitHub, and continuous integration with Jenkins. It outlines a structured server architecture for development, testing, and production, as well as tools for communication and metrics tracking among team members. The author emphasizes that while establishing and maintaining these systems requires effort, they ultimately enhance productivity and collaboration within development teams.
Smart development environments
- 2. Wojciech Sznapka PHPCon Pl Szczyrk 27.10.2013
- 5. Cześć! :)
- 6. Hanys ze Ślůnska wito Wos pierońsko piyknie
- 7. Since 2006 regularly in a teams of developers
- 8. Loves software craftsmanship, sophisticated architectures, Big Data and automation
- 9. Why a development environment needs care?
- 11. And repetitions leads to routine and are always error prone
- 12. Automation is always better than written process
- 16. Every team member has his own fork
- 17. He creates a feature branch related to the User Story from Jira, he is working on
- 18. He works on his own machine
- 20. After a series of commits to his feature branch he opens a pull request
- 21. Other devs review the code and make comments
- 22. Pro Tip: smaller pull request are easier to review and maintain
- 23. Developer fixes things and pushes again
- 24. The responsible person merges pull request into develop branch
- 25. The code metrics
- 26. Most of new projects are started based on Symfony XSolve Edition
- 28. It contains standard build.xml for Ant
- 29. There are around 28 targets
- 31. Most important are: »» build - used to deploy
- 32. Most important are: »» build - used to deploy »» ci - run on Jenkins
- 33. Most important are: »» build — used to deploy »» ci — run on Jenkins »» cli — runs code sniffer, mess detector, copy paste detector on CLI to check curremt status before committing
- 34. Most important are: »» build — used to deploy »» ci — run on Jenkins »» cli — runs code sniffer, mess detector, copy paste detector on CLI to check curremt status before committing »» thresholds-check — to build PRs
- 35. Code metrics are collected by Jenkins and available there
- 36. Builds
- 37. We build every change in develop branch
- 38. Also we build every project in the morning to see if passing time hasn’t affected the code :-)
- 39. The third build goes for Pull Requests
- 40. We’ve integrated Jenkins GitHub PR Builder
- 41. It runs tests and checks if code metrics warnings don’t exceed thresholds
- 45. This mechanisms helps us to not watch for code style or obvious things during code reviews, but to focus on what’s important
- 46. Deployments
- 47. A standard servers structure:
- 48. A standard servers structure: »» development
- 49. A standard servers structure: »» development »» CI server
- 50. A standard servers structure: »» development »» CI server »» test server
- 51. A standard servers structure: »» development »» CI server »» test server »» stagagging (A.K.A. Preview) server
- 52. A standard servers structure: »» development »» CI server »» test server »» stagagging (A.K.A. Preview) server »» production
- 53. We use launcher to update application on test and stagging server
- 54. Launcher is our Silex based application that launches ant tasks, triggered by github hook
- 55. It updates test env for every change...
- 56. ... and staging for every new tag
- 57. Communication
- 58. We use HipChat
- 60. It has a great and simple API
- 61. And plenty of tools has built-in integration
- 62. And plenty of tools has built-in integration »» GitHub
- 63. And plenty of tools has built-in integration »» GitHub »» Jira
- 64. And plenty of tools has built-in integration »» GitHub »» Jira »» Jenkins
- 65. And plenty of tools has built-in integration »» GitHub »» Jira »» Jenkins »» New Relic
- 66. And plenty of tools has built-in integration »» GitHub »» Jira »» Jenkins »» New Relic »» Zabbix
- 67. Also our internal tools uses HipChat API to notify important facts
- 68. Of course we have github, jira, jenkins emails notifications
- 69. Extras
- 70. Github-metrics
- 71. It counts pull requests and commits per developer across all repos and pushes it to HipChat every morning at 10:00
- 74. Harvesters Jenkins API to get number of violations (or fixes) for every developer
- 76. Summary
- 77. It requires a lot of effort to put all those tools together
- 78. Even more work is required to maintain and keeps it running
- 79. But after some time it works gloriously
- 80. Teams don’t waste time on non-programming work
- 81. It’s way easier to introduce new team members
- 82. And you have a lot more time to think about solving world’s problems
- 83. Thank you
- 85. Dołącz do nas!