cockpit-composer/packit.yaml
Packit 8edee9e1e0 [packit] 46 upstream release
Upstream tag: 46
Upstream commit: 87b01caa

If you need to do any change in this pull request, you need to locally fetch the source branch of it and push it (with a fix) to your fork (as it is not possible to push to the branch created in the Packit’s fork):
```
git fetch https://src.fedoraproject.org/forks/packit/rpms/cockpit-composer.git refs/heads/*:refs/remotes/packit/*
git checkout packit/46-rawhide-update-propose_downstream
```
2023-08-25 18:43:13 +00:00

55 lines
1.5 KiB
YAML

upstream_project_url: https://github.com/osbuild/cockpit-composer
specfile_path: cockpit-composer.spec
upstream_package_name: cockpit-composer
downstream_package_name: cockpit-composer
# use the nicely formatted release description from our upstream release, instead of git shortlog
copy_upstream_release_description: true
actions:
post-upstream-clone: make spec
create-archive: make dist-gzip
srpm_build_deps:
- make
- npm
jobs:
- job: copr_build
trigger: release
metadata:
owner: "@osbuild"
project: "cockpit-composer"
preserve_project: True
targets:
- centos-stream-8
- centos-stream-9
- epel-8
- epel-9
- fedora-all
actions:
post-upstream-clone: make spec
# HACK: tarball for releases (copr_build, koji, etc.), copying spec's Source0; this
# really should be the default, see https://github.com/packit/packit-service/issues/1505
create-archive:
- sh -exc "curl -L -O https://github.com/osbuild/cockpit-composer/releases/download/${PACKIT_PROJECT_VERSION}/${PACKIT_PROJECT_NAME_VERSION}.tar.gz"
- sh -exc "ls ${PACKIT_PROJECT_NAME_VERSION}.tar.gz"
- job: propose_downstream
trigger: release
metadata:
dist_git_branches:
- fedora-all
- job: koji_build
trigger: commit
metadata:
dist_git_branches:
- fedora-all
- job: bodhi_update
trigger: commit
metadata:
dist_git_branches:
# rawhide updates are created automatically
- fedora-branched