Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 4 additions & 8 deletions fedora-ci/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,12 +3,8 @@ title: Configuration
sidebar_position: 3
---

During the development phase, maintainers can opt in by adding their dist-git repository to the configuration [here](https://github.com/packit/deployment/blob/2cd9e846a6ab1c320f6a6c589e4bcab6b3cfb762/secrets/packit/prod/packit-service.yaml.j2#L105)
and submitting a [pull request](https://github.com/packit/deployment/pulls).
Fedora CI is now enabled by default for all Fedora dist-git repositories with a global default configuration.

You can use [scripts/enroll-users.py](https://github.com/packit/deployment/blob/main/scripts/enroll-users.py)
to enroll all packages maintained by you or your group (similar to the now obsolete [zuul-config-generator](https://github.com/befeleme/zuul-config-generator)).
Simply create a new branch, run the script as `./scripts/enroll-useres.py <fas-username>` and commit the changes.

In later phases, CI will run by default on all packages. The exact details of test plan configuration are still
being finalized, but the plan is to have a global default configuration that works well for most repositories.
If you need to opt out, you can request your repository to be added to the
[`disabled_projects_for_fedora_ci`](https://github.com/packit/deployment/blob/main/secrets/packit/prod/packit-service.yaml.j2)
list by submitting a [pull request](https://github.com/packit/deployment/pulls).
2 changes: 1 addition & 1 deletion fedora-ci/development.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,4 +23,4 @@ sidebar_position: 4
- [x] Phase 1: Introduce scratch builds for Fedora dist-git PRs (opt-in).
- [x] Phase 2: Implement installability checks (opt-in).
- [x] Phase 3: Implement support for user-defined TMT tests (opt-in).
- [ ] Final Phase: Transition to the new Packit-based CI as the default mechanism, replacing Fedora CI.
- [x] Final Phase: Transition to the new Packit-based CI as the default mechanism, replacing Fedora CI.
12 changes: 8 additions & 4 deletions fedora-ci/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,15 @@ id: index
---

Packit as Fedora dist-git CI is implemented as part of [this Fedora change proposal](https://fedoraproject.org/wiki/Changes/PackitDistgitCI).
The implementation is currently in progress.
This initiative aims to transition Fedora dist-git CI to a Packit-based solution, deprecating Fedora CI and Fedora Zuul Tenant.
This initiative transitioned Fedora dist-git CI to a Packit-based solution, deprecating Fedora CI and Fedora Zuul Tenant.
The change affects the triggering and reporting mechanism for tests but does not alter the tests themselves or the test
execution service ([Testing Farm](https://docs.testing-farm.io/Testing%20Farm/0.1/index.html)). The transition will be gradual, allowing maintainers to try the integration out,
provide feedback and catch issues early.
execution service ([Testing Farm](https://docs.testing-farm.io/Testing%20Farm/0.1/index.html)).

**Fedora CI is now enabled by default for all Fedora dist-git repositories.**

If you need to opt out, you can request your repository to be added to the
[`disabled_projects_for_fedora_ci`](https://github.com/packit/deployment/blob/main/secrets/packit/prod/packit-service.yaml.j2)
list in the Packit deployment configuration.

For more info continue with:

Expand Down
Loading