gitlab

问题 I have a monorepo in GitLab with a Feature Branch approach. What I'm trying to achieve is to launch the part of the pipeline associated to the directory containing the altered files. So my .gitlab-ci.yml looks like : job1: stage: build script: - ... only: changes: - myparentdir/dir1/* job2: stage: build script: - ... only: changes: - myparentdir/dir2/* Create a new branch from develop Commit myparentdir/dir2/test.txt on this branch The pipeline launch every build jobs ! It seems like GitLab

问题 I'm trying to install NPM dependencies from a private GitLab instence. So, I have my repo with basic files And I added this dependencie in the package.json on my project "node-demo-package": "https://oauth2:<ACCESS TOKEN>@gitlab.fullurl.git" But, when I run npm install , I receive this error message: npm ERR! code ENOPACKAGEJSON npm ERR! package.json Non-registry package missing package.json: node-demo-package@https://oauth2:<ACCESS TOKEN>@gitlab.fullurl.git. npm ERR! package.json npm can't

问题 So after googling a little bit (which is polluted by people having trouble with Pull Secrets) I am posting this here — and to GCP Support (will update as I hear). I created a Cluster from GitLab Kubernetes integration (docs: https://about.gitlab.com/solutions/kubernetes) within the same project as my GCR registry / images. When I add a new service / deployment to this Cluster using Kubectl (which relies on a private image within the GCR Registry in this project) the pods in the GitLab created

问题 I am a Newbie using gitlab-CI and my english is not very good. I want to use gitlab ci to deploy one project to i686, x86_64 linux machine respectively. So I can generate an update package on different types linux centos. Now I use gitlab-server(192.168.1.240), gitlab runner (192.168.1.184) production server1(192.168.1.162) production server2(192.168.1.163); gitlab-server(240) --> runner(184) ^ ^ product_s1(162) product_s2(163) /etc/gitlab-runner/config.toml: concurrent = 1 [[runners]] url =

问题 I have installed the latest Gitlab-CE (8.10) on CentOS 7 (fresh install) via the Omnibus package as described here: https://about.gitlab.com/downloads/#centos7 Now, I would like to change the default port at which one can access the Gitlab web interface. To this end, I followed the instructions at http://docs.gitlab.com/omnibus/settings/nginx.html#change-the-default-port-and-the-ssl-certificate-locations, namely I included external_url "http://127.0.0.1:8765" in the configuration file /etc

问题 I just recently install GitLab v5.0 on an Ubuntu 12.04 server and am now having issues with email notifications. I can't get GitLab to send any emails of any kind. I've got my config/environments/production.rb file setup to use sendmail as the transport service: config.action_mailer.delivery_method = :sendmail config.action_mailer.perform_deliveries = true config.action_mailer.raise_delivery_errors = true And I can manually use sendmail successfully from the shell as described here: http:/

问题 I'm trying to include SSL on my gitlab pages site, and it says I need to first install the Pages daemon. However, I'm not sure where to start: is cd /home/git a home directory on my Mac where I'm supposed to have git installed? When I do git --version it says git version 2.7.4 (Apple Git-66) however I'm not seeing a folder "git" inside my home directory. Any ideas on how I'd get into the /home/git folder? 回答1: \o/ Great! I got this certificate from StartSSL Class 1, check this tutorial to

问题 I followed the GitLab Docs to enable my project's CI to clone other private dependencies. Once it was working, I extracted from .gitlab-ci.yml : before_script: - 'which ssh-agent || ( apt-get update -y && apt-get install openssh-client -y )' - eval $(ssh-agent -s) - ssh-add <(echo "$SSH_PRIVATE_KEY") - mkdir -p ~/.ssh - '[[ -f /.dockerenv ]] && echo -e "Host *\n\tStrictHostKeyChecking no\n\n" > ~/.ssh/config' into a separate shell script setup.sh as follows: which ssh-agent || ( apt-get

问题 I am using GitLab with SonarQube executed by Jenkins. I want prevent merge requests from being accepted if SonarQube has reported any issues. Any ideas for Gitlab CE or EE? 回答1: Gitlab CI offers two ways to prevent merge requests, if build fails or if there is unresolved discussion. To start please configure a Jenkins plugin following this tutorial. Now that you have the gitlab-jenkins-ci integration and gitlab trigerrs the jenkins build you have to enable Only allow merge requests to be

问题 After a recent minor 8.x upgrade, I'm unable to execute GitLab CI tests that also fetch another repository. While everything worked previously, now I get the famous Host key verification failed. error message from ssh. What could be the cause of this? /etc/gitlab-runner/config.toml : concurrent = 1 [[runners]] name = "python-runner@localhost" # ... executor = "docker" [runners.docker] image = "edoburu/python-runner" privileged = false cap_drop = ["DAC_OVERRIDE"] volumes = [ "/cache", "/home