Where Continuous Integration and Deployment has its home.

Manuel Weiss

Subscribe to Manuel Weiss: eMailAlertsEmail Alerts
Get Manuel Weiss: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Manuel Weiss

How we built our Google Glass integration in less than 2 weeks I am happy to announce that we have officially launched our Google Glass integration for Crushpath along with an updated version of our Promotion and Social Monitoring features. In this post, I am excited to discuss why we picked Glass and how we achieved the integration in under 2 weeks. At Crushpath our mission is to help people, in particular, small business owners and entrepreneurs, quickly pitch their business to potential customers. Pitching is not a one time thing, it's about establishing a dialogue and giving people solid reasons to do business with you as well as listening to their feedback. For this reason, earlier this year we released a powerful new feature in our product called Crushpath Pitches. Pitches are very popular with our users for creating beautiful showcases of their business. To ge... (more)

Slow Tests Are the Symptom, Not the Cause

If you have a slow test suite and you are asking yourself "how can I make my tests faster?" then you are asking the wrong question. Most chances are that you have bigger problems than just slow tests. The test slowness is merely the symptom; what you should really address is the cause. Once the real cause is addressed you will find that it's easy to write new fast tests and straightforward to refactor existing tests. It's surprising how quickly a rails app's test suite can become slow. It's important to understand the reason for this slowness early on and address the real cause ... (more)

Efficiency in Development Workflows: Deployment Pipelines

Last week we talked about how we review code, open pull requests and use GitHub issues to manage our development workflow. This week I will show you every step that happens after a pull request is merged into our master branch. We use an automated deployment pipeline for releasing our code into production. Deployment Pipelines A deployment pipeline lays out the whole process that your code needs to go through from your repository to production. It breaks the build into several parts (e.g., build, test and deploy) and all the associated steps that need to be taken. By defining a p... (more)

Efficiency in Development Workflows: Immutable Infrastructure

After reading Chad Fowlers excellent blogpost about immutable deployments at 6Wunderkinder, we wanted to share our views on immutability in infrastructure. Our definition of Immutable Infrastructure: Automate the setup and deployment for every part and every layer of your infrastructure. Never change any part of your system once it is deployed. If you need to change it, deploy a new system. For example, instead of deploying into an existing EC2 instance, start a new server, deploy there and point your load balancer to the new server. Then remove the old server. Replacing a syste... (more)

How to Set Up Continuous Deployment to Amazon OpsWorks

Deploying code to Amazon OpsWorks using Codeship Here, at Novo IT, we love using Amazon OpsWorks for deploying our internal projects. With OpsWorks, we can easily segregate our development environments in Stacks and control how each project gets built via Chef recipes. OpsWorks binds directly with your code repository of choice. When you initiate a new build, it will pull in the latest changes and build them for you. One task, that is not immediately obvious how to solve, is triggering an OpsWorks build remotely from the command line, or from a build server. This article will expl... (more)