gitlab

问题 For instance, let's suppose I have a branch called develop , and all my features will be a branch created from develop that later I will need to do a merge request (in GitLab, what in GitHub would be a pull request). If I need to update my new branch before push it into origin and do a merge/pull request, does " git pull origin develop " would update my new branch too? If not, how can I do this? 回答1: The proper command would by: git fetch git switch myNewBranch git rebase origin/develop git

问题 I have a pipeline, where some tasks can only be processed by certain clients. For instance, some clients can only perform certain tests, where other clients are used to compile. Can I distribute my pipeline chain across different clients? For instance: /--- Testing (test-client-1)--\ Build (build-client-1)--+ +-- Package (build-client-1) \--- Testing (test-client-2)--/ 回答1: You can assign specific tasks to different runners, using tags: see runners/#using-tags and README.html#tags job: tags:

问题 GitLab 9.5.0 adds support for checking the gpg signature of commits and display the verification status next to the commit hash (release note). This version, however, does not verify commits signed using subkeys (gitlab issue, support is planned). Is it possible to export the subkeys in gpg and convert them into primary keys, such that these primary keys can be added to GitLab? 回答1: EDIT Oct 2017 Since version 10.1 GitLab has native support for subkeys. You can simply add the full public key.

问题 GitLab 9.5.0 adds support for checking the gpg signature of commits and display the verification status next to the commit hash (release note). This version, however, does not verify commits signed using subkeys (gitlab issue, support is planned). Is it possible to export the subkeys in gpg and convert them into primary keys, such that these primary keys can be added to GitLab? 回答1: EDIT Oct 2017 Since version 10.1 GitLab has native support for subkeys. You can simply add the full public key.

问题 I use gitlab runners in docker. It uses our own php image and mysql:5.7 image. It worked before, but now we can see this error when CI job is started: Running with gitlab-runner 10.4.0 (857480b6) on gitlab-runner-2 (00929f5e) Using Docker executor with image registry.blahblah.work/infra/docker-base/php ... Starting service mysql:5.7 ... Pulling docker image mysql:5.7 ... Using docker image mysql:5.7 ID=sha256:f008d8ff927dc527c5a57251b45cead7c9259c16a6a93c144f397eaafc103d36 for mysql service..

问题 I use gitlab runners in docker. It uses our own php image and mysql:5.7 image. It worked before, but now we can see this error when CI job is started: Running with gitlab-runner 10.4.0 (857480b6) on gitlab-runner-2 (00929f5e) Using Docker executor with image registry.blahblah.work/infra/docker-base/php ... Starting service mysql:5.7 ... Pulling docker image mysql:5.7 ... Using docker image mysql:5.7 ID=sha256:f008d8ff927dc527c5a57251b45cead7c9259c16a6a93c144f397eaafc103d36 for mysql service..

问题 I'm trying to install GitLab on a Debian 8.5.0. I folow the installation guide but the last step fail and I don't find any information in documentation. The gitlab-ctl reconfigure finish by Running handlers: Running handlers complete Chef Client failed. 3 resources updated in 02 seconds I have this error in the logs : Error executing action `run` on resource 'execute[/opt/gitlab/embedded/bin/initdb -D /var/opt/gitlab/postgresql/data -E UTF8]' The generated gitlab.rb is enterely commented

问题 Running the following: GitLab 8.15.0-rc1 GitLab Shell 4.0.3 GitLab Workhorse v1.1.1 GitLab API v3 Git 2.11.0 Ruby 2.3.3p222 Rails 4.2.7.1 PostgreSQL 9.2.18 I have created a project inside GitLab and pushed my code onto there without problems. I am the Project Owner and have the role 'Master' with the project. Branch 'master' is set as a 'protected branch' by default, allowing only group members with role 'Master' to merge and push to that branch. Now I made some small changes directly in

问题 I'm trying to build a go project in a docker container that relies on private submodules. I was hoping that --mount=type=ssh would pass my ssh credentials to the container and it'd work. Currently I can build locally with just make the GOPRIVATE variable set and the git config update. Here is my relevant Dockerfile currently # syntax = docker/dockerfile:experimental FROM golang:1.14.3-alpine AS build RUN apk add --no-cache git \ openssh-client \ ca-certificates WORKDIR /src ENV GIT_TERMINAL

问题 I'd like to incorporate GitLab CI into my Karate testing. I'd like to loop through my tests with different user names and passwords to ensure our API endpoints are responding correctly to different users. With that in mind, I'd like to be able to store the usernames and passwords as secure environment variables in GitLab (rather than in the karate-config as plain text) and have Karate pull them as needed from either the karate-config or the feature files. Looking through the docs and