Saying that, the more we delegate to CI, the more minutes we spend. Today, we don't know about these bugs because CI is taking care of them. That's such a waste of human attention and energy. Twig, Latte, NEON of YAML always had to be checked manually. We had few bugs with renamed classes and constant outside PHP in one project, usually too late or after a detailed code-review. to checking that new pricing has been released, and next month it will cost you much more :). Instead, the CI should be a helpful buddy, that you can delegate any tedious works - from updated, from finding bugs. It's not rare that in smaller companies with up to 15 devs, the CI is set up once for a particular job, but no-one knows how to use it practically. 2020: It's all About CI Minutes, Babyĭuring consulting, I teach companies to switch positions with their CI. it would be $19/user/mo (billed annually, works out to be $228) - a 585% increase!īut today, pricing is about something different. When we got the license in 2017, it was roughly $3.25/user/mo (billed annually, works out to be $39). Before we get into that, I came across post about similar topic back from 2018 - How #GitLab Will Lose Business. In January 2021 Gitlab introduced new pricing. I recall that was a massive spike in developer interest on Twitter just because of this exclusive feature.Īs time went by and both companies grew, GitHub introduced private repositories for free too. That was a game changed, as GitHub had this as paid service. This used to be true back in 2015 when GitLab allowed unlimited private repositories to an unlimited amount of users. Since Azure and GitHub both belong to Microsoft, they probably have an internal bridge with priority speed. Honza Mikes explained it to me: it might be related to Microsoft Azure. But on GitHub Actions, it's a matter of 5-10 seconds. When a new commit was pushed on the former, it took 20-40 seconds until the CI server noticed. Since the switch from Travis/Gitlab to GitHub Actions, we've experienced much faster CI reactions. We run on Gitlab in 2018 because Gitlab had better Docker support in CI. I'm not sure how about 2019 and before because I was not using GitHub.Īctions yet. That was a breaking point for me to give GitHub Actions a try and switch all my open-source projects from Travis to GitHub. Just use SSH Workflow and complete needed ENV variables. Do you want to publish your project via SSH? No need to learn how it works in detail and risk security breaches by invalid configuration. Think of it as a composer package for your CI. Can you imagine configuring your Symfony services config in Javascript? I don't.īut they switched to YAML as well and, as a bonus, added open-source storage for "Workflows". I recall it did not seems useful to me because most of the configuration happened in Javascript. GitHub introduced a new CI service in late 2018. This statement used to be true when the only CI GitHub had was Travis - an external service that got popular mainly thanks to the free tier for open-source projects. They also put effort into improving DX/UX, so these features are easy to use. Honestly, I have trouble finding simple settings like total CI minutes, so I have to call Honza and get mentoring on navigation. I find it as useful as this: "This manual has 100x more pages. When we compare CI services, this is one of the typical arguments for Gitlab. GitLab has Much more Features than GitHub Let's take typical arguments why Gitlab CI is not better than GitHub, one by one. After today's call with one of my clients, I've learned about one benefit of GitHub Actions for private projects I didn't consider before. I assumed they all were at a similar price layer. But I don't have much experience with private projects pricing for this and other services like GitLab or Bitbucket. I'm known for using GitHub, a true paradise for any open-source project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |