CODEWITHSUNDEEP
gitlabgitlab-cigitlab-ci-runner
Jeen Mathew
Jeen Mathew

Reputation: 3

Gitlab Runner to run jobs on selected runners according to custom variable

I am planning to schedule jobs on runners based on variable from pipeline web UI. I have two runners registered for a project and currently both are on same machine for now.Both runners are having the same tags so differentiation from tags is not possible too.

This is my yaml file

stages :
  - common
  - specific
test1:
  stage: common
  tags:
    - runner
    - linux
  script:
    - echo $CI_RUNNER_DESCRIPTION
    - echo "This is run on all runners"
test2:
  stage: specific
  tags:
    - runner
    - linux
  script: echo "This is run on runner 1" 
  only:
    variables:
      - $num == $CI_RUNNER_DESCRIPTION

test3:
  stage: specific
  tags:
    - runner
    - linux
  script: echo "This is run on runner 2"
  only:
    variables:
      - $num == $CI_RUNNER_DESCRIPTION

So variable on which the selection happens is "num". The description of the runners can be 1 or 2. The default value for num is 0 and according to variable passed from pipeline UI, the jobs are to be selected and run. But when I execute the test with num 1 or 2, only test1 gets executed which is common to all runners.

Is such a implementation possible or am I facing issue because the runners are on same machine ?

Upvotes: 0

Views: 4878

Answers (2)

zm31
zm31

Reputation: 269

You cannot do this currently with gitlab. As you noted in your comment on the accepted answer, this will be available when https://gitlab.com/gitlab-org/gitlab/-/issues/35742 is resolved.

That being said, while the "accepted" answer correctly states "only" is the incorrect way to do this, it suggests another way that also doesnt work.

Once dynamic tagging support is added into gitlab-ci, this will be possible. Currently, the solution is to provide unique jobs each with their own tags.

Depending on what exactly you are trying to accomplish, you can keep your code as DRY as possible for now by adding job templates in combination with extends to reduce duplication to a couple of lines per job.

Upvotes: 0

makozaki
makozaki

Reputation: 4366

Using variables only is not the right approach to select runners. Right now you select one of the 2 runners and try not to execute job if runner description doesn't match. Even if this worked it wouldn't make much sense as you don't know if the job will be executed or not. I suggest you add specific labels for runners and specify which job should run on which runner.

test2:
  stage: specific
  tags:
    - runner_1
  script: echo "This is run on runner 1" 

test3:
  stage: specific
  tags:
    - runner_2
  script: echo "This is run on runner 2"

If you want to select runner for the job based on UI input, maybe you can add variable to tags section. To be honest I didn't test such solution and donno if it's gonna work. Yet still it would require to create specific tags for your runners.

  tags:
    - $tag_variable_selected_from_UI

Upvotes: 0

Related Questions