Move example COPR release to packit

This replaces the cockpituous job.
This commit is contained in:
Martin Pitt 2022-05-03 09:20:03 +02:00 committed by Martin Pitt
parent bdd376e9e0
commit c639ffc276
4 changed files with 22 additions and 12 deletions

View file

@ -25,7 +25,6 @@ jobs:
# FIXME: Set your Fedora user account name here # FIXME: Set your Fedora user account name here
echo 'yourfedorauser' > ~/.config/bodhi-user echo 'yourfedorauser' > ~/.config/bodhi-user
echo '${{ secrets.GITHUB_TOKEN }}' > ~/.config/github-token echo '${{ secrets.GITHUB_TOKEN }}' > ~/.config/github-token
echo '${{ secrets.COPR_TOKEN }}' > ~/.config/copr
echo '${{ secrets.FEDORA_PASSWORD }}' > ~/.fedora-password echo '${{ secrets.FEDORA_PASSWORD }}' > ~/.fedora-password
- name: Run cockpituous - name: Run cockpituous

View file

@ -133,15 +133,18 @@ change:
Once your cloned project is ready for a release, you should consider automating Once your cloned project is ready for a release, you should consider automating
that. [Cockpituous release](https://github.com/cockpit-project/cockpituous/tree/main/release) that. [Cockpituous release](https://github.com/cockpit-project/cockpituous/tree/main/release)
aims to fully automate project releases to GitHub, Fedora, Ubuntu, COPR, Docker and [Packit](https://packit.dev/) aim to fully automate project releases to
Hub, and other places. The intention is that the only manual step for releasing GitHub, Fedora, Ubuntu, COPR, Docker Hub, and other places. The intention is
a project is to create a signed tag for the version number; pushing the tag that the only manual step for releasing a project is to create a signed tag for
then triggers a [GitHub action](https://github.com/features/actions) that calls a set of release scripts. the version number; pushing the tag then triggers a [GitHub
action](https://github.com/features/actions) that calls a set of release
scripts.
starter-kit includes an example [cockpitous release script](./cockpituous-release), starter-kit includes an example [cockpitous release script](./cockpituous-release)
with detailed comments how to use it. There is also an
[example GitHub release action](.github/workflows/release.yml.disabled) to set and a [packit.yaml](./packit.yaml) control file with detailed comments how to
up secrets and run cockpituous. use it. There is also an [example GitHub release action](.github/workflows/release.yml.disabled)
to set up secrets and run cockpituous.
# Automated maintenance # Automated maintenance

View file

@ -32,6 +32,3 @@ job release-srpm -V
# this needs no explicit secrets, just the GitHub action provided default one # this needs no explicit secrets, just the GitHub action provided default one
# job release-github # job release-github
# This needs secrets.COPR_TOKEN in .github/workflows/release.yml
# job release-copr @myorg/myrepo

View file

@ -32,3 +32,14 @@ jobs:
- fedora-all - fedora-all
- centos-stream-8 - centos-stream-8
- centos-stream-9 - centos-stream-9
# Build releases in COPR: https://packit.dev/docs/configuration/#copr_build
#- job: copr_build
# trigger: release
# metadata:
# owner: your_copr_login
# project: your_copr_project
# preserve_project: True
# targets:
# - fedora-all
# - centos-stream-9-x86_64