gitlab-ci-runner

问题 I'm trying to set up gitlab CI on a windows 10 PC. I have created a docker container for gitlab (volumes are docker volumes) docker run --detach --name gitlab --hostname gitlab.mod --publish 4443:443 --publish 4480:80 --publish 8222:22 --volume gitlab-conf:/etc/gitlab --volume gitlab-logs:/var/log/gitlab --volume gitlab-data:/var/opt/gitlab gitlab/gitlab-ce Another for the runner docker run -d --name gitlab-runner -v gitlab-runner-conf:/etc/gitlab-runner gitlab/gitlab-runner:latest registered

问题 I have a problem in my gitlab-ci.yml on Windows. I launch phpunit with environments variables. So, I have a variable like: PHPUNIT : %SOURCE_PATH%\cgi-bin\php.exe %PHPUNIT_PATH% And some variables are declared before: SOURCE_PATH: 'C:\Source' PHPUNIT_PATH: '"%SOURCE_PATH%\cgi-bin\tests\__init\tools\phpunit.phar"' But when I use the CALL command, Windows doesn't resolve the variable inside the other variable. So if I do: CALL Echo %PHPUNIT% I have: C:\Source\cgi-bin\php.exe "%SOURCE_PATH%\cgi

问题 I have a problem in my gitlab-ci.yml on Windows. I launch phpunit with environments variables. So, I have a variable like: PHPUNIT : %SOURCE_PATH%\cgi-bin\php.exe %PHPUNIT_PATH% And some variables are declared before: SOURCE_PATH: 'C:\Source' PHPUNIT_PATH: '"%SOURCE_PATH%\cgi-bin\tests\__init\tools\phpunit.phar"' But when I use the CALL command, Windows doesn't resolve the variable inside the other variable. So if I do: CALL Echo %PHPUNIT% I have: C:\Source\cgi-bin\php.exe "%SOURCE_PATH%\cgi

问题 I have setup GitLab runner on winserver 2016. Everything works fine, except output of runner on gitlab. Locale of winserver is RU. I'm trying to build projects with MSBUILD, which outputs russian characters: Checking out e5ec41d1 as release-2... Skipping Git submodules setup $ echo "начинается билд %PROJECT_NAME%" "начинается билд PEPSolution" $ echo "Релизная сборка... " "Релизная сборка... " $ "C:\Program Files ^(x86^)\MSBuild\14.0\Bin\amd64\MSBuild.exe" /consoleloggerparameters:ErrorsOnly

问题 I've got an exampleproject at gitlab where I would like to get the ID of the last badge in the .gitlab-ci.yml via script. I get the overview of all badges as a json. Is there a way to get the "id" of the last element? At the moment I'm setting a custom CI variable PYLINT_BADGE_ID by hand from the json for each project. In this case it is 37777. How to automate this by commandline? Details: I'm trying to solve this question: Pylint badge in gitlab. But they use gitlab pages, anybadge,

问题 I'm testing gitlab-ci and trying to generate an image on the registry from the Dockerfile. I have the same code just to test: #gitlab-ci image: docker:latest tages: - build - deploy build_application: stage: build script: - docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY - docker build -t $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA . -f Dockerfile - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA-test output: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker

问题 I'd like to automatically deploy new work from my Gitlab repository to a live website running on a production server. The live website is a GIT repo clone of the live branch. My questions: each time a 'build' happens, the runner seems to clone my repo afresh, into ~/builds/... . Is this mandatory behaviour? All I think I really want is a git pull inside my production website directory. if it really has to clone the repo each time, why doesn't it git reset it? At least that would save a ton of

问题 I'd like to automatically deploy new work from my Gitlab repository to a live website running on a production server. The live website is a GIT repo clone of the live branch. My questions: each time a 'build' happens, the runner seems to clone my repo afresh, into ~/builds/... . Is this mandatory behaviour? All I think I really want is a git pull inside my production website directory. if it really has to clone the repo each time, why doesn't it git reset it? At least that would save a ton of

问题 I'm running gitlab 10.4.3 with gitlab-runner 10.4.0 as a kubernetes deployment with kubernetes runner and a minio-server for caching. I installed it according to the gitlab docs. Everything worked with the cache as expected, when adding the appropriate settings to the .gitlab-ci.yml -file: build: stage: build variables: GIT_STRATEGY: fetch cache: key: "$CI_BUILD_REF_NAME" paths: - node_modules/ script: - compile-templates.sh - yarn install - yarn run build The pipeline output did fill the

问题 When I run my job on Gitlab CI/CD, after a while I obtain the following error message: Job's log exceeded limit of 4194304 bytes. How to change this limit? 回答1: To change the build log size of your jobs in Gitlab CI/CD, you can edit your config.toml file and add a new limit in kilobytes: [[runners]] output_limit = 10000 According to the documentation output_limit : Set maximum build log size in kilobytes, by default set to 4096 (4MB) 来源： https://stackoverflow.com/questions/53541000/gitlab-ci