gitlab-ci

问题 I’ve been having some fun setting up GitLab and after spending quite a while hacking away at it, I’ve become relatively used to setting it up, now having done that on two machines, the second time around with much more ease than originally… However, I am faced with a rather large problem, on both machines: My CI pipeline is broken. Somehow, somewhere, my setup is providing a 403 to artifacts once builds are completed, meaning that each and every job that ever technically succeeds will only be

问题 I am trying to set up a GitLab CI/CD pipeline with this following .gitlab-ci.yml file: stages: - test image: "ros:foxy-ros-base-focal" before_script: - apt-get -y update && apt-get install -y \ git wget qt5-default \ python3-osrf-pycommon \ python3-catkin-tools \ python3-rosdep \ python3-vcstool \ python3-pip \ python3-colcon-common-extensions \ apt-utils - rm -rf /var/lib/apt/lists/* - /bin/bash -c "source /opt/ros/${ROS_DISTRO}/setup.bash; colcon build" - echo "source /root/dev_ws/install

问题 I am trying to set up a GitLab CI/CD pipeline with this following .gitlab-ci.yml file: stages: - test image: "ros:foxy-ros-base-focal" before_script: - apt-get -y update && apt-get install -y \ git wget qt5-default \ python3-osrf-pycommon \ python3-catkin-tools \ python3-rosdep \ python3-vcstool \ python3-pip \ python3-colcon-common-extensions \ apt-utils - rm -rf /var/lib/apt/lists/* - /bin/bash -c "source /opt/ros/${ROS_DISTRO}/setup.bash; colcon build" - echo "source /root/dev_ws/install

问题 Our Gitlab pipeline generates some performance graphs, which I would like to be sent to every team member via e-mail. So far, they are marked as artifacts so Gitlab keeps them. Is there any way within Gitlab to achive this? Or should I do that within the job script? 回答1: There is no way currently to send artifacts via email from the gitlab interface. You will indeed have to send them from your job scripts. Gitlab can send an email after a pipeline is finished (see in Settings>Integrations

问题 How can I use git tags with the format major . minor . patch , without the " v " in the beginning (i.e. versions 1.0.1, 2.0.1)? I'm using Gitlab CI, but even using the Docker image locally I'm not able to pass the value to tag-format correctly. What I'm trying to do: npx --no-install semantic-release --tag-format "\${version}" The error log: [8:42:06 PM] [semantic-release] › ✖ ETAGNOVERSION Invalid tagFormat option. The tagFormat (https://github.com/semantic-release/semantic-release/blob

问题 In Gitlab, how can i programatically download the artefacts issued at end of a CI pipeline. It is easy to download it via the UI but how can I get it through API. In other words, is it possible to access it via a token or similar? 回答1: It is possible through the API as in https://docs.gitlab.com/ee/api/jobs.html#get-job-artifacts GET /projects/:id/jobs/:job_id/artifacts Example requests: Using the PRIVATE-TOKEN header: curl --location --header "PRIVATE-TOKEN: 9koXpg98eAheJpvBs5tK" "https:/

问题 In Gitlab, how can i programatically download the artefacts issued at end of a CI pipeline. It is easy to download it via the UI but how can I get it through API. In other words, is it possible to access it via a token or similar? 回答1: It is possible through the API as in https://docs.gitlab.com/ee/api/jobs.html#get-job-artifacts GET /projects/:id/jobs/:job_id/artifacts Example requests: Using the PRIVATE-TOKEN header: curl --location --header "PRIVATE-TOKEN: 9koXpg98eAheJpvBs5tK" "https:/

问题 I have autoscaled the gitlab-runner on AWS spot instances. And it works fine. And I have an issue when running the jobs. Below is my .gitlab-ci.yml and it has two stages. stages: - build - dev1:build build: stage: build script: - docker build --rm -t broker-connect-dev1-${CI_COMMIT_SHORT_SHA} -f BrokerConnect/Dockerfile . only: - dev1/release tags: - itela-spot-runner build-dev1: stage: dev1:build script: - docker tag broker-connect-dev1-${CI_COMMIT_SHORT_SHA}:latest 19950818/broker-connect:$

问题 I've read Can anyone explain docker.sock to understand what /var/run/docker.sock does, but its use in GitLab CI's Use Docker socket binding has me confused. Here is their example command for the gitlab-runner registration: sudo gitlab-runner register -n \ --url https://gitlab.com/ \ --registration-token REGISTRATION_TOKEN \ --executor docker \ --description "My Docker Runner" \ --docker-image "docker:19.03.12" \ --docker-volumes /var/run/docker.sock:/var/run/docker.sock I see two places that

问题 I am trying to build my project on GitLab CI but unfortunately for me I keep getting this error inside the runner: Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain Now I know there is something wrong with my environment but I just cant get my mind wrapped around the problem. I searched on the web and I found I needed to update my .gitignore file and I did here it is: ### Java ### *.class ### Android ### *.apk *.ap_ ### Package files ### *.war *.ear *.aar ###