Advanced pipelines using .gitlab-ci.yml

Поделиться
HTML-код
  • Опубликовано: 27 окт 2024

Комментарии • 23

  • @Sky-Walker6676
    @Sky-Walker6676 2 года назад +4

    Awesome video with beautiful Examples.
    Thank you.

  • @hakimbencella4242
    @hakimbencella4242 Год назад +1

    Awsome man! thanks a lot.

  • @AlDawoode
    @AlDawoode Год назад +1

    Awesome video. Thanks man.

  • @jamallmahmoudi9481
    @jamallmahmoudi9481 2 года назад +1

    Hi, very cool& Perfect
    Thanks a lot ......

  • @vighneshpp
    @vighneshpp 2 года назад

    Lovely video! Thanks for making this.

  • @coolpix807
    @coolpix807 5 месяцев назад

    Very useful!

  • @chongerwin
    @chongerwin 2 года назад

    Thank you very much!!

  • @AfmpJR
    @AfmpJR 5 месяцев назад

    What you've been doing, Tomek?

  • @PePTo-dx2yj
    @PePTo-dx2yj Год назад

    I have many local config files but runs only one, why?

  • @yokebabjr3866
    @yokebabjr3866 3 года назад +1

    Thank you very usefull! What is your advise for a library repo that trigger repos that consume that library. Now i recompile the library in each application to use the new version. Do you know a better way to do that?

  • @aloncarmelly282
    @aloncarmelly282 3 года назад +1

    thank you man !

    • @tomislater
      @tomislater  3 года назад

      I hope it was useful! :)

    • @aloncarmelly282
      @aloncarmelly282 3 года назад

      @@tomislater it is very much. One this i couldn't find.
      How to I run a test to one specific job?
      I want one line to extend from the build to the test while on another job in parallel have a different test

    • @tomislater
      @tomislater  3 года назад +2

      @@aloncarmelly282 Hmm, you can use rules keyword I think: ruclips.net/video/ddor-4Q2xto/видео.html
      You can pass env variable to the pipeline and add IF in rules section in jobs and decide if you want to spawn this job or not.

  • @raghupathym25
    @raghupathym25 2 года назад

    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"

    • @tomislater
      @tomislater  2 года назад +1

      I think you also have to provide `when` keyword?

    • @raghupathym25
      @raghupathym25 2 года назад

      @@tomislater in which line to add?

  • @nayanar2023
    @nayanar2023 3 года назад

    Great video bro

  • @deltax2673
    @deltax2673 3 года назад

    Hi @Tomik thanks for the video, I have case where 3 branch and he branch have own pipelines ( dev,qa, stg) am trying to build a docker image on qa pipeline then I push to registry. Now when I want to start qa pipeline I want to use available docker images from the registry
    is it possible to send pushed image information to next branch pipeline?
    FYI : docker images are tagged with commit sha and will get pushed to registry

    • @attilapinter7141
      @attilapinter7141 3 года назад +2

      Wouldn't artifacts or cache do that for you? (In case you didn't solve it yet ^_^)

  • @davidpccode
    @davidpccode 3 года назад

    Hi there...great video thanks!! One question..in a feature branch is it recommended to execute the complete pipeline with each push? I'm thinking tha5 could be heavy..thanks again

    • @tomislater
      @tomislater  3 года назад +1

      Hey, I would rather recommend to only build image/run tests. You can run some jobs only on master/develop branches for example.