gitlab-ci

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

问题 We have to customize hosts file in our dynamically generated Elastic Beanstalk instance of our Spring Boot application during our GitLab CI/CD pipeline. To do this, we need to provide a .ebextensions directory with a config file that looks like this: commands: 01_add_hosts: command: echo 123.12.12.123 myhost.com >> /etc/hosts Since we have a spring boot application, we have to package .ebextensions at the root level of our fat jar. So, basically we unzip the jar, add the ebextensions

问题 I am trying to run gitlab ci which contains custom php image. The before_script invokes docker_install.sh In docker_install.sh I executed whoami it gives "docker". I tried to list down groups it gives "docker sudo". When I try to execute further instructions in docker_install.sh file, like cp ci/php.ini /etc/php/7.4/cli/php.ini It does not execute and gives error cp: cannot create regular file '/etc/php/7.4/cli/php.ini': Permission denied If I do sudo cp ci/php.ini /etc/php/7.4/cli/php.ini it

问题 I have a Jenkins pipeline project and I would like to trigger a build every time a push to the Gitlab repository where the code is hosted is performed. On Jenkins I have installed the Gitlab plugin and the Git plugin and I have configured the Gitlab section (Manage Jenkins -> Configure System) by adding the Gitlab host URL (https://gitlab.com) and the Gitlab API token previously generated on Gitlab: if I perform a test connection, everything is OK, as expected. The problem is on Gitlab: I go

问题 I have a project in gitlab. The project gets built for every check-in in the repo and build artifacts are created when the gitlab pipeline is successful. I want to get these build artifacts in my jenkins pipeline job. Is there any way to do that? I couldn't find any plugin in Jenkins to do this. Any help is appreciated. 回答1: The GitLab API offers this with both complete artifacts package (zip) and single files. You need a GitLab token which you can add as a Credential (secret text) and the

问题 I have a project in gitlab. The project gets built for every check-in in the repo and build artifacts are created when the gitlab pipeline is successful. I want to get these build artifacts in my jenkins pipeline job. Is there any way to do that? I couldn't find any plugin in Jenkins to do this. Any help is appreciated. 回答1: The GitLab API offers this with both complete artifacts package (zip) and single files. You need a GitLab token which you can add as a Credential (secret text) and the

问题 I have a project in gitlab. The project gets built for every check-in in the repo and build artifacts are created when the gitlab pipeline is successful. I want to get these build artifacts in my jenkins pipeline job. Is there any way to do that? I couldn't find any plugin in Jenkins to do this. Any help is appreciated. 回答1: The GitLab API offers this with both complete artifacts package (zip) and single files. You need a GitLab token which you can add as a Credential (secret text) and the

问题 I have a project in gitlab. The project gets built for every check-in in the repo and build artifacts are created when the gitlab pipeline is successful. I want to get these build artifacts in my jenkins pipeline job. Is there any way to do that? I couldn't find any plugin in Jenkins to do this. Any help is appreciated. 回答1: The GitLab API offers this with both complete artifacts package (zip) and single files. You need a GitLab token which you can add as a Credential (secret text) and the

问题 stages: - build - docker-push - deploy cache: paths: - node_modules/ build: stage: build image: node:latest script: - yarn install - npm run build artifacts: paths: - dist/ docker: stage: docker-push image: docker:18.09.7 services: - docker:18.09.7-dind script: - docker login --username=$DOCKER_USERNAME --password=$DOCKER_PASSWORD - docker tag $DOCKER_REPOSITORY:$CI_RUNNER_ID $DOCKER_REPOSITORY:latest - docker push $DOCKER_REPOSITORY test: stage: deploy image: google/cloud-sdk:latest script:

问题 stages: - build - docker-push - deploy cache: paths: - node_modules/ build: stage: build image: node:latest script: - yarn install - npm run build artifacts: paths: - dist/ docker: stage: docker-push image: docker:18.09.7 services: - docker:18.09.7-dind script: - docker login --username=$DOCKER_USERNAME --password=$DOCKER_PASSWORD - docker tag $DOCKER_REPOSITORY:$CI_RUNNER_ID $DOCKER_REPOSITORY:latest - docker push $DOCKER_REPOSITORY test: stage: deploy image: google/cloud-sdk:latest script: