It's easy to think of git clone as a client-side operation, but the settings of this operation impact the server side and all networks in between. When you run a default full history clone, the server has to walk the entire history, build a pack file for it (that's what "counting objects" is actually doing), and ship it over the wire. The client then unpacks all of it and checks out a full working tree.
Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Darwin Sanoy
Automate embedded systems compliance with GitLab and CodeSonar
Continuous compliance verification for ISO 26262, DO-178C, MISRA, and other code quality and functional safety standards. Embedded systems development teams face a persistent challenge: maintaining development velocity while meeting stringent functional safety and code quality requirements. Standards like ISO 26262, IEC 62304, DO-178C, and IEC 61508 demand rigorous verification processes that are often manual and time-consuming.
How GitLab transforms embedded systems testing cycles
BlogEngineeringHow GitLab transforms embedded systems testing cycles Discover how managed lifecycle environments streamline and automate virtual testing, delivering rapid feedback without environment sprawl or cost overruns. Embedded developers know this cycle well: write code, wait days or weeks to test on a hardware test bench, discover bugs, fix them, then wait again.
Supercharge your Git workflows
BlogEngineeringSupercharge your Git workflows Optimize git clone operations in any environment — up to 93% reduction in clone times and 98% reduction in disk space usage — with the Git Much Faster script. Picture this: You're working on the Chromium project and you need to clone the repository. You run git clone, grab a coffee, check your email, maybe take a lunch break, and 95 minutes later, you finally have your working directory.
4 ways to accelerate embedded development with GitLab
Blog Product 4 ways to accelerate embedded development with GitLab Learn how automated hardware testing, standard builds, collaborative workflows, and integrated compliance eliminate bottlenecks in firmware development. DevSecOps platformtutorialfeatures Software in embedded systems is no longer just a part number — it's a critical differentiator. This shift has led to enormous complexity in the firmware running in our cars, airplanes, and industrial machines.
GitLab's On-Premise Device Cloud CI/CD Component Brings Efficiency
Blog In the world of embedded systems development, efficient testing and deployment processes are crucial for success. The GitLab Device Cloud CI/CD component offers a solution to streamline these processes by enabling hardware-in-the-loop (HIL) testing and global device sharing.
Ultimate guide to migrating from AWS CodeCommit to GitLab
On July 25, 2024, AWS made a significant announcement regarding its CodeCommit service. As detailed in their official blog post, AWS has decided to close new customer access to CodeCommit. While existing customers can continue using the service, AWS will not introduce new features, focusing only on security, availability, and performance improvements. This announcement has prompted development teams to consider migrating their repositories to alternative Git providers.
A CI component builder's journey
I've always found it fascinating that my father, a heavy-duty mechanic by trade, would make his own tools for challenging jobs for which his industry had not yet built a fit-to-purpose tool. Little did I realize I'd become a tool builder in IT, which has been one of my loves for many years now. I have been building GitLab includable, shared templates since starting with GitLab over four years ago.
GitLab achieves the AWS DevSecOps Partner Competency Specialty
GitLab recently achieved AWS's DevSecOps Partner Competency desigation, a sub-specialty for the AWS DevOps ISV Partner Competency category. GitLab also holds the AWS DevOps ISV Partner Competency designation. AWS's partner qualification program signifies to customers that AWS has vetted GitLab's capabilities and use cases. Attending AWS re:Invent 2023? Find us at Booth 1152.
Setting Up OpenID Connect with GitLab CI/CD to Provide Secure Access to Environments in AWS Accounts | Amazon Web Services
AWS Partner Network (APN) Blog By Joe Randazzo, Sr. Solutions Architect – GitLab By Darwin Sanoy, Staff Solutions Architect – GitLab By Mark Kriaf, Partner Solutions Architect – AWS When building out a CI/CD pipeline, there are ways to proactively harden your pipelines when they need to access environments in Amazon Web Services (AWS) accounts.
Get started with GitLab EKS Fargate Runners in 1 hour and zero code, Iteration 1
Leveraging Amazon's AWS Fargate container technology for GitLab Runners has been a longstanding ask from our customers. This tutorial gets you up and running with the GitLab EKS Fargate Runner combo in less than an hour. GitLab has a pattern for this task for Fargate runners under AWS Elastic Container Service (ECS). The primary challenge with this solution is that AWS ECS itself does not allow for the overriding of what image is used when calling an ECS task.
Is cloud security too easy to screw up?
This cloud conversation with Troy Hunt, Microsoft Regional Director and founder of Have I Been Pwned, has been edited and condensed for clarity. Forrest Brazeal: Troy, what’s your origin story? How did you become a legend in the world of application security? Troy Hunt: Kinda accidentally, to be honest. My background is in software development; I’ve been developing web apps since I was a teenager. I ended up in the corporate world for 15 years, making myself thoroughly miserable.
Live Coding Conversion of GitHub Action Super-Linter to GitLab CI
2020-06-20 · 566 words · 3 minute read Mission Impossible Code · PowerShell · Live Coding · GitLab · GitLab CI · GitHub In the most recent Mission Impossible Live Coding event, Jefferson and I convert the GitHub Action Super-Linter to run in GitLab CI. This is a summary of lessons learned and pointers to the results. So Jefferson and I worked through this approach. Before the session I played with some ideas and approaches, but ultimately we ended up with a new approach.
Mission Impossible LIVE Coding
2020-05-20 · 551 words · 3 minute read Mission Impossible Code · PowerShell · Live Coding · GitLab · GitLab CI I’ve been working as a Solutions Architect at GitLab for over 6 months now and I’ve met a lot of awesome people and been challenged by a lot of customer requirements. I work on a great team of solutions architects in a part of the company called “Customer Success”.
Human-Processed Code Part 3: A Multiplatform Toolset for Markdown Checklists
GitLab sponsored this post. This article is the third of a series. Part 1 justified that human-performed DevOps checklists are essentially source code, and according to GitOps principles, belong in Git just like any other code required for successfully managing a software stack. Part 2 dug into the rich but often overlooked, support for interactive checklists on GitHub and GitLab. In this article, we dive into the why and how of using rich desktop editing tools for checklist creation and completion.
Part 2: How Checklists on GitHub and GitLab Can Help Team Collaboration
GitLab sponsored this post. This article is the second of a series. Part 1 justifies that human-performed checklists are essentially source code, and according to GitOps principles, belong in git just like any other code required for successfully managing a software stack. Checklist Awareness and Skepticism Darwin Sanoy Darwin, a senior solutions architect for GitLab, has had a passion for all things Cloud, DevOps and CI/CD during his automation-focussed career.
Why Human-Processed Source Code Belongs in Git
GitLab sponsored this post, in anticipation to GitLab Commit London October 9. Darwin Sanoy Darwin is a senior cloud architect and a DevOps tooling team lead at Infor. His career focus on automation has led to a passion for all things Cloud, DevOps and CI/CD. He resides near Philadelphia with his two children and wife. When he’s not out on the trail trying to break his mountain bike, he’s in the garage tuning it.
Logging and Error Handling Best Practices for Automating Windows Update Installs (MSU) with wusa.exe (And For Logging Any Called Process)
Automation of Windows Updates is generally done by calling wusa.exe against a .MSU file. When wusa.exe experiences a failure the messages are typically obscure and hard to diagnose. The underlying error messages, however, are frequently easy to understand and resolve. The secret is to have wusa.exe do verbose logging in it’s standard exported windows event format and then use the PowerShell event message CMDLets to query that log - automatically, everytime you have an error.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Darwin
Contact Darwin, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack