A key goal for any DevOps team is to shorten the software development cycle and provide continuous delivery of high-quality software. Instead of continuing to the next logical goal, continuous deployment, most companies stop here. Developed code reaches the testing phase automatically, then, successful testing triggers a manual acceptance step. Only then is the application deployed into production.

.NET is a popular open source, cross-platform development framework for building fast and scalable full-stack applications for the web, desktop, mobile, and the cloud. This flexibility makes.NET a leading platform for developing enterprise web applications and makes.NET development one of the most in-demand skills on the market.

Code signing is an important part of testing and distributing your desktop and mobile applications. It ensures that the end user’s system can verify the legitimacy of your application. Because of the need for security around signed certificates, they are stored locally and not uploaded to the cloud. This constraint could prevent your team from fully automating your CI/CD pipeline.

The MSIX orb is the first “Windows-only” orb from CircleCI. When Microsoft approached us with the opportunity to build an orb that would help Windows developers build on our platform, we were enthusiastic. Most of our orbs, and general workload, revolve around Linux and utilize Bash. However, we recognized the deep need to provide good CI/CD solutions for building applications on Windows, and with use of PowerShell growing steadily within Linux, it was time to take the plunge.

NestJS is fast becoming the de facto framework for NodeJS projects. Unlike older frameworks, NestJS was built with TypeScript, which has become commonplace in the JavaScript community. Frameworks like NestJS seem to be preferred by teams that adopt TypeScript. NestJS supports building APIs in REST and GraphQL. The goal of this tutorial is to show how you can add unit and integration tests to a NestJS GraphQL project and automate the testing process with CircleCI.

AIOps is an approach to managing the exponential growth of IT operations and the complexity of new technology through the application of artificial intelligence (AI). IT infrastructure increasingly relies on complicated deployments, multi-cloud architectures, and huge amounts of data. Traditionally, the tech industry responds to complexity by applying extra brainpower to the problem, bringing in more engineers, developers, and management.

This series shows you how to get started with infrastructure as code (IaC). The goal is to help developers build a strong understanding of IaC through tutorials and code examples. In this post, I will demonstrate how to create continuous integration and deployment (CI/CD) pipelines that automate the Terraform IaC deployments covered in part 1 and part 2 of this series. Here is a quick list of things we will accomplish in this post.

This series shows you how to get started with infrastructure as code (IaC). The goal is to help developers build a strong understanding of IaC through tutorials and code examples. In this post, I will demonstrate how to how to create a Docker image for an application, then push that image to Docker Hub. I will also discuss how to create and deploy the Docker image to a Google Kubernetes Engine (GKE) cluster using HashiCorp’s Terraform.

This series shows you how to get started with infrastructure as code (IaC). The goal is to help developers build a strong understanding of IaC through tutorials and code examples. Infrastructure as Code (IaC) is an integral part of modern continuous integration pipelines. It is the process of managing and provisioning cloud and IT resources using machine readable definition files.