Deploying a basic Serverless application has been made easy with the abundance of frameworks out there. If you’re part of a small team or working on a relatively simple project, setting up a basic serverless CICD process is also pretty straightforward, since there is plenty of information on the subject. But when a Serverless application grows it can get very complex very fast.

Did your build fail? Would you need more info than what you find in the log? No problem, use Rebuild with Remote Access and check the build on the VM itself. Good news for anyone on a quest of debugging. ⚔ If you go to your app on Bitrise, and then to the failed build's page, you'll find a new button there: Rebuild with Remote Access. This will trigger a new build with the remote access enabled.

Today’s consumers expect continuous improvement in the apps they use. As a result, cloud-based application development teams need to innovate and release new app services and updates continually. An efficient alerting mechanism that augments the Continuous Integration and Continuous Delivery (CI/CD) pipeline is crucial to support this engineering and product velocity.

In software development and IT, a mindset of continuous iteration and improvement leads to faster delivery of reliable applications and infrastructure. But, part of continuous improvement is continuous testing. And, continuous testing naturally leads to improved monitoring and alerting and teams implementing chaos engineering practices and principles.

Infrastructure management has come a long way. (Mostly) gone are the days of manual configurations and deployments, when using SSH in a “for” loop was a perfectly reasonable way to execute server changes. Automation is a way of life. Configuration management tools like Chef, Puppet, and Ansible — once on the bleeding edge — are now used by most enterprises.

Continuous integration, and automation in general, is arguably extra important when working on an open source project that anyone can contribute to. Especially if a project starts gaining momentum, automating different kinds of tasks — from building and testing the project, to ensuring a consistent code style — can be truly essential in order for all contributors and maintainers to stay productive.

We’re on the verge of something here, people. A growing number of companies are shipping software in minutes. Yeah, you read that right. Minutes. Not hours, not weeks, months, or longer. Minutes. Often, teams struggle to ship software into the customer’s hands due to lack of consistency and excessive manual labor. Continuous integration (CI) and continuous delivery (CD) deliver software to a production environment with speed, safety, and reliability.

CI/CD stands for Continuous Integration/Continuous Delivery/Continuous Deployment, terms often used in modern software development. Continuous Integration is the practice of merging all of a developer’s working copies to a shared repository multiple times a day. The main idea behind this is to prevent “integration hell”.

DevOps is all the rage right now, and it is only the beginning. In this blog, I’ll cover how to get started with Talend continuous integration, delivery and deployment (CI/CD) on Azure. The first part of the blog will briefly present some basic DevOps and CI/CD concepts. I will then show you how the Talend CI/CD architecture and how it fits in Azure ecosystem with a hands-on example.