| |
@@ -24,18 +24,18 @@
|
| |
|
| |
Build all packages::
|
| |
|
| |
- releng/build-packages @copr/copr-dev
|
| |
+ releng/build-packages @copr/copr
|
| |
|
| |
Upgrade -dev machines
|
| |
---------------------
|
| |
|
| |
- Check that .repo files correctly points to copr-dev. And run on batcave01.phx2.fedoraproject.org (if you do not have account there ask Mirek or somebody from fedora-infra)::
|
| |
+ Check that .repo files correctly points to ``@copr/copr``. And run on batcave01.phx2.fedoraproject.org (if you do not have account there ask Mirek or somebody from fedora-infra)::
|
| |
|
| |
sudo rbac-playbook -l copr-be-dev.cloud.fedoraproject.org groups/copr-backend.yml
|
| |
|
| |
sudo rbac-playbook -l copr-keygen-dev.cloud.fedoraproject.org groups/copr-keygen.yml
|
| |
|
| |
- sudo rbac-playbook -l copr-fe-dev.cloud.fedoraproject.org groups/copr-frontend.yml
|
| |
+ sudo rbac-playbook -l copr-fe-dev.cloud.fedoraproject.org groups/copr-frontend-cloud.yml
|
| |
|
| |
sudo rbac-playbook -l copr-dist-git-dev.fedorainfracloud.org groups/copr-dist-git.yml
|
| |
|
| |
@@ -46,13 +46,20 @@
|
| |
|
| |
alembic upgrade head
|
| |
|
| |
+ Note: If there is a new version of copr-rpmbuild, run this on backend::
|
| |
+
|
| |
+ redis-cli
|
| |
+ 127.0.0.1:6379> FLUSHALL
|
| |
+ cleanup_vm_nova.py
|
| |
+ systemctl restart copr-backend
|
| |
+
|
| |
|
| |
Call for QA
|
| |
-----------
|
| |
|
| |
Move MODIFIED+ bugzillas to ON_QA.
|
| |
|
| |
- Ask people to test, verify bugs, and generally help with QA. They will ignore it but you will feel good about giving them a chance.
|
| |
+ Ask people to test, verify bugs, and generally help with QA. They will ignore it but you will feel good about giving them a chance.
|
| |
|
| |
Test
|
| |
----
|
| |
@@ -60,13 +67,6 @@
|
| |
Run :ref:`beaker_tests` and check the results.
|
| |
|
| |
|
| |
- Build packages for production
|
| |
- -----------------------------
|
| |
-
|
| |
- Build all packages for @copr projects::
|
| |
-
|
| |
- releng/build-packages @copr/copr
|
| |
-
|
| |
Release python-copr to PyPi
|
| |
---------------------------
|
| |
|
| |
@@ -78,10 +78,12 @@
|
| |
|
| |
If you cannot run that, tell somebody with access to run that (msuchy has access).
|
| |
|
| |
- Release package to Fedora
|
| |
- -------------------------
|
| |
+ .. _build_packages_for_production:
|
| |
+
|
| |
+ Build packages for production
|
| |
+ -----------------------------
|
| |
|
| |
- Make sure that ``releng/releasers.conf`` has up to date list of branches.
|
| |
+ Make sure that ``releng/releasers.ini`` has up to date list of branches.
|
| |
|
| |
Make sure you are co-maintainer of those packages in Fedora.
|
| |
|
| |
@@ -89,39 +91,61 @@
|
| |
|
| |
rm -r /tmp/rpkg
|
| |
|
| |
+ git checkout <latest-python-tag>
|
| |
rpkg --path python srpm --outdir /tmp/rpkg
|
| |
releng/fedora-release git-all /tmp/rpkg/python-copr*.src.rpm
|
| |
|
| |
+ git checkout <latest-cli-tag>
|
| |
rpkg --path cli srpm --outdir /tmp/rpkg
|
| |
releng/fedora-release git-all /tmp/rpkg/copr-cli*.src.rpm
|
| |
|
| |
+ git checkout <latest-frontend-tag>
|
| |
rpkg --path frontend srpm --outdir /tmp/rpkg
|
| |
releng/fedora-release git /tmp/rpkg/copr-frontend*.src.rpm
|
| |
|
| |
+ git checkout <latest-backend-tag>
|
| |
rpkg --path backend srpm --outdir /tmp/rpkg
|
| |
releng/fedora-release git /tmp/rpkg/copr-backend*.src.rpm
|
| |
|
| |
+ git checkout <latest-distgit-tag>
|
| |
rpkg --path dist-git srpm --outdir /tmp/rpkg
|
| |
releng/fedora-release git /tmp/rpkg/copr-dist-git*.src.rpm
|
| |
|
| |
+ git checkout <latest-keygen-tag>
|
| |
rpkg --path keygen srpm --outdir /tmp/rpkg
|
| |
releng/fedora-release git /tmp/rpkg/copr-keygen*.src.rpm
|
| |
|
| |
+ git checkout <latest-selinux-tag>
|
| |
rpkg --path selinux srpm --outdir /tmp/rpkg
|
| |
releng/fedora-release git /tmp/rpkg/copr-selinux*.src.rpm
|
| |
|
| |
+ git checkout <latest-prunerepo-tag>
|
| |
rpkg --path prunerepo srpm --outdir /tmp/rpkg
|
| |
releng/fedora-release git /tmp/rpkg/prunerepo*.src.rpm
|
| |
|
| |
+ git checkout <latest-common-tag>
|
| |
rpkg --path common srpm --outdir /tmp/rpkg
|
| |
releng/fedora-release git /tmp/rpkg/python-copr-common*.src.rpm
|
| |
|
| |
- And create erratas in Bodhi.
|
| |
+ git checkout <latest-srpm-tag>
|
| |
+ rpkg --path rpmbuild srpm --outdir /tmp/rpkg
|
| |
+ releng/fedora-release git /tmp/rpkg/copr-rpmbuild*.src.rpm
|
| |
+
|
| |
+ And submit them into `Infra tags repo <https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/infra-repo.html>`_.
|
| |
+ Not even every fedora infra member can to this, ping clime or ask on ``#fedora-admin``.
|
| |
+
|
| |
|
| |
Generate documentation
|
| |
----------------------
|
| |
|
| |
- Go to:
|
| |
+ Generate `Copr project documentation <https://docs.pagure.org/copr.copr/>`_
|
| |
+
|
| |
+ ::
|
| |
+
|
| |
+ cd doc
|
| |
+ ./update_docs.sh
|
| |
+
|
| |
+ Generate package specific documentation by going to:
|
| |
|
| |
* https://readthedocs.org/projects/copr-rest-api/
|
| |
|
| |
@@ -131,35 +155,55 @@
|
| |
|
| |
* https://readthedocs.org/projects/python-copr/
|
| |
|
| |
- And hit "Build" button for each of those projects.
|
| |
+ And hitting "Build" button for each of those projects.
|
| |
|
| |
If schema was modified you should generate new Schema documentation.
|
| |
|
| |
Prepare release notes
|
| |
---------------------
|
| |
|
| |
- Go over bugs, which were resolved. Write some nice announce.
|
| |
+ Go over bugs, which were resolved. Write some nice announce. It is useful to prepare the release notes beforehand
|
| |
+ because developers usualy don't remember what they worked on and therefore don't know what to test once
|
| |
+ production instances are upgraded. Sharing the prepared notes with team members before doing the actuall release
|
| |
+ is appreciated.
|
| |
+
|
| |
+ Schedule outage
|
| |
+ ---------------
|
| |
+
|
| |
+ Schedule outage even if it has to happen in the next 5 minutes!
|
| |
+
|
| |
+ Follow the instructions in `Outage SOP <https://docs.pagure.org/infra-docs/sysadmin-guide/sops/outage.html#id1>`_.
|
| |
|
| |
Upgrade production machines
|
| |
---------------------------
|
| |
|
| |
+ It is advised to stop ``copr-backend.service`` before upgrading production machines to avoid failing
|
| |
+ builds due to temporarily having installed incompatible versions of Copr packages.
|
| |
+
|
| |
Run on batcave01.phx2.fedoraproject.org (if you do not have account there ask Mirek or somebody from fedora-infra)::
|
| |
|
| |
sudo rbac-playbook -l copr-be.cloud.fedoraproject.org groups/copr-backend.yml
|
| |
|
| |
sudo rbac-playbook -l copr-keygen.cloud.fedoraproject.org groups/copr-keygen.yml
|
| |
|
| |
- sudo rbac-playbook -l copr-fe.cloud.fedoraproject.org groups/copr-frontend.yml
|
| |
+ sudo rbac-playbook -l copr-fe.cloud.fedoraproject.org groups/copr-frontend-cloud.yml
|
| |
|
| |
sudo rbac-playbook -l copr-dist-git.fedorainfracloud.org groups/copr-dist-git.yml
|
| |
|
| |
- Note: if need run manually DB upgrade.
|
| |
+ Note: You shouldn't need to upgrade DB manually, playbook covers it.
|
| |
+
|
| |
+ Note: If there is a new version of copr-rpmbuild, throw away all builders and reprovision them.
|
| |
|
| |
Test production machine
|
| |
-----------------------
|
| |
|
| |
Just run some build and check if it succeeds.
|
| |
|
| |
+ Submit Bodhi updates
|
| |
+ --------------------
|
| |
+
|
| |
+ Create updates in `Bodhi <https://bodhi.fedoraproject.org/>`_ for :ref:`every package built in Koji <build_packages_for_production>`.
|
| |
+
|
| |
Announce the release
|
| |
--------------------
|
| |
|
| |
@@ -168,12 +212,12 @@
|
| |
Post release
|
| |
------------
|
| |
|
| |
- Check if the MODIFIED bugs (that are not ON_QA) are fixed in released Copr or not, move them ON_QA if they are:
|
| |
+ Check if the `MODIFIED bugs <https://bugzilla.redhat.com/buglist.cgi?bug_status=POST&bug_status=MODIFIED&classification=Community&list_id=4678039&product=Copr&query_format=advanced>`_
|
| |
+ (that are not ON_QA) are fixed in released Copr or not, move them ON_QA.
|
| |
|
| |
- https://bugzilla.redhat.com/buglist.cgi?bug_status=POST&bug_status=MODIFIED&classification=Community&list_id=4678039&product=Copr&query_format=advanced
|
| |
|
| |
- Change status of all ON_DEV, ON_QA, VERIFIED, and RELEASE_PENDING bugs to CLOSED/CURRENTRELEASE with comment like 'New Copr has been released.':
|
| |
+ Change status of all `ON_DEV, ON_QA, VERIFIED, and RELEASE_PENDING bugs <https://bugzilla.redhat.com/buglist.cgi?bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&classification=Community&list_id=4678045&product=Copr&query_format=advanced>`_
|
| |
+ to CLOSED/CURRENTRELEASE with comment like 'New Copr has been released.'
|
| |
|
| |
- https://bugzilla.redhat.com/buglist.cgi?bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&classification=Community&list_id=4678045&product=Copr&query_format=advanced
|
| |
|
| |
Fix this document to make it easy for the release nanny of the next release to use it.
|
| |
During the last release, I found out, that the "How to release Copr" document is not up-to-date. This PR fixes it.
I was also thinking about restructuring the document to "pre-release", "outage window", "post-release" phases and also adding some templates for announcing a release and closing bugzillas, but those are enhancements, so I would rather do them in separate PR. This one deal mainly with outdated parts of the document.