Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
Bitbucket Pipelines is one of my favorite CI/CD tools, and I use it pretty heavily daily. Given the full range of use cases available for Pipelines, I have to frequently diagnose and debug new issues, and this process of debugging starts with being able to replicate the problems in my local environment quickly.
I’m going to walk you through the process of replicating a serverless deployment locally. For this exercise, I’ll use this serverless deployment as a reference.
I recently had a use case where I wanted to clone another Bitbucket repository during a Pipelines execution. Doing this is very simple, but there is a lot of conflicting information online, so I thought I would document the steps here.
Imagine a very simple Pipeline that looks like this:
Traveler.today makes local travel guides for tourists and self-explorers. We create a different app for each location because each of our apps is made for a different partner/customer.
As our business started to grow, we needed to create multiple new apps per week and it started to take too much time away from the whole team. It interrupted our development work as we would spend most of our time supporting releases. For each new app, it took several hours to configure the server, build and deploy a new application, update the database, fill metadata, etc.
Bitbucket now offers pre-built Pipes to deploy Lambdas to AWS. But what if we want to deploy an entire Serverless stack? That’s what we’ll talk about today.
The Serverless framework is a vendor-agnostic, declarative, and configurable framework. We use it to deploy Lambdas and their dependencies. We define our stack as a YAML file, and Serverless takes care of resource management.
Angular is one of the most widely used JavaScript frameworks. But though the builds are easy, developers face issues when configuring deployments and setting up CI/CD pipelines. This post outlines the steps required to deploy an Angular application to a Google VM using Bitbucket Pipelines.
Bitbucket Pipelines allow developers to configure continuous delivery (in the cloud) of source files to test/production servers. These pipelines are configured to connect to the production server using YAML scripts.
The democratizing nature of DevOps has seen the responsibility of building and managing CI/CD pipelines transition from specialized release engineers to developers. But automating a robust, dependable CI/CD pipeline is tedious work. Developers need to connect to multiple tools to deliver software, and writing pipeline integrations for these services is a manual, error-prone process. There's research involved to ensure dependencies are accounted for, as well as debugging and maintaining integrations when updates are made. It's no wonder many teams put automating CI/CD firmly in the "too hard" basket.
Bitbucket Pipelines is a CI/CD tool in the cloud that's part of your repository and makes it easy for developers to configure pipelines with code. We are launching Bitbucket Pipes to make it easier to build powerful, automated CI/CD workflows in a plug-and-play fashion without the hassle of managing integrations. We've worked with industry leaders including Microsoft, AWS, Slack, Google Cloud, and more to build supported pipes that help automate your CI/CD pipeline, and made it simple to create your own to help abstract any duplicated configuration across your repositories.