Source control, aka version control, is the method of tracking and managing changes to software code. Source Control Management (SCM) systems offer a running history of code changes and can be particularly helpful for teams of developers making changes to the same files. As a critical aspect of responsible software development, source control helps developers track code changes, see complete revision history, and revert back to a previous version of a project if needed.

You probably missed it. Don’t feel bad. It was just one small paragraph, buried in the GitLab 11.9 Omnibus Release Notes: Grafana is now bundled in our Omnibus package, making it easier than ever to understand how your instance is performing. “Omnibus” is what GitLab calls its main installation package, and “Grafana” is the time-series visualization software, but what does this paragraph even mean?

In this blog post, you will learn how to setup image scanning with Github Actions using Sysdig Secure DevOps Platform. We will create a basic workflow to perform a local scan to detect vulnerabilities and bad practices before the image is pushed to any registry. We will also customize scanning policies to stop the build according to a set of defined rules.

There has never been more pressure on development teams to build software faster and more efficiently. The rise in popularity of DevOps has largely been the result of its promise to speed up dev cycles, increase agility, and help teams resolve issues more quickly. And while the availability and sophistication of DevOps tools have improved greatly in the last few years, simply choosing the latest and greatest tools is no guarantee of a smooth, problem-free development lifecycle.

The typical workday for a developer using Git involves a variety of different tasks. Between generating new SSH keys, cloning Git repositories, viewing commit diffs, creating pull requests, and on and on. But do you ever sit back and think about how much time you’re spending on each of these seemingly smaller tasks? Trust us, it adds up. The concept for the GitKraken Git GUI was born from this very frustration.

Whether you’re a product owner, project manager, or the CEO of the company, understanding how your team plans for and achieves project milestones is crucial to reaching long-term and sustainable success.

In part 1 of the GitOps blog series, we discussed the value of using GitOps for Calico policies, and how to roll out such a framework. In this second part of the series, we will expand the scope to include decentralized deployment and GitOps.

At first glance, storing Kubernetes secrets seems simple enough. Kubernetes stores them automatically in etcd, a key-value store. And, Kubernetes can be configured to encrypt these secrets by default to help keep them secure. That’s all good and well if you’re content with keeping your secrets inside Kubernetes. But, what if you want to keep external copies of your secrets, rather than just relying on Kubernetes and etcd?

At Sentry, we’re big fans of continuous integration and deployment. We’re also big fans of GitHub — and not just because we employ a number of notable GitHub alumni. We use our own GitHub integration to link issues, identify suspect commits that likely introduced new errors, and suggest assignees who can best resolve each issue. Last month, GitHub released GitHub Actions for general availability.