GitLab CI/CD is a tool that is built into GitLab. It allows you to create automated tasks that you can use to form a Continuous Integration and Continuous Delivery / Deployment process. You configure GitLab CI/CD by adding a yaml file (called `.gitlab-ci.yml`) to your source repository. This file creates a pipeline, which will then run when a code change is pushed to the repository. Pipelines are made up of a series of stages, and each stage can each contain a number of jobs or scripts.

The standard Command Line Interface for Kubernetes (kubectl) is a very powerful tool for debugging or monitoring purposes. It is very inefficient, but just if you want to get a high-level overview of your Kubernetes cluster or want to work with multiple resources at the same time. A large number of graphical Kubernetes dashboards exist today and chances are that you already used the default Kubernetes dashboard or the one that comes with your cloud provider.

COVID-19 is leading to large-scale migrations away from on-premises environments, according to Codefresh’s second annual State of DevOps survey that revealed this and other surprising insights into the continued evolution of the industry. At the same time, DevOps automation continues to expand in scope and complexity with more and more processes becoming automated, and more involved technologies like Kubernetes continuing to gain strong traction.

Developers understand the importance of keeping their team up to date on work and use many of the integrations between Bitbucket Cloud and Jira like smart commits and automation triggers to do so automatically. However there may be times where there are nuances or uncommon situations when merging a pull request that aren't covered by existing automation rules – sometimes there are multiple pull requests, or sometimes merging means you're now in 'Done' and other times you're in 'Releasing'.

Bitbucket Pipelines provides teams with a one-stop solution to build, test, deploy and track their code, without ever leaving Bitbucket. Developers and release managers can easily track and visualize deployments, while non-technical teams can have visibility into what features are coming down the pipeline.

For the last four years, anyone wanting to deploy the Ingress NGINX Controller for Kubernetes would find its official Helm chart nginx-ingress in the stable repository maintained by the Helm project. Those days are over. And not just for NGINX, the most popular Ingress Controller used as a reverse proxy and load balancer, but for all open-source K8s apps. With the advent of Helm 3, the Helm project is deprecating the stable repositories.

While working from home is the new normal, communicating and collaborating virtually hasn't become any easier. And for developers, being productive while at home has its own set of challenges (we're thinking of things like figuring out how to pair program over Zoom or how to make do with only a single monitor). In times like this, our engineering team has been relying on one short-cut towards productivity: the Bitbucket Cloud bot for Slack.

All deployments are not created equal, but you'd never know it from your Slack channel notifications. In reality, some deployments you really care about, as they contain things like API changes or database migrations, and you want that information to surface. We created tags in Sleuth for this very reason. Out of the box, Sleuth matches files in your deployment with known patterns, and if any are found, tags your deployments automatically.

Being in the DevOps space, we're often asked questions about software deployment like, "What's the difference between continuous deployment and continuous delivery?", "What is continuous deployment?", and "Are continuous deployment and continuous delivery the same thing?" So first, let's start by clearly defining these terms.