Lessons: 16Length: 1.6 hours
- Overview
- Transcript
5.1 Conclusion
We've covered a lot of ground, and we've seen three powerful options for continuous integration. I hope this course has given you ideas for improving your personal or team development workflow.
From all of us here at Envato Tuts+, thanks for watching!
1.Introduction
1.1Introduction01:07
1.2What Is Continuous Integration?04:54
1.3Development Approaches: Git Flow and GitHub Flow04:38
1.4Project Overview01:42
2.Git Flow, Travis CI and Engine Yard
2.1Travis CI Overview09:01
2.2Test a New Feature07:43
2.3Release and Hotfix08:04
2.4Engine Yard Deployment08:27
3.GitHub Flow, Codeship and Heroku
3.1Codeship Overview09:24
3.2Develop a New Feature09:49
3.3Heroku Deployment05:38
4.Bonus: Custom Jenkins Server and Capistrano
4.1Installing Jenkins on a VPS02:31
4.2Jenkins Overview10:08
4.3Test a Ruby Project06:02
4.4Capistrano Deployment08:04
5.Conclusion
5.1Conclusion01:02
5.1 Conclusion
You've made it. Now you know the basics of two very important Continuous Integration Workflows. It is mandatory to follow those to the point. You can take what you think is useful from them and create your very own workflow that completely fits your needs. One alteration of the GitHub flow that is very popular is to add another safeguard, a distinct production branch that only pulls from master and only if the staging environment is stable. Feel free to contact me on Twitter if you have any further questions. Or want to know more about the specific topic I covered. Thank you for watching this course. From all of us here at Tuts+, we hope you enjoyed and learned something from it. See you next time.
