gitlab

Error uploading artifacts to coordinator

由 穿精又带淫゛_ 提交于 2021-02-20 03:56:49
问题 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

Best pracitces for multi-developer Git for single user application

由 不问归期 提交于 2021-02-20 02:17:12
问题 I am responsible for a quite old application that we are trying to wrap modern tools around. The application is a Linux based data processing application. It takes some data in, does some complex analysis/simulation, and has a simple web/CSV interface. We run multiple instances of this, one for each client of ours, where the core the same, and we write some helper/wrapper scripts that we store in Git. Also as many config files as we could add are in Git. The core application is required to be

“Unable to locate package git” when running GitLab CI/CD pipeline

由 微笑、不失礼 提交于 2021-02-19 05:26:15
问题 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

“Unable to locate package git” when running GitLab CI/CD pipeline

由 心不动则不痛 提交于 2021-02-19 05:25:32
问题 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

GitLab CI/CD: Run jobs only when files in a specific directory have changed

由 点点圈 提交于 2021-02-18 22:09:45
问题 I would like to run specific jobs on the .gitlab-ci.yaml if and only if files within specific directories of the repository have changed. Is there a way to do this with gilab's ci/cd tooling or would it be easier just to run a custom build script? 回答1: Changes policy introduced in GitLab 11.4. For example: docker build: script: docker build -t my-image:$CI_COMMIT_REF_SLUG . only: changes: - Dockerfile - docker/scripts/* - dockerfiles/**/* - more_scripts/*.{rb,py,sh} In the scenario above, if

GitLab CI/CD: Run jobs only when files in a specific directory have changed

由 浪尽此生 提交于 2021-02-18 22:09:14
问题 I would like to run specific jobs on the .gitlab-ci.yaml if and only if files within specific directories of the repository have changed. Is there a way to do this with gilab's ci/cd tooling or would it be easier just to run a custom build script? 回答1: Changes policy introduced in GitLab 11.4. For example: docker build: script: docker build -t my-image:$CI_COMMIT_REF_SLUG . only: changes: - Dockerfile - docker/scripts/* - dockerfiles/**/* - more_scripts/*.{rb,py,sh} In the scenario above, if

GitLab CI/CD: Run jobs only when files in a specific directory have changed

由 怎甘沉沦 提交于 2021-02-18 22:08:39
问题 I would like to run specific jobs on the .gitlab-ci.yaml if and only if files within specific directories of the repository have changed. Is there a way to do this with gilab's ci/cd tooling or would it be easier just to run a custom build script? 回答1: Changes policy introduced in GitLab 11.4. For example: docker build: script: docker build -t my-image:$CI_COMMIT_REF_SLUG . only: changes: - Dockerfile - docker/scripts/* - dockerfiles/**/* - more_scripts/*.{rb,py,sh} In the scenario above, if

Disallow CI pipelines of one GitLab project to run concurrently?

由 走远了吗. 提交于 2021-02-18 18:49:10
问题 On an internal GitLab server there is one project with a CI script not tolerating concurrent execution of multiple pipelines (external side effects in Kubernetes). So if two commits are pushed in succession with less time in between than the first pipeline needs to finish, the two pipelines will run concurrently, which causes both to fail. Globally setting concurrent = 1 for the CI runner (one K8s runner used across multiple repos) is not practicable in that case, because pipelines of other

Disallow CI pipelines of one GitLab project to run concurrently?

由 感情迁移 提交于 2021-02-18 18:47:03
问题 On an internal GitLab server there is one project with a CI script not tolerating concurrent execution of multiple pipelines (external side effects in Kubernetes). So if two commits are pushed in succession with less time in between than the first pipeline needs to finish, the two pipelines will run concurrently, which causes both to fail. Globally setting concurrent = 1 for the CI runner (one K8s runner used across multiple repos) is not practicable in that case, because pipelines of other

为什么黑客从不用鼠标，一直在敲键盘？看完长见识了

由 落花浮王杯 提交于 2021-02-18 15:21:17
点击下方“ 民工哥技术之路 ”，选择“设为星标” 回复“ 1024 ”获取独家整理的学习资料！ 在各种好莱坞大片里头，但凡需要“技术小子”表现一下如何用几分钟时间黑掉一个庞大IT系统的时候，里面的电脑都是这样的： 文字处理软件从来不显示光标。 所有的屏幕都显示1英尺高的字符。 高技术的计算机都有简单易用的图形界面。 即便是没有图形界面，计算机也能正确理解自然语言并执行。 只需要敲入“读出秘密文件”（“Access The Secret Files”），计算机就会给出任何你想要的信息。 仅仅通过敲入“上载病毒”（“Upload Virus”），就能够攻击一台计算机。 黑客总是能够在仅仅猜测密码一两次的情况下，就进入保密的计算机。 磁盘可以用在任何有软盘驱动器的计算机上，并且所有的软件可以工作在任何平台上。 笔记本计算机总有实时电视电话能力，它们的性能就是比超级CRAY计算机也不差。 有一个细节是，很多时候里面出现特别专业的操作电脑的画面时，基本没有鼠标的影子！还记得《黑客帝国》里接线员坦克操作的电脑么？不仅是图形界面，而且是键盘操作——根本没有放鼠标或者轨迹球的地方——再就是显示器屏幕旁的几个旋钮扳来扳去。 当然电影就是电影，不过黑客鼠标用得少也是事实，据某黑客的专业解读： 1、懒得搞图形界面。 看起来简单的图形界面实现起来工作量非常大
订阅 gitlab