1. Switzerland GitLab meetup: First time GitLab & CI/CD workshop with Michael Friedrich

[@pollcon]

CI/CD starts @ 18:13

[@michi_gl]

Thanks for flagging, I've updated the video description :)

[@jillanemcghee5927]

Thank you Michael! As a regular GL user, I was mostly interested in the CI/CD part of your vid, but I thought what the heck, you can always discover new things about things you think you know, so I watched this vid. Very detailed and comprehensive. You sure know your stuff! Thanks for doing this and for lots of helpful tips and info.😊

[@pavelzarembo4880]

Thanks for this nice piece of GitLab wisdom, very well explained by the way ) Without too much talk and with sufficient practice examples.

[@mironovsan]

The repository is not available anymore :(

[@mindmantra-digital]

Actual content starts at 4:39

[@dnsmichi]

Thanks, I have edited the description and added all topics with timestamps to the agenda.

[@h3ct0rjs]

Thank you very much.

[@BibleStoriesandBeyond]

Nice sharing!

[@michaelulloa12]

Do you have the blog post for 25:20?

[@dragonliu1548]

挖槽，一句没听懂 。哈哈

[@mic_y]

Am I just one who heard Hitler instead of GitLab every time?.. XD

[@joh5299]

I am a bloody beginner with Gitlab CI and I have tried this example (beginning ca. 28:00) without success. I have tried it with my own project and I use the community version of Gitlab (Self hosted). Is that ok? I could create the merge request with the ci-config branch and the .gitlab-ci.yml But Gitlab seems to hang forever on "Checking pipeline status". I have realized the I don't have a "Submit Request" button in 29:46, but a "Create Request" button. I clicked that. I never get your picture in 29:49, there is always the sandbox on "Checking pipline status".

[@joh5299]

Hi again. I could meanwhile manage the Gitlab CI myself, with other tutorials, but mostly on my own since almost all tutorials are WAY TOO COMPLICATED IMHO. First, you must try to enable the CI/CD buttons in your project, they were hidden in mine for some reason. Unfortunately, this option is buried in the Gitlab settings. Then, you must explicitely install a Runner in your Gitlab server (oh, and before that, a Ruby On Rails Console for Gitlab). For starters, the most simple, i.e. Shell Runner, is the best. It is much better first to try the most simple pipeline in the shell, without docker, kubernetes, and without complicated code. And use 2 stages (build and test), no more. Also, if you use Shell Scripts for the Pipeline Jobs, you must query the compiler results with $? and explicitely exit with non-zero. Otherwise the shell will happily terminate sucessfully on build/test errrors, and your pipeline will also be successful (even if it is not). This is just right of my head, I had much more issues. Just if some other person would find this useful.