Setup CI on the repo in the new forge #114

Closed
opened 2026-05-07 16:22:46 +00:00 by siosm · 9 comments
Owner

As we lost CI on pagure.io (ci/tickets#544 / releng/tickets#13222), we moved the config repo to https://forge.fedoraproject.org/atomic-desktops/config.

However we don't have a full replacement for the (limited) CI that existed before.

As we lost CI on pagure.io (https://forge.fedoraproject.org/ci/tickets/issues/544 / https://forge.fedoraproject.org/releng/tickets/issues/13222), we moved the config repo to https://forge.fedoraproject.org/atomic-desktops/config. However we don't have a full replacement for the (limited) CI that existed before. - Getting Forgejo runners: - ~~https://forge.fedoraproject.org/forge/forge/issues/364~~ - ~~https://forge.fedoraproject.org/forge/forge/issues/562~~ - [x] https://forge.fedoraproject.org/forge/forge/issues/563 - ~~https://forge.fedoraproject.org/forge/forge/issues/564~~ - We use Testing Farm now - Getting an organization on the staging forge: - [x] https://forge.fedoraproject.org/forge/forge/issues/546 - Test repo: https://forge.stg.fedoraproject.org/atomic-desktops/config-ci-test - Using testing farm with existing Forgejo runners: - [x] https://forge.fedoraproject.org/atomic-desktops/config/pulls/757 -> https://forge.fedoraproject.org/atomic-desktops/config/pulls/767 - Relies on https://forge.fedoraproject.org/forge/forge/issues/568 as this will block a runner slot for the entire duration of the job. - List of available composes for testing-farm jobs: https://api.testing-farm.io/v0.2/composes/public - Konflux: - Setting up a releng owned service account for Konflux: https://forge.fedoraproject.org/releng/tickets/issues/13341 - Requesting an new group to get an email alias in the meantime
Author
Owner

In the mean time, PRs to the right branch in https://github.com/travier/fedora-atomic-desktops-devel should get us some form of CI / build testing.

In the mean time, PRs to the right branch in https://github.com/travier/fedora-atomic-desktops-devel should get us some form of CI / build testing.
Author
Owner
Testing runners in the staging repo: https://forge.stg.fedoraproject.org/atomic-desktops/config-ci-test
Author
Owner

We now have compose build tests using testing-farm:

We now have compose build tests using testing-farm: - https://forge.fedoraproject.org/atomic-desktops/config/pulls/767 - https://forge.fedoraproject.org/atomic-desktops/config/pulls/769 - https://forge.fedoraproject.org/atomic-desktops/config/pulls/770
Author
Owner

With the improvements from forge/forge#568 and atomic-desktops/config#776, we have good parallel runs now.

With the improvements from https://forge.fedoraproject.org/forge/forge/issues/568 and https://forge.fedoraproject.org/atomic-desktops/config/pulls/776, we have good parallel runs now.

Hi @siosm, do you still need these?

Or is it covered by the TestingFarm dispatch?

Hi @siosm, do you still need these? - unprivileged aarch64 runner [forge/forge#562](https://forge.fedoraproject.org/forge/forge/issues/562) - privileged x86_64 runner https://forge.fedoraproject.org/forge/forge/issues/564 Or is it covered by the TestingFarm dispatch?
Author
Owner

Hey @lenkaseg. I think we are good right now with the Testing Farm setup so we can close them. We'll ask again if it turns out that's not enough. Thanks for the work on this!

Hey @lenkaseg. I think we are good right now with the Testing Farm setup so we can close them. We'll ask again if it turns out that's not enough. Thanks for the work on this!
Author
Owner

Let's mark this one as done for now. We can track the Konflux part in #91.

Let's mark this one as done for now. We can track the Konflux part in https://forge.fedoraproject.org/atomic-desktops/tracker/issues/91.
siosm closed this issue 2026-07-09 15:11:58 +00:00

Alright! The infra is created so in case you'd need them in the future, it should be a matter of a moment.
Currently there is one privileged aarch64 runner for atomic-desktops org on production instance and on staging as well. Do you want to keep those for experiments or should I remove them?

Alright! The infra is created so in case you'd need them in the future, it should be a matter of a moment. Currently there is one privileged aarch64 runner for atomic-desktops org on production instance and on staging as well. Do you want to keep those for experiments or should I remove them?
Member

Please don't remove the runners from the staging instance. Thanks!

Please don't remove the runners from the staging instance. Thanks!
Sign in to join this conversation.
No description provided.