If y'all are interested in more Gitlab and Gitlab-CI Videos, check out my playlist: kzfaq.info/sun/PLu-nSsOS6FRLA_6gcYKS0lGzZ4dkracbt
@mylesedwin43283 жыл бұрын
i know I am pretty off topic but do anyone know of a good place to watch newly released tv shows online ?
@santinozakai70113 жыл бұрын
@Myles Edwin Lately I have been using FlixZone. Just search on google for it =)
@timothykenneth49253 жыл бұрын
@Santino Zakai yup, I have been using flixzone for since march myself :)
@mylesedwin43283 жыл бұрын
@Santino Zakai Thank you, signed up and it seems to work :) I really appreciate it !
@santinozakai70113 жыл бұрын
@Myles Edwin glad I could help :D
@MyVirtualboy4 жыл бұрын
Thanks so much for this tutorial, just started using GitLab CI\CD and this explained a lot.
@andrewnaveen5 жыл бұрын
SO HELPFUL.. Thank you so much.. Now I understand why it was setup like this in our projects in my company! I'm trying to learn more about CI in general.
@XNDTECH6 жыл бұрын
Very helpful video, Dan! Please keep making cool contents like this as people who is learning like me highly need and appreciate this kind of content. Thank you!
@GoogleUser-gv2tq5 жыл бұрын
Thank you so much! Great help to get started with the GitLab CI/CD quickly! Keep up the good work!
@chuongtran21916 жыл бұрын
Very good video, Dan. Hope to see more on this topic in the near future. Thanks.
@sachinrastogi97876 жыл бұрын
Hi Dan, awesome video.. looking forward to more on CD via Gitlab
@vimalneha6 жыл бұрын
Helpful video, gave good introduction.
@JeanSergeGagnon4 жыл бұрын
Thanks for great quick tutorial. I'm one of the seasoned git users migrating to GitLab and some of my developers are asking for tutorials on GitLab I'm wondering what you think about fast-forward only merges? I've been thinking that would be preferable in some contexts as you could ensure you already had tests run when merging on the commit being merged in. I guess I'm thinking that a real merge which potentially gives you different code does indeed require a new build and test run but when tests take a long time, it might be preferable to use fast forward merges to avoid double build/test cycles. Have you ever used fast forward merges? One thing I am wondering about is that GitLab seems to tie a pipeline result to a branch commit, not just a commit id... (for example, if you create a new branch off of a commit that has a successful build, that new branch will have same commit id but will not have any build results)
@DanGitschooldude4 жыл бұрын
The fast-forward only merges achieves the stated goal but creates race conditions for large teams and/or long testing times. For example, if 10 people have MRs in testing, and all are ready to be merged, once the first one is merged the other 9 technically need to rebase (to maintain the fast-forward condition) and then re-test (since the code has changed from the rebase). GitLab is aware of this constraint and has released "pipelines for merge requests" and an accompanying "merge train" feature to attempt to mitigate it. I have a video where I talk about this relatively new feature: kzfaq.info/get/bejne/hZedhsty2te2noU.html Thanks for watching!
@cizzlen074 жыл бұрын
Dan Gitschooldude subbed!
@slocomptech6 жыл бұрын
Very helpful video :)
@rezarabbani53353 жыл бұрын
That keyboard
@DanGitschooldude3 жыл бұрын
🤣
@wexwexexort5 жыл бұрын
Hi Dan, I have been using git for a time but never used CI or pipelines. I have a question, I've installed Gitlab-CE self-hosted version and Gitlab-Runner on a different server. I'm creating simple repos containing .txt files and there is nothing to compile yet gitlab automatically sends each commit to a pipeline and they just fails. I didn't add .gitlab-ci.yml into repositories. Do you know how to disable automatic pipeline setting or don't you think it should only create a pipeline if there is a .gitlab-ci.yml file? Thanks for the these great tutorials by the way! PS. I've disabled Auto DevOps.
@DanGitschooldude5 жыл бұрын
Not sure, my first suggestion was going to be check Project Settings / CI-CD / Auto DevOps but it sounds like you already went down that path. My assumption is that no testing will happen unless a .gitlab-ci.yml file exists, but GitLab updates frequently so maybe that behavior has changed. If you figure it out, let us know!
@wexwexexort5 жыл бұрын
@@DanGitschooldude I actually meant to say it's solved after disabling Auto DevOps. I don't know why I didn't say it clearly. :)
@thiagomanhaes12175 жыл бұрын
How did you config the gitlab to automatically create a pull request from your push in 9:15?
@DanGitschooldude5 жыл бұрын
There's no configuration -- I had previously created the merge request so Gitlab had already associated my source branch with that Merge Request.