Every year, iThome hosts a challenge where IT practitioners write a blog post every day for 30 days. (iThome is a well-known IT news media in Taiwan.)
This year, I decided to join this challenge and chose a frequently asked question: ‘Why do you pay for GitLab?’ as my topic.
You can find all 30 posts on iThome’s website. If you’re interested, feel free to check out the links below.
Notice: All posts are written in Traditional Chinese. I only translated the article title into English.
Since I decided to join the challenge at the last minute, there were some days when I struggled to find inspiration for my topic. Plus, the quality of some posts might not be the best.
Introduction
This is a pretty bare-bones introduction where I’m just documenting my initial thoughts about joining the challenge.
Why do companies pay for software?
Individuals and businesses have different needs and priorities when it comes to paid features.
- Day 2: Enterprise Features Might Not Be What You Think
- Day 3: What Features Do Enterprises Actually Care About?
Introducing GitLab’s Paid Features
I introduced several paid features of GitLab.
- Day 4: GitLab Geo: A High Availability Solution for Self-Hosted GitLab
- Day 5: How to avoid AD failure affecting login to GitLab?
- Day 6: Customized user permissions
- Day 7: Audit, Stay Away, There’s Nothing Worth Checking Here!
- Day 8: Prove the Effectiveness of Your DevOps Adoption with Metrics!
- Day 18: Security Feature - Pre-build scanning
- Day 19: Security Feature - Post-build scanning
- Day 21: GitLab’s AI Feature - GitLab Duo
- Day 22: GitLab’s Incident management Feature
- Day 23: GitLab’s Portfolio Management Feature
History and Feature Development of GitLab
Notice!
In these articles, I just read the public history of GitLab and each release note, and then I excerpted some information based on my own interests. Therefore, these articles are more like my personal notes, and the most readable parts are the thoughts at the end of each article.
- Day 9: GitLab The One (Fill in some keywords) Platform
- Day 10: History and Feature Development of GitLab Part 1 (2011-2015)
- Day 12: History and Feature Development of GitLab Part 2 (2016-2017)
- Day 13: History and Feature Development of GitLab Part 3 (2018)
- Day 14: History and Feature Development of GitLab Part 4 (2019-2020)
- Day 15: History and Feature Development of GitLab Part 5 (2021-2022)
- Day 17: History and Feature Development of GitLab Part 6 (2023-2024)
Product Direction of GitLab
While tracing history and feature development of GitLab , it’s inevitable to also pay attention to product direction of GitLab. Therefore, I’ve also looked into some related content.
- Day 16: Product Direction of GitLab - ModelOps
- Day 20: Product Direction of GitLab - Software Supply Chain Security
- Day 24: Product Direction of GitLab - Monitor:Observability
Introducing two GitLab teams
I’ve chosen two GitLab teams that I find particularly impressive to introduce.
Introducing Useful Tools Developed by GitLab Quality Department
GitLab has actually released many great tools to the public, but you need to do some digging to find them. This time, I’ve discovered a few tools to share with you.
- Day 25: Testing Your GitLab Performance Part 1 - Generate Some Fake Data First!
- Day 26: Testing Your GitLab Performance Part 2 - Run Performance Tests!
- Day 27: Testing Your GitLab Performance Part 3 - GitLab Browser Performance Tool
- Day 28: Generate More Fake Data for Your GitLab
- Day 30: Are You Analyzing Your CI/CD Pipeline Efficiency?
