Merge Byline Attempt with airSlate SignNow

Merge initial request

hi this is francis potter senior solution architect with git lab i'm here to talk about merge trains today actually i'm going to talk about pipelines for merge requests and pipelines for merged results they're different and merge trains and i'm going to try to explain it as well as i can understand and we'll see some of the kind of quirks and weirdnesses along the way so let's dive in first off when does get lab run pipelines i'm going to start very simple here there are a whole bunch of events the trigger pipeline runs within gitlab a new commit a new branch a new tag those all have to be pushed if you're working locally of course you can run jaw you can run pipelines manually you can use do it through an api call you can do it on as a scheduled pipeline run there are a whole range of different things that trigger pipeline runs and it's important to understand these now there is a variable that you get in gitlab ci that helps you understand what caused your pipeline to be run it's called ci pipeline source um excuse the fact that this is all lower case it should be uppercase and it has a very specific set of values and only have one of these values to tell you what's triggering the run of your pipeline so i'm not going to dive into all of these but there are a couple of them that are really important to understand the first is that a push pipeline covers new commits new branches and new tags and if you're working locally and pushing then there's push pipeline for that but also if you're working in the ui you're also pushing and that includes if you click the new branch button on the branches page or you click the create a merge request from this issue button on the issues page which creates a branch those actually generate a push which generate a pipeline and it's important to recognize that also important to recognize that a push action can trigger multiple pipelines and i know of three cases where i can trigger multiple pipelines one is if you have multiple branches in the same push it'll trigger multiple pipelines if you have multiple tags in the same push it'll trigger multiple pipelines or if you're inside a merge request and you have both merge request pipelines which we'll get to and push pipelines in the same pipeline you'll run two potentially on the same commit which can be really weird so we're going to talk today mostly about merge request event but it's important to kind of have this in the context of the different things that cause a pipeline to run uh if you look in the pipelines list view right next to like like halfway through the middle there's a little icon and it's one of these three as near as i can tell...