August 2016 Summaries

The Quay by CoreOS integration with the Codefresh platform has been announced, offering users the ability to use Quay as their Docker registry with Codefresh through a straightforward setup. Quay.io provides a hosted service for building, analyzing, and storing container images, featuring an intuitive interface with detailed information and reports. This integration allows organizations utilizing Quay.io to benefit from Codefresh’s Docker-native CI/CD features to automate and collaborate on their Docker applications. By combining these platforms, users can effectively manage their entire build, test, and deployment pipeline while gaining insights at every stage. Additionally, the integration supports any private Docker registry, enhancing the continuous integration experience. Instructions are provided for integrating a Codefresh account with Quay.io or a private registry to facilitate image management across projects, with the option to sign up for a free Codefresh account if needed.

Developers using Docker benefit from the ability to quickly build and test various code and environment combinations through container-based development, allowing for efficient blue-green deployment and A/B testing. However, resource limitations on development machines may require the removal of images and termination of containers to manage and run new versions effectively. To aid in this process, command-line tricks such as forcing the removal of images with 'docker rmi -f' can help clean up the working environment. Additionally, when using the 'docker ps' command, omitting the ':<tag>' will list only containers based on the 'latest' tag of a specified image. The text encourages sharing additional tips in the comments and mentions Codefresh, a Docker automation and collaboration platform for agile teams, offering free accounts to users.

The blog post discusses challenges and solutions in handling error reporting for Node.js servers, particularly focusing on the issues that arise when multiple errors are generated from a single request, leading to a loss of information about the original error. Codefresh explored various methods for chaining and aggregating errors, initially experimenting with the WError module but ultimately developing their own error handling module called CFError. This module allows for a streamlined error reporting process by wrapping and chaining errors, ensuring all relevant information is retained and easily accessible. Additionally, Codefresh addresses the issue of false alerts in monitoring systems by introducing a 'recognized' field to differentiate between genuine errors and expected system behavior, using the CFError's 'getFirstValue' function to retrieve this field's value throughout the error chain. This approach aids in maintaining accurate monitoring and reporting, crucial for identifying and solving problems effectively.

Containerizing applications, which involves running them inside containers using platforms like Docker, offers numerous advantages but requires careful consideration of the app's design and configuration. The process is particularly suited for stateless applications, providing a simpler path to elastic scaling, although stateful applications can also be containerized with additional complexities. Effective containerization involves creating platform-agnostic apps, separating environment configurations from the application itself, and ensuring containers house single processes to maintain clean deployments. This separation allows for independent management of application builds and environment configurations, promoting a single build artifact deployable across various environments. To achieve efficient containerization, familiarity with principles such as those found on the 12Factor site is beneficial, as they guide building apps to run as services. Additionally, tools like Codefresh can streamline the containerization process, making it less daunting by automating many tasks involved. The author, Matthew Oaks, a Lead DevOps Engineer, emphasizes the importance of these practices while noting his own journey from software engineering to DevOps, driven by a passion for configuration and monitoring.

Integrating Jenkins and Codefresh offers a solution for development teams seeking to leverage both traditional CI systems and container-native CI/CD platforms, particularly in light of the increasing adoption of Docker containers. Many organizations have invested in Jenkins for their continuous integration needs; however, not all software components in a build process are suited for containerization, necessitating the use of a traditional CI server for external components like libraries and modules. By combining Jenkins with Codefresh, a container-native CI tool, teams can efficiently manage non-containerized components alongside Docker-based application images. This integration, facilitated by a plugin, enables seamless execution of Docker builds and tests through Codefresh, with results reported back to Jenkins, thereby enhancing existing continuous delivery pipelines and improving development and testing workflows.