gitlab-ci

问题 I am trying to build Aria2 in the docker image (CentOS 8). The local build of it (inside Docker/outside Docker) works fine. But a build in Gitlab CI with the SAME DOCKER IMAGE fails with an error: ./configure: line 13043: syntax error near unexpected token `libuv' ./configure: line 13043: `ARIA2_ARG_WITH(libuv)' I cat'ed this fragment of the configure file, it looks like: ... cat >>confdefs.h <<_ACEOF #define TARGET "$target" _ACEOF # Checks for arguments. ARIA2_ARG_WITH(libuv) ARIA2_ARG

问题 I am pushing packages to one of my gitlab repositories. All the packages are pushing fine except for one version of one package. I have three versions of the same package And I am giving this as the source to dotnet nuget push command and 2.0.0 and 2.0.1 packages are pushed successfully while 1.0.1 package is never getting pushed. And it does not give any error, it even shows in the command line that it is trying to push all the three folder packages one by one and showed success for all of

问题 I am using docker+machine to run my gitlab ci/cd jobs. So my .gitlab-ci.yml looks like below: stages: - RUN_TESTS image: name: docker:stable services: - name: docker:dind variables: DOCKER_HOST: tcp://docker:2375/ DOCKER_DRIVER: overlay2 DOCKER_TLS_CERTDIR: "" build-docker: stage: RUN_TESTS script: - echo "Running the tests..." - docker build -t run-tests . This works totally fine with docker:dind image set as the service block as shown above. Now here comes the fun part, I need some other

问题 I have a functional tests project for my ASP.NET Core 3.1 API that uses WebApplicationFactory to create a test server for the API. The tests pass locally and within a local docker-compose environment. However when run on the GitLab CI server within the same docker-compose environment the WebApplication factory's CreateClient method is blocking. When the test server starts the confluent Kafka Admin Service is blocking, i.e no confirmation log message is displayed confirming the topic created.

问题 I used pelican as the static site generator to build a static site. I wanted to host it on GitLab Pages and let the site generate with GitLab's continuous integration with Makefile. The site successfully builds locally as well as on GitLab via its CI/CD pipeline. The build code passes with artifacts uploaded and job succeeded. The content files are built and produced in the public folder. Somehow, after the build being passed and artifacts being uploaded in public folder as desired, it was

问题 I have a gitlab pipeline which has two stages as shown below: Below is my current .gitlab-ci.yml : stages: - build - push build: image: docker.repo.test.data/stuff/something:latest variables: LEGACY_VERSION: 10000 before_script: - export CI_PIPE_ID=`expr $CI_PIPE_ID + $OLDER_VERSION` script: - echo "Building Project" - ls -lrth - ./build-project push: stage: push image: docker.repo.test.data/stuff/something:latest only: - master script: - some stuff here In my build stage I try to build my

问题 I am setting up a CI build for my node project. Although my npm run test works as expected in my local environment, the gitlab ci is throwing an exception. The test command fails in: > nyc ./node_modules/.bin/cucumber-js ./test/BDD/**/*.feature -f node_modules/cucumber-pretty -f json:./test/report/cucumber_report.json --require-module ts-node/register --require ./test/**/*.ts Error: Parse error in 'test/BDD/step-definition.ts': (1:1): expected: #EOF, #Language, #TagLine, #FeatureLine,

问题 I have a GitLab project and my .gitlab-ci.yml looks like this: stages: - build - deploy image: registry.gitlab.com/myuser/myproj/ubuntuxenial:v1 before_script: - cd /home - mkdir docker - cd docker - git clone "https://xxx@github.com/myuser/myproj.git" repo - cd repo render_site: stage: build artifacts: name: "$CI_JOB_NAME-$CI_COMMIT_REF_NAME--$CI_JOB_STAGE-$CI_COMMIT_REF_NAME" expire_in: 1 week paths: - home/docker/repo/ script: - Rscript build.R ... I have provided the essential parts of

问题 I'm currently developing Quarkus applications and need therefore a CI Pipeline + Container Registry. As containerization through docker isn't working (docker daemon - priviliged mode) I want to use Jib, which is already supported by Quarkus. Command in Pipeline: - mvn clean package -Dquarkus.container-image.push=true -Dquarkus.container-image.registry="https://$registry" -Dquarkus.container-image.username=$username -Dquarkus.container-image.password=$deployToken -Dquarkus.container-image.name

问题 I'm currently developing Quarkus applications and need therefore a CI Pipeline + Container Registry. As containerization through docker isn't working (docker daemon - priviliged mode) I want to use Jib, which is already supported by Quarkus. Command in Pipeline: - mvn clean package -Dquarkus.container-image.push=true -Dquarkus.container-image.registry="https://$registry" -Dquarkus.container-image.username=$username -Dquarkus.container-image.password=$deployToken -Dquarkus.container-image.name