Operations | Monitoring | ITSM | DevOps | Cloud

CI CD

The latest News and Information on Continuous Integration and Development, and related technologies.

When and Why To Adopt Feature Flags

What if there was a way to deploy a new feature into production — and not actually turn it on until you’re ready? There is! These tools are called feature flags (or feature toggles or flippers, depending on whom you ask). Feature flags are a powerful way to fine-tune your control over which features are enabled within a software deployment. Of course, feature flags aren’t the right solution in all cases.

Default Pull Request Tasks

There are multiple ways to create a task on a pull request. They can be added from the sidebar, top-level pull request comments, file-level comment or inline comments. Once created, they all appear in the sidebar. On any repository, merge checks can be configured for any branch to only allow merging if all pull request tasks are resolved. This is a very useful functionality if some tasks are critical to be resolved before changes are merged.

Automating compliance in software delivery

Software development teams face a large and growing number of obstacles: shifting design requirements, organizational blockers, tight deadlines, complicated tech stacks and software supply chains. One emerging challenge that developers and IT leaders face is the need to stay compliant with regulations and control frameworks that stipulate comprehensive data security, incident response, and monitoring and reporting requirements.

Edge computing vs cloud computing

By now, almost everyone is familiar with cloud computing in one form or another. Throughout the 2010s, the concept of cloud computing evolved within the software industry, then worked its way into everyday life as a universal household term. Somewhat less familiar is the concept of edge computing. The genesis of the “edge” dates to the first content delivery networks in the 1990s. Since then, the edge concept has primarily been the domain of network engineers.

Automate deployment of ASP.NET Core apps to Heroku

Known for its cross-platform compatibility and elegant structure, ASP.NET Core is an open-source framework created by Microsoft for building modern web applications. With it, development teams can build monolithic web applications and RESTful APIs of any size and complexity. Thanks to CircleCI’s improved infrastructure and support for Windows platforms and technology, setting up an automated deployment process for an ASP.NET Core application has become even easier.

CICD Pipeline | Case Study | Razorops | 72pi

72pi is an all in one platform that enables you to compare and adjust your portfolios based on various parameters and complement your investment process and become a smarter investor at portfolio construction. With Razorops they are able to move and fix faster. Efficient feedback and a fast CI/CD pipeline allowed their team to do frequent end-to-end production deployments and get products into customers hands more quickly and efficiently.

Configuring a pipeline using multiple CircleCI orbs

Continuous integration/continuous delivery (CI/CD) tools give developers the ability to automate the software development process. As soon as developers push code to git, your CI/CD system can build, test, stage, integration test, deploy, and scale. That’s fantastic! In this tutorial, we will look at CircleCI orbs and how they can support your CI/CD practice. We’ll look at how to use multiple orbs and how orbs can help with multi-builds for a variety of application types.