Click below to read other articles from our CLI intro series: At the beginning of this series, we looked at the benefits of using the CLI shell on your machine. One of those benefits is the wide range of developer tools available that only have a CLI. In this part of the CLI intro series, we’re going to focus on.
In this article, we will cover how you can combine some of the most powerful tools available to developers–VS Code and Git–to start making meaningful contributions to both open source and private projects. Before we get into driving Git with VS Code let’s start with some background.
Git Integration for Jira Cloud has seen some major updates in the last quarter, including new data residency support for the EU and US regions and a BRAND NEW interface for Jira administrators: giving you more control over managing your integrations and repositories directly from Jira. Let’s dive into the new features and improvements for Git Integration for Jira Cloud.
While doing packaging for Icinga, I noticed we have a lot of YAML files describing GitLab pipelines doing very similar jobs. The same build job across different operating systems. That’s wasteful behaviour, which leads to a bigger workload when it comes to modifying these jobs. Tasks like adding new versions and especially adding new operating systems become tedious. What I’m looking for is a way to have interchangeable values for our building jobs.
In part 1 of the CLI Stands For…A CLI Into Series, we outline why you would want to use the CLI, some of the benefits of doing so, and a bit of CLI history and terminology. In part 2 – An Introduction to Shell Commands, get ready to roll up your sleeves and dive into a deeper understanding of the terminal.
Today I’m back with another integration available for Grafana Cloud, our observability platform that gathers all your metrics, logs, and traces under a single roof with Grafana. I’m going to highlight how you can use Grafana with Gitea, an open source forge software package for hosting software development version control. It uses Git as well as other collaborative features like bug tracking, wikis, and code review. It is a great choice for those who manage Git repositories.
Creating a DevOps workflow to optimize application deployments to your Kubernetes cluster can be a complex journey. I recently demonstrated how to optimize your local K8s development workflow with Rancher Desktop and Skaffold. If you haven’t seen it yet, you can watch it by viewing the video below. You might be wondering, “What happens next?” How do you extend this solution beyond a local setup to a real-world pipeline with a remote cluster?
GitLens users rejoice! This release introduces exciting updates, including preview support for a browser-based editing experience in VS Code online, legendary new GitLens+ features like Worktrees and Visual File History, and more! Keep reading to see what’s new in GitLens 12.
