Operations | Monitoring | ITSM | DevOps | Cloud

As time goes by, I’m looking for solutions that require as little maintenance as possible. One of those is deploying our client web app and our homepage directly on the CDN edge, with GitHub Actions. Not only we don’t need a server to host the app, but the deployment script is also serverless and maintenance-less. This allows me to focus on important tasks, knowing that deployment and serving of the app is always blazing fast.

It is impossible to overestimate the importance of a strong development environment when scaling your team’s capacity. Nowadays, most organizations use Git, and one of the popular and successful development models used by many organizations is Gitflow. When making use of such models, continuous integration (CI) is key as it enables faster project delivery and offers reduced risk and expenses thanks to self-managed and easy-to-control dedicated teams.

First of all, we’re pleased to announce the first release of the GitHub data source. The source code is available at github.com/grafana/github-datasource. Contributions, feature requests, and bug reports are welcome. Using the GitHub data source, Grafana users can visualize data from GitHub’s API. In this blog, we’ll go over some use cases for this handy plugin.

To help you get the most out of using the GitKraken Git client, we’re bringing back our popular #GitKrakenTip series. These quick tips and tricks will empower you to wield the mighty Kraken and code like you never have before.

Mighty Keif the Kraken has reached across the interweb to join tentacles with his good friend Mona the Octocat once again. 🦑🤝🐙 But this time, it’s all about the issues. The GitKraken Git GUI now supports issue tracking integrations for GitHub and GitHub Enterprise! If you already use GitKraken to manage your GitHub repositories, optimize your workflow even further with new benefits offered in GitKraken Git GUI v7.3.

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.