gitlab

IIt took a while since my last post, but there was so much to process! Having visited San Francisco after half a week of touristic sightseeing, the GitLab Commit buzz started to fizz at the speakers’ dinner. The actual day started early with a walk down market street, passing the Twitter headquarters and Uber HQ on my left side conspicuously. Being part of the Agile Transformation track, I stayed most of the day at presentations given by my fellow track mates. [Read More]

In preparation for my talk at GitLab Commit, I have asked several people about their experiences with GitLab in larger organizations. It seems it is installed in a lot of cases by developers or system administrators themselves, creating a grassroots movement pushing CI/CD. If you are using GitLab in your company, what are your experiences? I would love to hear from you and created a questionnaire. It is anonymous, and the data won’t be used commercially. [Read More]

One of my dreams has come true! I am going to San Francisco in California! And also for an excellent reason. I am allowed to deliver a talk at GitLab Commit in January 2020! The talk will be about the easy acceptance of GitLab in startup culture versus the more tough environment of the enterprise. GitLab is very popular on the internet and has an excellent reputation amongst developers. The CI feature has been ranked as top of it’s class. [Read More]

Now that my book has been published I have more time to think. It crossed my mind today that my earliest encounter with GitLab was in 2014, when we needed an on-premise git server, and preferably open-source. GitHub was already very popular back then. I remember how smoothly the install was using the Omnibus installer. We were with only 4 developers, and we did not even use issue management or any kind of CI for that matter. [Read More]