I&#39;d like to use GitLab CI with the .gitlab-ci.yml file to run different stages with separate scripts. The first stage produces a tool that must be used in a later stage to perform tests. I&#39;ve declared the generated tool as artifact.

Now how can I execute that tool in a later stage job? What is the correct path, and what files will there be around it?

For example the first stage builds artifacts/bin/TestTool/TestTool.exe and that directory contains other required files (DLLs and others). My .gitlab-ci.yml file looks like this:

    releasebuild:
      script:
        - chcp 65001
        - build.cmd
      stage: build
      artifacts:
        paths:
          - artifacts/bin/TestTool/
    
    systemtests:
      script:
        - chcp 65001
        - WHAT TO WRITE HERE?
      stage: test

The build and tests run on Windows if that&#39;s relevant.

How can I pass artifacts to another stage?

I use the [new *command line tools* for Android][1] because the old *sdk-tools* repository of Android isn&#39;t available anymore. So I changed my gitlab-ci to load the `commandlintools`. But when I try to run it I get the following error:

    Warning: Could not create settings
    java.lang.IllegalArgumentException
    	at com.android.sdklib.tool.sdkmanager.SdkManagerCliSettings.&lt;init&gt;(SdkManagerCliSettings.java:428)
    	at com.android.sdklib.tool.sdkmanager.SdkManagerCliSettings.createSettings(SdkManagerCliSettings.java:152)
    	at com.android.sdklib.tool.sdkmanager.SdkManagerCliSettings.createSettings(SdkManagerCliSettings.java:134)
    	at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:57)
    	at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)


I already tried executing those commandy by hand, but I get the same error. Also if I run `sdkmanager --version`, the same error occurs.
My gitlab-ci looks like:

    image: openjdk:9-jdk
    
    variables:
      ANDROID_COMPILE_SDK: &quot;29&quot;
      ANDROID_BUILD_TOOLS: &quot;29.0.3&quot;
      ANDROID_SDK_TOOLS:   &quot;6200805&quot;
    
    before_script:
      - apt-get --quiet update --yes
      - apt-get --quiet install --yes wget tar unzip lib32stdc++6 lib32z1
      - wget --quiet --output-document=android-sdk.zip https://dl.google.com/android/repository/commandlinetools-linux-${ANDROID_SDK_TOOLS}_latest.zip
      - unzip -d android-sdk-linux android-sdk.zip
      - echo y | android-sdk-linux/tools/bin/sdkmanager &quot;platform-tools&quot; &quot;platforms;android-${ANDROID_COMPILE_SDK}&quot; &gt;/dev/null
      #- echo y | android-sdk-linux/tools/bin/sdkmanager &quot;platform-tools&quot; &gt;/dev/null
      - echo y | android-sdk-linux/tools/bin/sdkmanager &quot;build-tools;${ANDROID_BUILD_TOOLS}&quot; &gt;/dev/null
      - export ANDROID_HOME=$PWD/android-sdk-linux
      - export PATH=$PATH:$PWD/android-sdk-linux/platform-tools/
      - chmod +x ./gradlew
      # temporarily disable checking for EPIPE error and use yes to accept all licenses
      - set +o pipefail
      - yes | android-sdk-linux/tools/bin/sdkmanager --licenses
      - set -o pipefail
    
    stages:
      - build
      - test
    
    lintDebug:
      stage: build
      script:
        - ./gradlew -Pci --console=plain :app:lintDebug -PbuildDir=lint
    
    assembleDebug:
      stage: build
      script:
        - ./gradlew assembleDebug
      artifacts:
        paths:
        - app/build/outputs/
    
    debugTests:
      stage: test
      script:
        - ./gradlew -Pci --console=plain :app:testDebug


  [1]: https://developer.android.com/studio/#command-tools

Android Command line tools sdkmanager always shows: Warning: Could not create settings

If a GitLab project is configured on GitLab CI, is there a way to run the build locally?

I don&#39;t want to turn my laptop into a build &quot;runner&quot;, I just want to take advantage of Docker and `.gitlab-ci.yml` to run tests locally (i.e. it&#39;s all pre-configured). Another advantage of that is that I&#39;m sure that I&#39;m using the same environment locally and on CI.

Here is an example of [how to run Travis builds locally using Docker](https://github.com/jolicode/JoliCi), I&#39;m looking for something similar with GitLab.

Use GitLab CI to run tests locally?

What is the difference between Jenkins and other CI like GitLab CI, drone.io coming with the Git distribution. On some research I could only come up that GitLab community edition doesn&#39;t allow Jenkins to be added, but GitLab enterprise edition does. Are there any other significant differences?


GitLab CI vs. Jenkins

I&#39;m trying to write a `gitlab-ci.yml` file which uses a multi-line string for the command. However, it seems like it is not being parsed. I&#39;ve tried both the `- |` and `- &gt;` with identical results.

    stages:
      - mystage

    Build:
      stage: mystage
      script:
        - |
            echo -e &quot;
                echo &#39;hi&#39;;
                echo &#39;bye&#39;;
            &quot;

When it tries to run, it only shows `echo -e &#39;` as the script to run, and not the whole multiline string. This causes issues for me.

What would be the correct syntax to write something like this?

Multiline YAML string for GitLab CI (.gitlab-ci.yml)

How to use if else condition inside the gitlab-CI.

I have below code:

    deploy-dev:
      image: testimage
      environment: dev
      tags:
        - kubectl
      script:
       - kubectl apply -f demo1 --record=true
       - kubectl apply -f demo2 --record=true


Now I want to add a condition something like this

    script:
        - (if [ &quot;$flag&quot; == &quot;true&quot; ]; then kubectl apply -f demo1 --record=true; else kubectl apply -f demo2 --record=true);

Could someone provide the correct syntax for the same? Is there any documentation for the conditions (if-else, for loop) in gitlabci?



How to use if-else condition on gitlabci

Here is my problem setup with GitLab and its integrated CI service. I have a current GitLab 8.1. and a gitlabci-multi-runner (0.6.2) with Docker support. After extending the ubuntu:precise image to include `git` and `build-essentials` (now named *precise:base*) I got the following `.gitlab-ci.yml` running:

    image: precise:base
    before_script:
       - apt-get install --yes cmake libmatio-dev libblas-dev libsqlite3-dev libcurl4-openssl-dev
       - apt-get install --yes libarchive-dev liblzma-dev
    
    build:
      script:
        - mkdir build/
        - cd build
        - cmake -D CMAKE_BUILD_TYPE=Debug ../
        - make

Now my question is how to include more jobs on different images? Because I need to check if the code compiles (and later on works) on different operating systems like Ubuntu Precise, Ubuntu Trusty, CentOS 6, CentOS 7. To reduce the work I think the best way is to provide different Docker images as base.  

Now the questions is how must the `.gitlab-ci.yml` look like to support this? 

Multiple Docker images in .gitlab-ci.yml

I got the following error during a `terraform plan` which occured in my pipeline:

    Error: Error locking state: Error acquiring the state lock: ConditionalCheckFailedException: The conditional request failed
    Lock Info:
    ID:        9db590f1-b6fe-c5f2-2678-8804f089deba
    Path:      ...
    Operation: OperationTypePlan
    Who:       ...
    Version:   0.12.25
    Created:   2020-05-29 12:52:25.690864752 +0000 UTC
    Info:      
    Terraform acquires a state lock to protect the state from being written
    by multiple users at the same time. Please resolve the issue above and try
    again. For most commands, you can disable locking with the &quot;-lock=false&quot;
    flag, but this is not recommended.

It is weird because I&#39;m sure there is no other concurrent plan.
Is there a way to deal with this? How should I remove this lock?

Terraform: Error acquiring the state lock: ConditionalCheckFailedException

I have a `.gitlab-ci.yml` file which contains following:

&lt;!-- language: lang-yaml --&gt;

    image: docker:latest
    
    services:
      - docker:dind
    
    before_script:
      - docker info
      - docker-compose --version
    
    buildJob:
      stage: build
      tags:
        - docker
      script:
        - docker-compose build

But in `ci-log` I receive message:

&lt;!-- language: lang-bash

    $ docker-compose --version
    /bin/sh: eval: line 46: docker-compose: not found

What am I doing wrong?

Run docker-compose build in .gitlab-ci.yml

I use GitLab on their servers. I would like to download my latest built artifacts (build via GitLab CI) via the API like this:

```
curl --header &quot;PRIVATE-TOKEN: 9koXpg98eAheJpvBs5tK&quot; &quot;https://gitlab.com/api/v3/projects/1/builds/8/artifacts&quot;
```

Where do I find this project ID? Or is this way of using the API not intended for hosted GitLab projects?


Where do I find the project ID for the GitLab API?

How do I run a .gitlab-ci.yml job only on a tagged Master branch?

    job:
      script:
      - echo &quot;Do something&quot;
      only:
      - master
      - tags

The above code will run if either condition exists: a Master branch or a tagged commit. 

My goal is to have this run for a production deploy, but it would require that it be on the Master branch and that it be tagged (with a version). Otherwise, I&#39;ll have another job that will push to staging if its missing a tag.

How to run a gitlab-ci.yml job only on a tagged branch?

I&#39;m using GitLab CI to build a C# solution and try to pass some build artifacts from one build stage to another.

The problem is, that the artifacts are not located in a single directory but in different subdirectories, which however all have the same names `bin/` or `obj/`.

My `.gitlab-ci.yml` looks like the following:

    ...
    stages:
      - build
      - test
    
    build:
      stage: build
      script:
        CALL %MSBuild% ...
      artifacts:
        paths:
          - /**/bin/
          - /**/obj/
        expire_in: 6 hrs

    test:
      stage: test
      dependencies:
        - build
      ...

I tried to capture the artifacts using different ways, e.g.

    **/bin/
    **/obj/

(invalid syntax), or

    .*/bin/
    .*/obj/

but that one did not find any artifacts, just as `/**/bin/` and `/**/obj/`, giving me following errors:

    Uploading artifacts...
    WARNING: /**/bin/: no matching files
    WARNING: /**/obj/: no matching files

**How can I specify a subdirectory pattern to be scanned for artifacts? Or is this even possible at all?**

Simply using

    artifacts:
      untracked: true

is not an option, because of a huge untracked `packages/` subdirectory, which causes artifacts upload to fail because of a too large archive:

    Uploading artifacts...
    untracked: found 4513 files                        
    ERROR: Uploading artifacts to coordinator... too large archive  id=36 responseStatus=413 Request Entity Too Large token=...
    FATAL: Too large


How to specify wildcard artifacts subdirectories in .gitlab-ci.yml?

We use GitLab CI with shared runners to do our continuous integration. For each build, the runner downloads tons of maven artifacts.

Is there a way to configure GitLab CI to cache those artifacts so we can speed up the building process by preventing downloading the same artifact over and over again?

How to enable maven artifact caching for GitLab CI runner?

According to the official [gitlab documentation][1], one way to enable `docker build` within `ci` pipelines, is to make use of the `dind` service (in terms of `gitlab-ci` [services][2]).

However, as it is always the case with ci jobs running on docker executors, the `docker:latest` image is also needed.

Could someone explain:

- what is the difference between the `docker:dind` and the `docker:latest` images?
- (most importantly): __why__ are __both__ the service and the docker image needed (e.g. as indicated [in this example][3], linked to from the github documentation) to perform e.g. a `docker build` whithin a ci job? doesn&#39;t the `docker:latest` image (__within which the job will be executed__!) incorporate the docker daemon (and I think the `docker-compose` also), which are the tools necessary for the commands we need (e.g. `docker build`, `docker push` etc)?

Unless I am wrong, the question more or less becomes:

&gt; Why a docker client and a docker daemon cannot reside in the same docker (enabled) container

  [1]: https://docs.gitlab.com/ce/ci/docker/using_docker_build.html#use-docker-in-docker-executor
  [2]: https://docs.gitlab.com/ce/ci/services/
  [3]: https://gitlab.com/gitlab-examples/docker/blob/master/.gitlab-ci.yml

Role of docker-in-docker (dind) service in gitlab ci

We have a project that is composed of multiple (non-public) repositories. 

To build the whole project, the build system needs to have the files of all repositories (`master` branches).

Is there a way I can configure GitLab CI to provide the repositories I need?

I guess I could do a `git fetch` or similar during the CI build, but how to deal with authentication then? 

how to access multiple repositories in CI build?

I have been experimenting with no success whatsoever, I am running a Gitlab hosted on Linux, and trying to get my head around the CI functionality.
 
According to the Gitlab documentation you only need to create a `.gitlab-ci.yml` file, the Gitlab implementation of Travis-CI. Now from the looks of it you can accomplish a lot with the `.gitlab-ci.yml`, but a lot of the documentation is referencing Ruby and other languages. Nothing is said about how to build Java Maven projects.

How can I build a simple application in Java? Can I use the shared runner, or should I be using a specific runner, in that case what or which runner implementation should I choose: ssh, docker, or shell? Then, what should I put in the `.gitlab-ci.yml` file at least to build the project with Maven?

How to use Gitlab CI to build a Java Maven project?

I&#39;ve finally manage to make it work so that when you push to a branch job would launch, but I keep waiting for it to launch around 3min and then I&#39;ve got errors which I need to fix and then commit again, and then waiting again. How can I just ssh to that public runner and test `.gitlab-ci.yml` &quot;script&quot; part just in the bash? 

How can I test gitlab-ci.yml?

I have GitLab &amp; GitLab CI set up to host and test some of my private repos. For my composer modules under this system, I have Satis set up to resolve my private packages.

Obviously these private packages require an ssh key to clone them, and I have this working in the terminal - I can run composer install and get these packages, so long as I have the key added with `ssh-add` in the shell.

However, when running my tests in GitLab CI, if a project has any of these dependencies the tests will not complete as my GitLab instance needs authentication to get the deps (obviously), and the test fails saying `Host key verification failed`.

My question is how do I set this up so that when the runner runs the test it can authenticate to gitlab without a password? I have tried putting a password-less ssh-key in my runners `~/.ssh` folder, however the build wont even add the key, &quot;eval `ssh-agent -s`&quot; followed by ssh-add seems to fail saying the agent isn&#39;t running...

Getting GitLab CI to clone private repositories

When I run my job on Gitlab CI/CD, after a while I obtain the following error message:

    Job&#39;s log exceeded limit of 4194304 bytes.
How to change this limit?

Gitlab CI/CD job&#39;s log exceeded limit

Gitlab provides a `.gitlab-ci.yml` template for building and publishing images to its own registry (click &quot;new file&quot; in one of your project, select `.gitlab-ci.yml` and `docker`). The file looks like this and it works out of the box :)

&lt;!-- language: lang-yaml --&gt;

    # This file is a template, and might need editing before it works on your project.
    # Official docker image.
    image: docker:latest

    services:
      - docker:dind

    before_script:
      - docker login -u &quot;$CI_REGISTRY_USER&quot; -p &quot;$CI_REGISTRY_PASSWORD&quot; $CI_REGISTRY

    build-master:
      stage: build
      script:
        - docker build --pull -t &quot;$CI_REGISTRY_IMAGE&quot; .
        - docker push &quot;$CI_REGISTRY_IMAGE&quot;
      only:
        - master

    build:
      stage: build
      script:
        - docker build --pull -t &quot;$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG&quot; .
        - docker push &quot;$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG&quot;
      except:
        - master

But by default, this will publish to gitlab&#39;s registry. How can we publish to [docker hub](https://hub.docker.com/) instead?

How to publish docker images to docker hub from gitlab-ci

I&#39;m using a self-hosted `GitLab CI server` (community edition v8.9.5) and `gitlab-ci-multi-runner` 1.2.0 to build a project.  One of my pipeline stages (test) takes a while to run and I get the following erm:

&gt;     ERROR: Build failed: execution took longer than 3600 seconds

Where do I put the override for this timeout?  Can I apply it to just the test pipeline stage?

All Gitlab Ci Solutions on Gang of Coders

Total of 21 Gitlab Ci Solutions