Optimize Your Deal Pipelines for Quality Assurance with airSlate SignNow

How to create outlook signature

welcome to this video in which I'm going to explain the Qi pipeline in its processes and details so let's jump straight into what I'm going to talk about today I'm going to talk about the Qi pipeline in general and I'm going to walk you through the builds server pipeline and I'm gonna walk you also through the test server pipeline and I will show possible solutions of how to do swarm reviews in this pipeline and I'm also discussing the feedback you receive from the build server the test server or from swarm reviews in general um in the notification sections besides this and walking you through very briefly about Jenkins and how Jenkins setup and how we can use it so yeah let's jump straight into the high level overview the high level overview contains the following elements which is Jenkins swamp discord in mantis so Jenkins is our build server environment where we're going to run builds and we're gonna run our tests besides this we have perforce where all our code lives where all our assets live and purpose is a source control tool and then we have helix swamp which is our interface web interface where we're going to do our code reviews in or our acid reducer and this is also where we receive the feedback where we give feedback in regards to what needs to be changed in our review like in our change list and then we have discord discord as our general team communication platform will be quickly organized or long-term organized things communicate over and we do our teamwork layout and then the last part is mantis mantis is a bug tracking software where we group box where we keep tracks of barks and we assign bugs and all of those three tools notify discord about anything which changes so therefore discourse our notification help the center of all information so this is our general QA workflow so I create a swarm review this swarm review triggers the build server and the build server with this review current review and the build server then will trigger after it's successfully being built test server which runs it's a test on this review and if that has been done the the test server will modified the user if this is not a review if this is a normal build what's going to happen is all the same steps happen the build server builds the test server tests and then at the end the result of everything is our chi is gonna be pushed to steam and at the end the user can react to its this by downloading it and plays or play tests can happen so yeah let's jump straight into the build server of workflow so this is a walkthrough so it's going to happen is that the user triggers a swarm review by creating one this then triggers the build server of this review which then notifies discord hey it has a new review you might want to check it then on build fail so if the result has been failed the build server will update discord which then notifies obviously the user and it also will create update status on swarm and we'll leave a comment on swarm so swarm gets notified hey it fails and swarm will also know then a link to the current builds to see the logs so if the build server passed everything it will trigger the test server that's the easiest pipeline Oh view and optionally - this is if the build server passes everything discord gets notified again and the user gets informed about the results and this is optional and this is the general overview so we have the test server workflow which is very similar to the previous example of the build server just reform dear friends is that the build server will trigger the unpacking of the artifacts off the test server so then the test of it will run its tests upon those artifacts which is already built in stuff and this will on success inform this court so which then informs the user and on fail it will also inform this court which then modifies the user and it will also inform swarm hey something has been built it is okay to you know pass and approve the review and then if it doesn't happen it will inform swarm as well and say like hey the tests have been phased and there's a comment in this so and that's the general overview of what I've just described so let's talk about possible strong review workflow so we have option eight option a looks like the user creates a swan review via p4 which creates a swan review what which creates a swarm review and then the user basically waits the user waits till it gets a notification that it has been created and this is then that the user reviews the swarm review and in this model the build server is not partially there to inform the user hi something has changed you should review this is just I review immediately as soon as I got a response that there has been a review this is for example just for purely artists it's very useful so the second option or option B is the user creates a review which then creates a swarm review it means I have to wait now for a notification so Jenkins were informed me with the results by a dis court that something has happened and this will also update and the swarm review and the user then after it received their information from Jenkins reviews the swarm review because if you want to review something and you might review it manually and you think it looks all fine the code looks fine and you don't necessarily have the time to pull down the code you might not approve it but you might leave like slightly comments slightly better comments but you still have to pull down the review which takes the time so the Jenkins built environment will does it does that job for you we will do this and when you have a notification then from Jenkins Haiti builds the task tests up past you can then pull down the source code run it and verify that all the functionality work which saves you the step of pulling it down it breaks building and then you have to know if I hate broken so now when you wait - Jenkins notifies you you your workflow is easier so and then swarm review like it then you review the swarm review with like hey maybe you want to change this in person this also this is great for for you knowing exactly if a test fails what to review like where to review what it's the same for if build fails you can then easier verify what's wrong let's talk about it notification examples so what is my feedback I receive so if a notification received I receive a notification for that as a review being created you receive something like this in this Court you receive like a link to their to the build which is currently building while you get this review a review link a description of the review and underneath again short information about like what's the purpose review what's my possible build review and then you can click on new review as well which links you to the review if a review pasts the pipeline you get a notification with the build link maybe you want to still check it out um the review link because you want to prove it or review it anyways and the description and underneath the same thing like you get access to the perverse revision which is the current purpose revision which is on perforce like the latest and the purpose review ID if something fails you get a few more information which is you get the link to the build the link to the non past log and the past log later about this what this means and a revealing which allows you to review the review and the description let's talk about Jenkins so this is a brief overview of Jenkins so when we open Jenkin we have the project overview and the project overview looks similar to this and what's highlighted here with the red box around it or the project overviews we have in this case this is a folder and underneath this we would have our extra projects so our actual projects would be in this line and we can just click on it by the highlighted box where we click on the link here 2019 year 3 so this would give us then this overview and in there we can just click on a project which in this case is management review development built so when we click on it we land to the Jenkins job aka project page job and project is being interchanging lately used in Jenkins this is just due to its history so yeah let's we just wrought with it so this is a job page or a project page and what we're going to have here is the first it's the stage overview so if we move back quickly so this is how it looks in general and then the stage view is basically this is the stage view and the stage view is giving you a brief overview of all the stages in this project this is only when we have a pipeline project not when we have a workflows project and I'm not going into depth about a workflows project because the workflow project would have no stage overview but the rest from now on would be the same but let's talk about the stage view first so the stage view gives you a overview of all the stages what takes how long and you can see where it failed so when you see where it fits you might want to know what failed so you hover over with your mouse where you want like what you want to be like for example in packaging and something went wrong there so you click on it and then you see this little pop-up coming up you can click on locks and then you see the overview with all the steps um what happens we're and then you can unfold it and you see exactly the log there which is very useful if you want to analyze okay so this is broken you don't want to scroll through all the millions lines as long as you have so let's talk about the build view let's find a build first of all so when we are back in our stage viewing or general project overview we have on the left side the build history and we can see all our builds rep means the build fails blue means the build passes and gray means the build was ordered and this is like this little bubble in the beginning which indicates the stages of a builds we can just select one like the number one here and we can click on it we also see when it was built in what time so yeah when we click on it we did land into this so called two Jenkins build page and a build page looks similar to this and what's interesting here is the change overview like you see here which gives you the overview of all the changes which is very interesting when you have to source control pack is source control working at the same time like in this example we have get and purpose running and underneath we see if the plugin paused log is installed we see the overview of all the errors and warnings we have so we have five errors and we have hundred and six warnings on the left side is the navigation which is interesting where we can navigate for the project or in this case to the builds we put in we click on parameters and we have a parameter rised builds which means we can we can give it some information we find them here and we can see them which parameter is this particular build number six had on console output we can see the entire console output non pass just plain old text if we click on console output passed which gives you a nice overview and replay in a pipeline project allows you to replay an entire build again with the same parameter it received this allows you for example if something in your pipeline script went wrong to change this or if just some little minor things went wrong which have to do with Jenkins itself you can change it there so let's have a look about the build log so we have two different build logs in our project so we have first the console output which basically looks like this and you see the output here which is just plain text with some color but not really interesting and the best way to navigate through this is control f and then you look for error or something like this and you want to click maybe on view as plain text which gives you the entirety of the output nice not nicely but easier to scroll through then we have the Jenkins past log which only is available if the plug-in is installed which it is in this case so we have a nice overview nicer overview here and we have a nice overview of all the errors or warnings or information we have here we click on that and I expanse and then we see a list of what particular went wrong we can click on it and then we automatically scroll the right side to the right lines they are red highlighted and this gives you a really nice and easier way to navigate through the log and to see what's wrong thank you very much for this