<p>Answering my own question here. &quot;Multi project pipeline&quot; is not necessary here. You simply have a single project and mark jobs with different &quot;tags&quot;. You can then register runners for these different tags, on different machines.</p>
<p>(Artifacts are transferred from one job to the next the same, regardless if the runners are run on the same machine or on different ones)</p>
<p><a href="https://docs.gitlab.com/ee/ci/yaml/README.html#tags" rel="nofollow noreferrer">https://docs.gitlab.com/ee/ci/yaml/README.html#tags</a></p>

CC BY-SA 4.0
2021-02-15T11:40:05.473Z
2021-02-15T11:40:05.473Z
petke
<p>I'm learning gitlab and am asking for advice / best practice here.</p>
<p>I want to install a program to a different machine than the build computer, and run some automatic tests on that machine. How is this best done?</p>
<p>I think this can be accomplished with the &quot;multi project pipeline&quot; feature. Is this the simplest/best way?</p>
<p>Here is my plan:</p>
<p>I could have one (shell) runner and project for my build machine, and a different runner and project for my test machine. The two would be connected using &quot;multi project pipeline&quot; feature. The artifacts from the build pipeline would be installed on the test machine and then system tests would run on the test machine.</p>
<p>Is this the best way to solve this? Or is there a simpler/better way?</p>
<p>Edit: The test machine has special hardware/enviornment necessary for the program to run. That's why program needs to be installed there.</p>

<gitlab><gitlab-ci-runner>
Howto run test on test computer instead of build computer, using gitlab
petke
# Howto run test on test computer instead of build computer, using gitlab

(Asked by: username_0 on 2021-02-05)

I'm learning gitlab and am asking for advice / best practice here.

I want to install a program to a different machine than the build computer, and run some automatic tests on that machine. How is this best done?

I think this can be accomplished with the "multi project pipeline" feature. Is this the simplest/best way?

Here is my plan:

I could have one (shell) runner and project for my build machine, and a different runner and project for my test machine. The two would be connected using "multi project pipeline" feature. The artifacts from the build pipeline would be installed on the test machine and then system tests would run on the test machine.

Is this the best way to solve this? Or is there a simpler/better way?

Edit: The test machine has special hardware/enviornment necessary for the program to run. That's why program needs to be installed there.

**Tags:** gitlab, gitlab-ci-runner


---

## 1 answers

### Answer by username_0 on 2021-02-15. Score: 1

Answering my own question here. "Multi project pipeline" is not necessary here. You simply have a single project and mark jobs with different "tags". You can then register runners for these different tags, on different machines.

(Artifacts are transferred from one job to the next the same, regardless if the runners are run on the same machine or on different ones)

<https://docs.gitlab.com/ee/ci/yaml/README.html#tags>


---

