After my last blog around sending Github Data to Splunk via Webhooks, I received a healthy amount of feedback that I want to address here. I learned that (unsurprisingly) a lot of customers are curious about, or dependant on, other cloud platforms out there. In fact, I heard directly from some customers who specifically cannot use any other cloud platforms than one in particular that was not highlighted in my last blog.
Time trolls people. It speeds up in good times and slows down in bad. For instance, when you push code, your brain feels like it’s in a whirlwind. But when you’re debugging subsequent errors, the hours seem to slog by. This is particularly true if you are operating without context and without the help of automation. Fortunately, our friends at GitHub built an automation platform for products like Sentry to integrate with: Sentry Release GitHub Action.
The latest release to GitKraken Boards is nothing short of monumental, including a Trello importer, giving users the ability to copy Trello boards with full card details into GitKraken Boards, and a complete makeover of the Home Screen, including board starter templates. GitKraken Boards: Now with Trello Importer! Sign Up for GitKraken Boards Free.
The GitKraken Git GUI now integrates with Trello as an issue tracker! You can now manage your Trello issues directly from the GitKraken ecosystem. This allows developers to stay focused on the lines of code in front of them, while also staying on top of personal and team assignments. You no longer have to leave the GitKraken Git GUI to do the following: *Paid features. The Trello integration isn’t the only treat you will enjoy courtesy of the GitKraken Git GUI v7.1 release.
What does ‘diff’ mean in Git? In this beginner Git tutorial, we will walk you through the concept of a diff and the benefits of using a robust diff tool, like that offered in the GitKraken Git GUI.
So, you want to plan a product release? Well, let’s be honest, no one really wants to plan a product release; it’s a complex and exhausting process that requires the buy-in of various people across your organization.
An SCM such as Git is more than just a database for source code. It’s not only the thing you need to interact with to get code to production, but also a log of changes on a project. It’s not just the last couple of weeks of commits that are worth looking at. Any commit remains relevant weeks, months and years later. A commit serves multiple purposes. The first one is to explain a change during its review and the second is to explain a change to a future reader.
We’ve always been focused on creating tools that make development teams more productive. In 2014, we introduced GitKraken, the legendary cross-platform Git GUI: an intuitive tool to visualize what’s going on under the hood of Git in a way that makes version control less intimidating for individual developers and more scalable for organizations. Next came Glo Boards, a Kanban tool for project managers and developers.
Introduction One of the SRE team’s goals at Moogsoft is to make sure our feature teams have an easy path from local code changes to production. Changes rolling out to production mean new features, bug fixes, optimizations, and more, which translates into value added for our customers. In short, at Moogsoft we are all about making sure our product is continually evolving, and one way the SRE group helps is by building shared Jenkins functionality our engineers understand and can use quickly.
In today’s ever-changing world of DevOps, it is essential to follow best practices. That goes for security, access control, resource limits, etc. One of the most important things in the world of DevOps is continuous integration and continuous delivery, or CI/CD. Continuous integration is a crucial part of an efficient deployment. We are all guilty of repeating manual steps over and over again – especially when it comes to node configuration.
