From da06135330b38f86cb207d0fdc287398077ba6f7 Mon Sep 17 00:00:00 2001 From: Martin Pitt Date: Tue, 28 Aug 2018 22:20:58 +0200 Subject: [PATCH] cockpituous-release: Show how to do Fedora uploads Closes #40 --- cockpituous-release | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/cockpituous-release b/cockpituous-release index a4fda06..b876779 100644 --- a/cockpituous-release +++ b/cockpituous-release @@ -4,6 +4,8 @@ # Anything that start with 'job' may run in a way that it SIGSTOP's # itself when preliminary preparition and then gets a SIGCONT in # order to complete its work. +# +# Check cockpituous documentation for available release targets. RELEASE_SOURCE="_release/source" RELEASE_SPEC="cockpit-starter-kit.spec" @@ -11,6 +13,19 @@ RELEASE_SRPM="_release/srpm" job release-source job release-srpm + +# Once you have a Fedora package and add the https://pagure.io/user/cockpit +# user to your project's maintainers, you can also upload to Fedora automatically: + +## Authenticate for pushing into Fedora dist-git (works in Cockpituous release container) +# cat ~/.fedora-password | kinit cockpit@FEDORAPROJECT.ORG +## Do fedora builds for the tag, using tarball +# job release-koji -k master +# job release-koji f29 +# job release-bodhi F29 + +# These are likely the first of your release targets; but run them after Fedora uploads, +# so that failures there will fail the release early, before publishing on GitHub + # job release-github # job release-copr @myorg/myrepo -# check cockpituous documentation for available release targets