gitlab-ci

问题 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

问题 Actually I have a need to get a timestamp of my commit in GitLab CI. Alredy have tested the official documentation of GitLab CI Variables here: https://docs.gitlab.com/ee/ci/variables But there are only commit variables for CI_COMMIT_SHA The commit revision for which project is built CI_COMMIT_TAG The commit tag name. Present only when building tags. Is there a way to achieve this? Need to add these values to variables. My prefered way would be to add it to the variables section. job:

问题 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

问题 According to the official gitlab documentation, one way to enable docker build within ci pipelines, is to make use of the dind service (in terms of gitlab-ci services). However, as it is always the case with ci jobs running on docker executors, the docker:latest image is also needed. Could someone explain: what is the difference between the docker:dind and the docker:latest images? (most importantly): why are both the service and the docker image needed (e.g. as indicated in this example,

问题 I am getting the artifacts (apks) on successful operation of pipeline in Gitlab . Is there any ways to send the artifacts (apks) on the Email address after successful operation in gitlab. Right now i need to do download artifacts manually. Is there any way to send the artifacts on Email after successfully build creation.Thanks 回答1: I think there is no way to send artifacts via email for Gitlab-CI. You can send the mail on success or failure or pipeline. Refer the same question here: Send

问题 I am getting the artifacts (apks) on successful operation of pipeline in Gitlab . Is there any ways to send the artifacts (apks) on the Email address after successful operation in gitlab. Right now i need to do download artifacts manually. Is there any way to send the artifacts on Email after successfully build creation.Thanks 回答1: I think there is no way to send artifacts via email for Gitlab-CI. You can send the mail on success or failure or pipeline. Refer the same question here: Send