---
title: "Blog — Page 2 | Clarive"
description: "DevOps insights, tutorials, and best practices from the Clarive team."
url: "https://clarive.com/blog/page/2"
---

# Blog

Page 2 of 8

[![Bringing DevOps to the Mainframe (4/4)](https://clarive.com/images/blog/bringing-devops-to-the-mainframe-44.webp)May 3, 2018·5 min readBringing DevOps to the Mainframe (4/4)In this last installment of this series, we will review how Clarive can replace z/OS SCM tools such as CA Endeavor or Serena ChangeMan with a global DevOps pipeline that can drive unified deployments across all platforms.![Ricardo Martinez](https://clarive.com/images/authors/ricardo.png)Ricardo Martinez](https://clarive.com/blog/bringing-devops-to-the-mainframe-44) [![Entrega de aplicaciones móviles en 5 minutos](https://clarive.com/images/blog/entrega-de-aplicaciones-moviles-en-5-minutos.webp)April 30, 2018·3 min readEntrega de aplicaciones móviles en 5 minutosEn esta entrada vamos a explicar cómo realizar despliegues de aplicaciones utilizando Clarive EE tanto a la tienda Google Play Store, como a la tienda de iOS (Apple Store) gracias a los Clarive Plugins.![Rodrigo Gonzalez](https://clarive.com/images/authors/rodrigo.jpg)Rodrigo Gonzalez](https://clarive.com/blog/entrega-de-aplicaciones-moviles-en-5-minutos) [![Why continuous delivery should run in containers](https://clarive.com/images/blog/why-continuous-delivery-should-run-in-containers.webp)April 27, 2018·4 min readWhy continuous delivery should run in containersThe situation with the DevOps toolchain is that it just has too many moving parts. And these moving parts have become a cumbersome part of delivering applications.![Rodrigo Gonzalez](https://clarive.com/images/authors/rodrigo.jpg)Rodrigo Gonzalez](https://clarive.com/blog/why-continuous-delivery-should-run-in-containers) [![Continuous release readiness checklist](https://clarive.com/images/blog/continuous-release-readiness-checklist.webp)April 25, 2018·6 min readContinuous release readiness checklistARA is a key DevOps discipline that deals with managing the software and infrastructure changes brought about by a new release. In order to gain a clearer understanding of ARA, we could say that the development lifecycle involves two main areas:![Elena Gómez Illán](https://clarive.com/images/authors/elena.jpg)Elena Gómez Illán](https://clarive.com/blog/continuous-release-readiness-checklist) [![Bringing DevOps to the Mainframe (3/4): Source code versioned in z/OS](https://clarive.com/images/blog/bringing-devops-to-the-mainframe-34-source-code-versioned-in-zos.webp)April 24, 2018·2 min readBringing DevOps to the Mainframe (3/4): Source code versioned in z/OSIn this installment of this series we will review how Clarive drive popular z/OS SCM tools such as CA Endevor or Serena ChangeMan as part of your global DevOps pipeline.![Ricardo Martinez](https://clarive.com/images/authors/ricardo.png)Ricardo Martinez](https://clarive.com/blog/bringing-devops-to-the-mainframe-34-source-code-versioned-in-zos) [![Scheduling your pipeline stages](https://clarive.com/images/blog/scheduling-your-pipeline-stages.webp)April 20, 2018·3 min readScheduling your pipeline stagesRunning pipeline jobs to critical environments often requires a scheduled execution to take place. Clarive scheduled jobs run always in 3 main steps, called "Pre", "Run" and "Post".![Rodrigo Gonzalez](https://clarive.com/images/authors/rodrigo.jpg)Rodrigo Gonzalez](https://clarive.com/blog/scheduling-your-pipeline-stages) [![Bringing DevOps to the Mainframe (2/4): Tooling](https://clarive.com/images/blog/bringing-devops-to-the-mainframe-24.webp)April 16, 2018·4 min readBringing DevOps to the Mainframe (2/4): ToolingIn this second part of this blog series we will detail the mainframe features you can find in Clarive and how they are integrated into the system.![Ricardo Martinez](https://clarive.com/images/authors/ricardo.png)Ricardo Martinez](https://clarive.com/blog/bringing-devops-to-the-mainframe-24) [April 6, 2018·2 min readQA Automation: building test plans with Clarive\*![Manuel Touriño](https://clarive.com/images/authors/rodrigo.jpg)Manuel Touriño](https://clarive.com/blog/clarive-test) [April 6, 2018·4 min readBringing DevOps to the Mainframe (1/4)The DevOps movement in general, tends to exclude any technologies that are outliers to the do-it-yourself spirit of DevOps. This is due to the nature of how certain technologies are closed to developer-driven improvements, or roles are irreversibly i...![Ricardo Martinez](https://clarive.com/images/authors/ricardo.png)Ricardo Martinez](https://clarive.com/blog/mainframe) [March 27, 2018·6 min readClarive 7.0.13 released with custom kanban card layoutsThis release contains a lot of minor fixes and improvements from 7.0.12\. It is also focus on refactoring interface improving the kanban boards.![Ricardo Martinez](https://clarive.com/images/authors/ricardo.png)Ricardo Martinez](https://clarive.com/blog/clarive-7-0-13-released-with-custom-kanban-card-layouts) [March 23, 2018·6 min readKill remote processes on job cancelClarive 7.0.13 introduces a new feature that allows remote jobs to be killed when a pipeline job is cancelled.![Ricardo Martinez](https://clarive.com/images/authors/ricardo.png)Ricardo Martinez](https://clarive.com/blog/kill-remote-processes-on-job-cancel) [March 19, 2018·6 min readWhy environment provisioning is a key part of DevOps?Environment provisioning is a key part of a continuous delivery process. The idea is simple: we should not only build, test and deploy application code, but also the underlying application environment.![Rodrigo Gonzalez](https://clarive.com/images/authors/rodrigo.jpg)Rodrigo Gonzalez](https://clarive.com/blog/why-environment-provisioning)
