January 2019 Summaries

CircleCI has revamped its hiring process for engineering managers to better align with the distinct skills required for management roles, shifting away from the previous approach of hiring managers as if they were engineers. The company realized that focusing heavily on technical skills was not effective for identifying suitable candidates for management positions, leading to a redefined process that emphasizes people management and business value delivery. This new approach involves structured, behavior-based interviews that assess a candidate's management experience, collaborative problem-solving abilities, and understanding of product and delivery from a customer value perspective. By doing so, CircleCI aims to hire engineering managers who are committed to personal and professional growth, capable of supporting teams through the product delivery process, and aligned with the organization's evolving values. The changes have enabled CircleCI to double its engineering management team while maintaining a focus on leadership and organizational alignment.

DevSecOps integrates security into modern development workflows by embedding security practices into the tools developers already use, such as CircleCI, allowing continuous application of security standards during the build and deploy process. By scanning container images before they are deployed, DevSecOps provides immediate feedback to developers, preventing insecure or non-compliant workloads from entering production. Automated security and compliance quality gates are established in consultation with security teams and are integrated into the CI/CD process, enabling developers to address vulnerabilities early in development. The Twistlock orb in the CircleCI Orb Registry allows integration of Twistlock's scanning capabilities via the twistcli command-line tool, which can assess images for vulnerabilities and compliance issues without needing a native plugin. Users can customize scan settings to block builds that don't meet security requirements, and scan results are accessible in both CircleCI and the Twistlock Console. The integration of security into DevOps workflows is exemplified by Jeremy Adams' work with Twistlock, where he leverages his extensive IT operations experience to help cloud-native partners release secure applications.

CircleCI build pipelines are configured in a .circleci/config.yml file, which differs from the configurations used in other CI/CD services like Travis CI. Developers looking to migrate their projects from Travis CI to CircleCI may find the differences in configuration daunting. This guide aims to help by comparing the core elements of Travis CI build configurations with their CircleCI equivalents, despite the inherent differences between the two systems. It provides a reference table to assist developers in understanding how to translate specific build elements from Travis CI to CircleCI, facilitating a smoother transition. Additionally, the guide encourages developers to consult CircleCI's documentation for practical migration examples and to engage with the CircleCI community for support.

The text discusses the complexities of modern software systems and how cloud engineering, particularly using tools like Pulumi and CircleCI, can simplify managing infrastructure as code. It highlights how cloud engineering integrates closer with application development, enabling faster innovation and collaboration across teams using practices like continuous integration and test-driven development. The tutorial illustrates deploying an example application using Pulumi's TypeScript SDK on Google Cloud Platform, emphasizing the use of CircleCI orbs for clean, declarative CI/CD workflows without ad-hoc scripts. The integration with existing systems allows for easy auditing of changes and seamless interaction with platforms like GitHub, ensuring transparency in cloud infrastructure modifications. The text concludes by encouraging the use of Pulumi and CircleCI to enhance continuous deployment processes and invites users to explore these tools by setting up a free account and experimenting with workflows.

Codecov is a tool designed to provide developers and teams with detailed insights into their code's quality by offering integrated solutions for managing and analyzing code coverage reports. Initially created to address a developer's personal challenge in efficiently tracking test coverage, Codecov has evolved into a widely adopted resource used by individual developers, open source projects, and large enterprises alike. By integrating Codecov with CI/CD providers like CircleCI, teams can elevate code coverage from a solitary task to a collaborative team activity, ensuring that commits are thoroughly tested before merging into the main codebase. Codecov's features facilitate a deeper understanding of test coverage, promoting improved code quality over time. The recent partnership with CircleCI introduces a Codecov orb, simplifying the process of uploading coverage reports and enhancing the overall efficiency of achieving and monitoring code coverage metrics. Tom Hu, an advocate for code coverage and an experienced software engineer, highlights the benefits of such integrations, emphasizing the importance of cohesive tools in improving software development workflows.

Ghost Inspector provides an automated browser testing service that simplifies the process of creating, managing, and executing tests from the cloud, enabling QA teams to test more thoroughly and deliver more consistently. By integrating with CircleCI through orbs, Ghost Inspector allows for seamless incorporation of browser-based tests into deployment workflows with minimal configuration. This integration facilitates executing test suites in a repeatable fashion, using real browsers to mimic user actions, and offers the flexibility to parameterize and modularize tests. The use of CircleCI orbs has streamlined the configuration process, reducing code complexity while allowing for effective testing against various environments. This setup helps prevent issues from reaching production by updating test statuses within CircleCI workflows, thereby enhancing the efficiency of DevOps processes.

Continuous integration (CI) tools, traditionally used for running tests and reporting results, have evolved into versatile computing environments that can manage tasks like building and deploying documentation. Leveraging CI platforms for documentation deployment can provide a seamless workflow, particularly when using tools like CircleCI to automate the deployment of documentation to GitHub Pages. This setup is beneficial for teams already utilizing these platforms for code hosting and automated testing. Documentation deployment can be done using language-specific tools such as sphinx for Python or javadoc for Java, and hosted on services like Read the Docs, which automatically builds and renders documentation upon code updates. However, for teams working with multiple languages or needing specific dependencies, hosting documentation within a CI environment and deploying it to destinations like GitHub Pages or Amazon S3 can be more efficient. GitHub Pages offers three deployment options, including deployment to a separate gh-pages branch, rendering the main branch, or a docs directory, each with different workflow implications. The process involves creating a CircleCI workflow that builds, tests, and deploys the documentation, while also handling credentials and permissions to ensure secure access. This method, as implemented by teams like Mozilla's data platform team, allows for autonomy in managing documentation workflows and reduces the need for additional tools, while being adaptable to different programming languages and infrastructures.