gitlab-ci-android | sample project used in the Gitlab blog post | Continous Integration library

Indeed JAVA_HOME is not set in the image but java binary is located under /usr/bin/java.

You can set JAVA_HOME in the same way you set GRADLE_USER_HOME, in before_script section :

First, you need to setup slack authentication keys.

1. Create App in Slack
2. Go to Authentication Section and Generate Authentication Key.
3. Get Channel Id which you want to receive messages.
4. Mention your app name in your slack thread and add the app to the channel.
5. Setup those keys in your GitLab ci setting variables.

SLACK_CHANNEL_ACCESS_TOKEN = Access Token Generated by Slack App

SLACK_CHANNEL_ID = Channel Id (Check URL Last section for the channel id)

8.Copy your existing Keystore file to the repository. (Please do this if your project is private.) 7.Change GitLab script's content to the below code.

Make sure to change certificate password,key password and alias.

Steps to register a Shared Runner:

Pre-requisite: Gitlab-Runner should have been installed. Follow this document for Installing Runner

• Login to Gitlab. Go to Admin Area >> Overview >> Runners >> Set up a shared Runner manually

• Login to the server where runner is installed, either with root user or the user with which you have installed runner (say gitlab-runner). Here, we are registering the runner using root user. Run the below command:

  gitlab-runner register

• Fill the following details according to your setup:

  • Please enter the gitlab-ci coordinator URL: https://example.com/gitlab/

    (Look for the url in the gitlab under Set up a shared Runner manually)

  • Please enter the gitlab-ci token for this runner: jiRS-3KxGaEdkLo6tToZ

    (Look for the token in the gitlab under Set up a shared Runner manually )

  • Please enter the gitlab-ci description for this runner: my-first-shred-runner

    (Enter any name for the runner)

  • Please enter the gitlab-ci tags for this runner (comma separated): ci-shared,ci-task

    (Enter any tags you want to associate with the runner)

  • Please enter the executor: docker-ssh, parallels, virtualbox, docker+machine, kubernetes, custom, docker, docker-ssh+machine, shell, ssh: shell

    (Enter the executor you need the runner to use, depending on choice of executor you will get other options to fill. Please go through documents of executors )

Now, you can see the message runner has been registered.

You can verify the same in the Gitlab. Go to Gitlab, Admin Area >> Overview >> Runners >> Set up a shared Runner manually and you can see the runner has been registered with name my-first-shred-runner

Steps to enable Shared Runner for a project in Gitlab:

1. Go to a Project in Gitlab.
2. Then, in the project page, Settings >> CI/CD >> Runners >> Shared Runners
3. Then, click on Enable shared runners. Now, you can use the shared runner for Gitlab CI/CD.
4. Use the tags associated with shared runner in .gitlab-ci.yml, so that the jobs will run using shared runner.

Change the tags in .gitlab-ci.yml

Either set BASE_URL within the .gitlab-ci.yml:

If you have active shared-runner, then try to give the tags of the runner in the .gitlab-ci.yml. Say if the tag for the shared-runner is dev-ci, then find below the updated code:

We shouldn’t store keystore file and credentials in version control system. We can hide credentials with creating keystore.properties file and using credentials from this file in signing config part like this: