Branching SOP: Difference between revisions

Latest revision as of 17:50, 3 November 2015

This page is deprecated
All Fedora Release Engineering Documentation has moved here with source hosted along side the code in the releng pagure repository

Shortcut: RSOP:BRANCH

Description

This SOP covers how to make git and pkgdb branches for packages, either for new packages that have passed review, or for existing packages that need a new branch (e.g. EPEL). Release Engineering has written a script to automate this process.

Normal Action (automated)

1) On your local system (not on an infrastructure hosted system), be sure you have the following packages installed:

python-bugzilla
python-configobj
python-fedora

2) Run "bugzilla login" and successfully receive an Authorization cookie.

3) Clone the fedora-infrastructure tools repository:

git clone ssh://git.fedorahosted.org/git/releng.git

4) In scripts/process-git-requests, run "process-git-requests". Answer the prompts.

Manual Action

Creating a new branch for an existing package

1) ssh into pkgs.fedoraproject.org

2) pkgdb-client edit -u $YOURUSERNAME -b $NEWBRANCH --master=devel $NAMEOFPACKAGE

3) pkgdb2branch.py $NAMEOFPACKAGE

@@ Line 1: / Line 1: @@
+{{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source hosted along side the code in the [https://pagure.io/releng releng pagure repository]}}
 {{shortcut|RSOP:BRANCH}}
 == Description ==
@@ Line 17: / Line 19: @@
 ) Clone the fedora-infrastructure tools repository:
 <pre>
-git clone ssh://git.fedorahosted.org/git/fedora-infrastructure.git
+git clone ssh://git.fedorahosted.org/git/releng.git
 </pre>
@@ Line 24: / Line 26: @@
 == Manual Action ==
-TODO
+=== Creating a new branch for an existing package ===
+) ssh into pkgs.fedoraproject.org
+) pkgdb-client edit -u $YOURUSERNAME -b $NEWBRANCH --master=devel $NAMEOFPACKAGE
+) pkgdb2branch.py $NAMEOFPACKAGE
 [[Category:Release Engineering SOPs]]

Search