I had two pipelines optionally running on the master branch: prepare_release:stage:prepare_releaserules:-if:$CI_PIPELINE_SOURCE=="schedule"when:never-if:$CI_COMMIT_TAGwhen:never-if:$CI_COMMIT_BRANCH==$CI_DEFAULT_BRANCHwhen:manualscript:-...create_release:image:registry.gitlab.com/gitlab-org...
In my gitlab CI I always get this hint messages. Yes, I see I have to setgit config --global init.defaultBranch main, but everything I'm adding in my stages / jobs of the CI gitlab config is executedafterfetching. test:stage:testimage:name:registry.domain.com/project/...
Jenkins, GitHub and GitLab use the Pull Request branch workflows. Imaging you added a required input to your tests and the Pull Request runs the default branch workflow, it will fail. You will have to merge your changes without testing them. You are right: Disagree. Everyone can do ...
I had two pipelines optionally running on the master branch: prepare_release:stage:prepare_releaserules:-if:$CI_PIPELINE_SOURCE=="schedule"when:never-if:$CI_COMMIT_TAGwhen:never-if:$CI_COMMIT_BRANCH==$CI_DEFAULT_BRANCHwhen:manualscript:-...create_release:image:registry.gitlab.com/gitlab-org...