Operations | Monitoring | ITSM | DevOps | Cloud

CI CD

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

Deploy application environments on demand with the Quali Torque orb

Most developers care about building the next big thing. Automating your build, test, and release processes allows you to maintain focus on innovating and delivering value to your users. By combining the power of best-in-class CI/CD workflow orchestration with managed environments-as-a-service, developers can stay focused on building what’s next.

The Future is Continuous: Integration, Packaging and Delivery - DevOps Institute SKILup Day CI/CD

With the increased focus on software supply chain security, the question arises- what implications does that have for CI/CD processes and DevOps pipelines? Join Dan McKinney, Developer Relations at Cloudsmith for an introduction to Continuous Packaging, and to discuss what it takes to secure build and deployment pipelines at The 2022 DevOps Institute SKILup Day CI/CD.

Synthetic Monitoring for CI/CD Pipelines

For DevOps teams, delivering quality software has long required reconciling a major tension: In a perfect world, you’d catch every issue in each new release of your application before you deployed the release into production. But in the real world, doing so is tricky, not least because it’s hard to collect data about application performance before the application is actually deployed.

Automating Flask deployments with PythonAnywhere

Now that development teams know about CI/CD, there is no reason for deployments to become a time-consuming and cumbersome process. CI/CD may start with continuous testing, but adding automated deployments takes your CI/CD practice to the next level. Continuous deployment slashes the time it takes to release so you can spend more time improving the quality of your applications.

A Guide To Continuous Integration

Before continuous integration was invented, developers had to work on code separately before merging it into the end product. This technique had a high chance of error. If something was left out, it took time to determine the problem. Furthermore, communication between team members became difficult as the project grew. The larger the project, the more developers, engineers, and project owners were supposed to be faithful to each other’s schedules.

Functional vs non-functional software testing

When you think of software testing, what comes up first? For many developers, unit tests and integration tests are often top of mind. Both software testing methods are vital to writing and maintaining a high-quality production codebase. But they are not sufficient on their own. Your team’s testing practice should assess the entire application, observe the larger story of how it operates when functioning correctly, and raise alarms when deviations are found.