gitlab

问题 I would like to setup the AutoDevops functionality of Gitlab CI/CD, and for that I am trying to setup the existing kubernetes cluster as my environment. However, the Gitlab requires Kubernetes Master API URL that uses to access the Kubernetes API. Kubernetes exposes several APIs, we want the "base" URL that is common to all of them, e.g., https://kubernetes.example.com rather than https://kubernetes.example.com/api/v1. we will get the API URL by running this command: kubectl cluster-info |

问题 I would like to setup the AutoDevops functionality of Gitlab CI/CD, and for that I am trying to setup the existing kubernetes cluster as my environment. However, the Gitlab requires Kubernetes Master API URL that uses to access the Kubernetes API. Kubernetes exposes several APIs, we want the "base" URL that is common to all of them, e.g., https://kubernetes.example.com rather than https://kubernetes.example.com/api/v1. we will get the API URL by running this command: kubectl cluster-info |

问题 How do I prevent a gitlab ci pipeline being triggered when I add a git tag? I'm running this command locally (as opposed to within a gitlab-ci job) git tag -a "xyz" and then pushing the tag; and this triggers various pipelines. I want to exclude some of those pipelines from running. I'm trying variations on ideas from questions such as this; that question is using only , I'm wanting to exclude, so I'm trying except. The answers there have two variants, one with refs one without. build: # ...

问题 How do I prevent a gitlab ci pipeline being triggered when I add a git tag? I'm running this command locally (as opposed to within a gitlab-ci job) git tag -a "xyz" and then pushing the tag; and this triggers various pipelines. I want to exclude some of those pipelines from running. I'm trying variations on ideas from questions such as this; that question is using only , I'm wanting to exclude, so I'm trying except. The answers there have two variants, one with refs one without. build: # ...

问题 How do I prevent a gitlab ci pipeline being triggered when I add a git tag? I'm running this command locally (as opposed to within a gitlab-ci job) git tag -a "xyz" and then pushing the tag; and this triggers various pipelines. I want to exclude some of those pipelines from running. I'm trying variations on ideas from questions such as this; that question is using only , I'm wanting to exclude, so I'm trying except. The answers there have two variants, one with refs one without. build: # ...

问题 How do I prevent a gitlab ci pipeline being triggered when I add a git tag? I'm running this command locally (as opposed to within a gitlab-ci job) git tag -a "xyz" and then pushing the tag; and this triggers various pipelines. I want to exclude some of those pipelines from running. I'm trying variations on ideas from questions such as this; that question is using only , I'm wanting to exclude, so I'm trying except. The answers there have two variants, one with refs one without. build: # ...

问题 How do I prevent a gitlab ci pipeline being triggered when I add a git tag? I'm running this command locally (as opposed to within a gitlab-ci job) git tag -a "xyz" and then pushing the tag; and this triggers various pipelines. I want to exclude some of those pipelines from running. I'm trying variations on ideas from questions such as this; that question is using only , I'm wanting to exclude, so I'm trying except. The answers there have two variants, one with refs one without. build: # ...

问题 I have a C++ project that is compiled and packaged for multiple OS (Linux, Windows, MacOS) as well as multiple CPU architectures (i386, x86_64, arm, Aarch64) For this I'm using Jenkins to grab the source code and run the build script in parallel on each system. It's a simple working solution, since my build script deals with the system differences. Now I'm looking into Gitlab CI/CD, and it has many things I find appealing ( being able to keep the build script as part of the repository, very

问题 We're currently evaluating the use of GitLab for our project and one thing we find slightly off is the comments when reviewing a merge request. The problems starts when some comments were entered as part of the code review and a new commit was pushed to address these comments. Both the comments made on the commits and those made on "Changes" panel are shown on the "Discussion" tab, but there's no indication that some changes around the same lines were made. Going to "Changes" panel and

问题 Im currently working on e2e test in Chrome Puppeteer. I am at the stage where it would be ideal to integrate my tests in the development process. What I want to accomplish is the following: my tests run automated before every deploy to production. If they succeed deployment goes through, if they fail deployment is canceled. I use a pipeline on gitlab to automate my deployment process. So my main question is how can I integrate my puppeteer tests into the gitlab-ci.yml file? 回答1: This might be