Placester is an all-in-one digital marketing solution for real estate professionals employing 160 people, with the engineering department counting for about 20% (30+ developers) of the overall employee count. The engineering teams are distributed between Boston and Chicago.
We talked with Ryan Fisch, Senior Director of Engineering at Placester, to learn about their experience with CodeShip Basic and CodeShip Pro.
Why Placester Adopted CodeShip’s Continuous Integration Platform
When Fisch, who previously had used CodeShip Basic at a former company, had been tasked with leading the Engineering departments at Placester and making their development workflows more cohesive and efficient, he set out to get CodeShip implemented at Placester.
As Placester’s tech stack is very varied (NodeJS, PHP, Java, Go and Python apps running on AWS) they were looking for a cloud-hosted, customizable CI/CD solution that did not require a lot of internal maintenance. Previously running on Jenkins but not being satisfied with the amount of internal resources it required and having had satisfying experiences with CodeShip previously, Fisch decided to start adopting CodeShip Pro throughout all of Placester’s apps and projects after evaluating multiple CI services in the cloud and on-premise market.
How Placester is Using CodeShip for CI/CD
“We were up and running in a day, and it’s been like that ever since, even with all the new deployments and all the new features. They’re adopted very quickly, everything is very intuitive.” Fisch says. Also citing that “the intuitive nature of CodeShip’s Products and the customer support and interaction with CodeShip as a whole has been a differentiator. They are best in class.” After a period of six months working with CodeShip, Placester’s testing and deployment of their Platform as a Service is 100 percent automated.
Previously to using CodeShip Pro, Docker technologies had not been used at all by the Placester engineering teams. Once the teams set out to achieve more flexibility and customizability within their workflows using Docker made a lot of sense to them. It opened up a lot more avenues for them to complete custom builds and custom tailoring their build platforms.
The Placester engineers are using CodeShip Pro’s local CLI to do a lot of their testing. Today, they are developing locally and building locally to test for production. Fisch mentions that the cohesiveness of the packaging of CodeShip proved to be very helpful to his teams. “CodeShip is integrated into our packages, into our code bases. The quality controls are built in. It allows us to prohibit anything from getting out into our production environments that could break our applications.”
The Future of CodeShip at Placester
“CodeShip allowed me to move out of the tech ops implementation and really take the spirit of DevOps. My engineers are all responsible for their infrastructure automations, their CodeShip compilations and build and step configurations.” said Fisch.
As new CodeShip features continue to roll out, Placester plans to integrate them into their workflows in order to increase awareness and monitoring across their systems. The goal is to have a set Continuous Delivery pattern where a release schedule is not needed any more.
CodeShip has enabled Placester to speed up their development processes by an order of magnitude compared to their previous setup.
Real Estate, Marketing