30 Jan '17, 11am

"Continuous delivery with Git (hotfix by default)"

"Continuous delivery with Git (hotfix by default)"

Recently there has been shift in the way we organize code and do releases in one of our Ruby on Rails web projects. Previously, when we were introducing new major feature, we were going with pretty standard git-flow . How do we use git-flow? When using git flow, we usually work on feature branches (i.e. feature/1234-super-cool-stuff ), and start them based on master branch. After work on given feature branch is completed, it gets merged back into master . This triggers automatic build on our CI server. Whenever CI server reports a green build on master , it automatically deploys the code to our staging server. The story is then tested on staging, and accepted/rejected. The whole process reiterates until all stories of current epic feature are tested and accepted. At this point, we are ready to release to production. This is done by merging master branch into production bra...

Full article: https://www.amberbit.com/blog/2017/1/30/continous-deliver...

Tweets

Google AdWords Updates IF Functions & Default V...

seroundtable.com 31 Jan '17, 12pm

Google quietly announced on Google+ that they made some changes to the IF functions and default values used for ad customi...

How to set up continuous integration for a #Rub...

youtube.com 27 Jan '17, 9pm

This video shows how to set up continuous integration for a Ruby on Rails project on Semaphore CI, a hosted continuous int...

Continuous training needed to help workers displaced by artificial intelligence: IPS

Continuous training needed to help workers disp...

todayonline.com 30 Jan '17, 10pm

SINGAPORE — Imagine a scenario where the Government imposes a quota system — like the one used to manage vehicle populatio...