Skip to content

Avoid running CI on self-hosted runner when possible #393

@Kailai-Wang

Description

@Kailai-Wang

Context

We run most of our CI jobs on a self-hosted machine, mostly because we want to push the docker image from there (where the docker credential is already configured)

This is causing a few problems:

  • the build is executed sequentially and very slow, especially when multiple PRs are pending
  • CI host is shared with other projects, which slows down the build further
  • They are not built in a standard env, so any env changes on the host could affect the output

image

Task

We should try to avoid using self-hosted runner when possible, especially for build & test.
We can leave as it is for other tasks where running on self-hosted runner is absolutely required (e.g. benchmarking, as we need to login to other remote hosts from the CI-host)

Acceptance criteria

  • remove all the self-hosted usage in build_and_run_test.yml

✔️ Please set appropriate labels and assignees if applicable.

Metadata

Metadata

Assignees

Labels

I2-mediumshould be completed within 10 working days

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions