gitlab-ci-runner

Build Errors unable to find jq. Err http://deb.debian.org jessie/main amd64 Packages 404 Not Found Err http://deb.debian.org jessie-updates/main amd64 Packages 404 Not Found Fetched 723 kB in 2s (357 kB/s) W: Failed to fetch http://deb.debian.org/debian/dists/jessie/main/binary-amd64/Packages 404 Not Found W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found E: Some index files failed to download. They have been ignored, or old ones used instead. $ apt-get install jq Reading package lists... Building dependency tree... Reading state

I am trying to host a reveal.js presentation via gitlab pages. The repository can be found here: https://gitlab.com/JanGregor/demo-slides My .gitlab-ci.yml is fairly simple: image: node:4.2.2 pages: cache: paths: - node_modules/ script: - npm install - node_modules/.bin/gulp artifacts: paths: - build only: - master After a commit to master though, something goes wrong. The pages task itself is executed and runs just fine . It even shows in the logs that my build directory has been scanned and that the artefacts have been found. Oddly, the subsequent pages:deploy task fails. It only says :

I'm using docker in docker to host my containers as they work through the pipeline. The container I create from my code is setup to have a volume to pass in a gcloud key to the container. This works perfectly on my local machine, but on the gitlab-runner it doesn't link correctly. From reading this appears to be because it links the host to my container, rather than the dind host to my container. How do I link the directory that is inside dind to my container? (Also ignore any minor issues with tagging and such, this ci file is very early in development) GitLab ci below image: docker:latest

I'm trying to run my Gitlab CI locally using Gitlab-runner and docker before committing to make sure they work okay. But I'm having some strange issues! Unfortunately I have no choice but to use windows (I've had success in the past on Linux). Every time I run a job in powershell: C:/Gitlab-runner/gitlab-runner exec docker npm I get an error: Job failed (system failure): Error response from daemon: invalid volume specification: '/host_mnt/c/builds/project-0/Users/Lewsmith/api:C:/Users/Lewsmith/api:ro' (executor_docker.go:921:0s) I've tried setting docker volumes (nemerous combinations) and

I have a .gitlab-ci.yml file: integration_test: services: - name: registry.gitlab.com/group/project/testmailserver:1.1 alias: "mail.email" stage: test script: - ./gradlew -g /cache/.gradle --stacktrace --info integrationTest The service is a full stack email server based on this: tvial/docker-mailserver:latest . Locally with my docker-compose config I'm able to run it and connect to it. version: '2' services: mail: image: registry.gitlab.com/group/project/testmailserver:1.1 hostname: mail domainname: localhost ports: - "25:25" - "143:143" - "587:587" - "993:993" environment: - ONE_DIR=1 - DMS

I have the following configuration as .gitlab-ci.yml but I found out after successfully pass build stage (which would create a virtualenv called venv), it seems that in test stage you would get a brand new environment(there's no venv directory at all). So I wonder should I put setup script in before_script therefor it would run in each phase(build/test/deploy). Is it a right way to do it ? before_script: - uname -r types: - build - test - deploy job_install: type: build script: - apt-get update - apt-get install -y libncurses5-dev - apt-get install -y libxml2-dev libxslt1-dev - apt-get install

I have a gitlab-ci-runner setup for linux in a straight forward way (cmake, make, make test). Here is how it roughly looks: variables: GIT_SUBMODULE_STRATEGY: recursive stages: - build - test build: stage: build script: - cd build - sh createBuildScripts.sh - cd release - make - cd ../.. artifacts: untracked: true only: - master # run tests using the binary built before test: stage: test script: - cd build - cd release - make test only: - master With Visual Studio 2017 having cmake support built-in, I was wondering if there is now a similarly simple solution available for windows? 来源： https:/

I'm using .gitlab-ci.yml and docker as a GitLab CI runner on an Android project. At the end of the test run, gradlew saves test results in xml and html under the build directory: Finished generating test XML results (0.001 secs) into: /builds/org/project/sdk/build/test-results/release Generating HTML test report... Finished generating test html results (0.002 secs) into: /builds/org/project/sdk/build/reports/tests/release I'd like to have access to these files, but the documentation doesn't mention how to mount a volume like one would with docker run -v <path>:/builds/org/... . I would advice

We recently started to use GitLab-CI on the gitlab.com free service. At first everything went fine, but now, seems like we can't build our project anymore. The builds are shown as pending and doesn't do anything. Here's what we have in our builds list: And if we check the details of a build: As you might notice, in the list, each build is assigned to a runner id, but in the details page, the runner section is blank. At first, we thought it was just latency caused by gitlab.com ingrastructure, but it's really just stuck there... EDIT It's more than 1 year ago but I keep having notifications