GitLab CI - Control your pipeline jobs

In this video I will give an introduction into how you can control your pipeline jobs in a GitLab CI pipeline. I will, at a high level show you how to apply the "needs" and "rules" keywords and how you can apply them.
A list of GitLab predefined variables can be found here:
docs.gitlab.co...
Further details regarding GitLab keywords, including "needs" and "rules" can be found here:
docs.gitlab.co...

[@forexmeter3900]

Very well explained, maybe do another video and delve a little deeper into the predefined variables to control the pipeline. Thank you!

[@alhamdubello]

Brilliant consice explanation on CICD rules

[@abhimanyumithun832]

thank you for making this beautiful video..

[@user-gs6sk5vl4q]

Great video! Thank you!

[@jhosnatas]

Thank you bro ! amazing class

[@alwaha4283]

That’s very good 👍

[@LalajiRocks]

When making changes in deployment stages, ci jobs getting started each time, how to control such case. How to mange pipeline so that making changes in cd part only trigger cd stage jobs only ?

[@hakimbencella4242]

Thanks a lot

[@premierde]

how should a rule be enforced that a job only run on branch & not on main.

[@tobisdevelopercorner1190]

Hello premierde, Since the "only" keyword has been deprecated, you can enforce (or limit) what job is being run on what branch in the rules. You can evaluate the "CI_COMMIT_BRANCH" variable accordingly. Here is a link to the GitLab pre-defined variables: docs.gitlab.com/ee/ci/variables/predefined_variables.html Hope this helps. Happy coding!

[@tzgardner]

How do you get a stage to not run if the previous stage had a job fail?

[@pravallikachevuru4767]

hi can u please explain how we auto increment build number(apk in my case) in firebase from gitlab

[@tobisdevelopercorner1190]

Hello pravallikachevuru4767, I admit that I am not that familiar with Firebase. However, in order to do something from a GitLab pipeline on a remote system (in this case Firebase), you would need to write the appropriate job and template to connect to Firebase and perform the action you would like. Please also keep in mind that the shared runners offered by GitLab may not lend themselves to perform the task you would like to, which would require a private runner to be available/setup. In order to provide better help, one would need to have more details about your setup and certainly more familiarity with Firebase than I have :). I would think other community members here on KZbin or forums can provide better guidance. Maybe this helps: stackoverflow.com/questions/39065786/auto-increment-a-value-in-firebase-with-javascript www.freecodecamp.org/news/how-to-get-started-with-firebase-using-python/ Happy coding!

[@vinodghate5716]

Friends , can anyone answer to implement this feature which tier of subscription is better? i have not opted any subscription yet, but thinking to opt one. . This will be very helpful if you can answer.

[@raghupathym25]

How to trigger gitlab pipeline when commit to other branches except develop and master, also while merge to master branch? The below code is not working rules: - if: $CI_COMMIT_BRANCH != “master” - if: $CI_COMMIT_BRANCH != “develop” - if: $CI_MERGE_REQUEST_TARGET_BRANCH_NAME == “master

[@jamallmahmoudi9481]

Hi, cool & perfect . 🙏🙏🙏

[@debajyotisarkar3960]

Hi Tobias, that's a really great video to learn the CICD pipeline. Could you please share with me the GitLab URL for my self-learning?

[@tobisdevelopercorner1190]

Hello Debajyoti, To create your own GitLab account, you can visit gitlab.com. Just click the "Login / Register" link in hte upper right hand corner and follow the instructions. Happy coding!

[@pqKa16]

This is very helpful! :) BTW, I tried implementing a parallel run with 3 jobs and 3 runners but my 2 jobs used the same runner. I already set my limit and request_concurrency to 1 in config. Do you have any suggestion or video for that? :)

[@balan7442]

Thanks Tobias, it was nice video and explained well on CICD jobs execution at different stages with rules. I have one question, where there is a new feature branch creation from dev branch, CI job triggering automatically even just creates a branch without any code commit. So i need to stop this auto trigger CI job only when the branch creates Here is my sample snippet of yml file, could you pls check and guide me how to resolve auto trigger of CI job as i couldn't found in the web and gitlab issue tracker (May be i didn't get). Appreciate your support and Thanks in advance --- Stage --- Build: stage: build only: - /^feature-.*$/ - develop - /^hotfix-.*$/ allow_failure: false environment: name: dev script: - echo "build stage execution"

[@tobisdevelopercorner1190]

Hello Bala N, That is actually a very good question. As you may have seen searching on Google, there have been a few folks asking for this but no definitive answer has been given. One way of controlling the job execution is to not run the job on a push event. When you create a new branch, the pipeline is being triggered by a push event. It is important to note though the if you exclude the push event, this means that the pipeline will not run automatically upon committing code either. If it is not a problem to run the pipeline manually by clicking the "Run Pipeline" button, than the following rule may help you: Build: stage: build allow_failure: false environment: name: dev script: - echo "build stage execution" - echo "$CI_PIPELINE_SOURCE" rules: - if: $CI_PIPELINE_SOURCE == "push" when: never - if: $CI_COMMIT_BRANCH =~ /^feature-.*$/ || $CI_COMMIT_BRANCH == "develop" || $CI_COMMIT_BRANCH =~ /^hotfix-.*$/ when: always NOTE: You cannot use "rules" and "only" together, so you will have to add the branch names to the rules. There may be other variables you want to filter on. To see what is available in the pipeline, you can check the predefined variables here: docs.gitlab.com/ee/ci/variables/predefined_variables.html Happy coding!