prep config docs for the launch
@@ -74,8 +74,6 @@ synced_files:
### Packit service jobs
-**Packit service is not live, we are working on opening it to the world in June.**
-
Once the service starts handling events of your repository, it needs to have a clear definition of what it should do.
The tasks the packit service should do are defined in section `jobs`. This is a list of dicts.
@@ -92,33 +90,25 @@ Jobs can also accept additional configuration in a dict `metadata`.
#### Supported jobs
-**propose\_downstream**
-
-Take the new upstream release and land it in Fedora.
+**copr\_build**
-Supported triggers: **release**.
+Gather data from new pull_request or release and use trigger new copr build with it.
-Additional configuration set in the `metadata` section:
-* `dist_git_branch`: name of the dist-git branch where the PR should be opened.
+Supported triggers: **pull_request**, **release**.
**Example**
```yaml
jobs:
-- job: propose_downstream
- trigger: release
- metadata:
- dist_git_branch: master
-- job: propose_downstream
- trigger: release
+- job: copr_build
+ trigger: pull_request
metadata:
- dist_git_branch: f30
-```
+ targets:
+ - fedora-rawhide-x86_64
+ - fedora-30-x86_64
-With this configuration, packit service would react to new upstream releases
-and create dist-git pull requests for master and f30 branches with the
-content of the upstream release.
+```
**sync\_from\_downstream**
@@ -137,31 +127,6 @@ jobs:
trigger: commit
```
-**copr\_build**
-
-Gather data from new pull_request or release and use trigger new copr build with it.
-
-Supported triggers: **pull_request**, **release**.
-
-
-**Example**
-
-```yaml
-jobs:
-- job: copr_build
- trigger: pull_request
- metadata:
- targets:
- - fedora-rawhide-x86_64
- - fedora-30-x86_64
-
-```
-
-### In-progress work
-
-You may see packit configs with more values: support for checks is work in progress.
-Packit is not using those values right now.
-
## User configuration file
