Thanks for the video, once I realized running make init created the Makefile I was in business! Now if I can only figure out a way to notify developers when certain watched files are changed.
I guess the only: keyword is associated under-the-hood to the branch name? As apposed to writing an if statement to accomplish what you did at around 5:30-6:00
I'm not sure - but I believe only: is no longer being updated/supported and the entire mechanism has been replaced by the newer rules: clause, check out the documentation for details.
It's really nice video and good explanation provided. Incase there are multiple branches like, develop, release and hotfix along with master branches. As you may understand that, typically develop branch will be used for development, release branch is for any releases, hotfix branch is for emergency fixes and master branch is for production. How does the yml file update with only option to choose for the respective branches are selected when CICD job triggers. How to pass the artifacts from one stage to other stage where these stages get involve with different branches. Could you please provide your inputs as I am a newbie for GitLab. Thanks & appreciate your support.
Great video! Is there a way that I can specifically trigger a particular gitlab runner by committing my changes into branch? In that way I could have one runner for dev branch and one for test branch.. any comments on that?
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"
thanks for the variables note on commit msg.. life saver
Definitely checking out your other videos too!
Thanks for the video, once I realized running make init created the Makefile I was in business! Now if I can only figure out a way to notify developers when certain watched files are changed.
I guess the only: keyword is associated under-the-hood to the branch name? As apposed to writing an if statement to accomplish what you did at around 5:30-6:00
I'm not sure - but I believe only: is no longer being updated/supported and the entire mechanism has been replaced by the newer rules: clause, check out the documentation for details.
which only variable we must use when the commit is made to one branch and that branch tag has to be created and pushed to ECR?
hello im facing a problem . after completetion of my job. gitlab triger automatically these job again?
It's really nice video and good explanation provided. Incase there are multiple branches like, develop, release and hotfix along with master branches. As you may understand that, typically develop branch will be used for development, release branch is for any releases, hotfix branch is for emergency fixes and master branch is for production. How does the yml file update with only option to choose for the respective branches are selected when CICD job triggers.
How to pass the artifacts from one stage to other stage where these stages get involve with different branches. Could you please provide your inputs as I am a newbie for GitLab. Thanks & appreciate your support.
See 'only:' and 'needs:' job options in the gitlab ci documentation.
Great video! Is there a way that I can specifically trigger a particular gitlab runner by committing my changes into branch? In that way I could have one runner for dev branch and one for test branch.. any comments on that?
How many file include can be done in a trigger
with only: is it if all condition passes or any one of them passes?
I believe it's if at least one of the 'only' conditions passes. Check out the documentation: docs.gitlab.com/ee/ci/yaml/#onlyexcept-basic
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"
teaching or showing your skill