ABF Console Client

What links here (3) →

Intro

Our team (or just me) is about to start the development of the long-awaited project, console client for ABF!

Firstly we have to make up the list of features. All the demands and proposals are welcome in this mailing list (rosa-devel) or here.

Naming

The name of the tool is not defined yet. You can write you ideas here.

Possible variants:

1. abfsys
2. abfcc
3. ... (add here)

Feature List

Here is the list of the proposed features.

<DONE> abfsys get PROJECT [-g GROUP] [-b BRANCH]

clone git repository, project group is set to GROUP or default

with -b BRANCH - checkout

<DONE> abfsys build [PROJECT] [-t PLATFORM] [-b BRANCH] [-p] [-a ARCHES]

Without parameters - build current project for default distribution from proper git branch; For example, build from latest_rosa2012.1 branch to rosa2012.1/main)

With PROJECT - select the project to operate on.

With BRANCH- build the project from that branch.

With PLATFORM - build the project to that platform.

If something is not specified - resolve it automatically. For example,

abfsys build mock-urpm -t rosa2012lts

will build mock-urpm from branch latest_rosa2012lts.

With -p - automatic publishing.

-a ARCHES - coma-separated list of arches to build. "i586,x86_64" by default

abfsys rebuild [PROJECT]

Execute the last executet abfsys build ... command for the project specified or to the current project if possible.

<DONE> abfsys buildstatus [ID]

Get the status of the build task with ID. If ID not set and you are inside the repository directory - get the id of the last project build.

abfsys localbuild

Build the project from cwd using mock. A set of parameters will be available later.

abfsys sync

Check and cleanup package sources and patches using current spec as base.

(delete all sources and patches from working directory if they are not listed in spec; inform if any listed patches/sources are missing; create proper file used to store tarballs on file server)

abfsys backport SRC_BRANCH [DST_BRANCH]

Copy all the files from SRC_BRANCH to DST_BRANCH, or to the current brunch if not specified.

<DONE> abfsys put -m "commit message"

Commit changes (git commit -am "message") and push (git push origin branch)

abfsys uploadsrpm SRPM_PATH [GROUP] [-h] [-n NAME] [-d DESCRIPTION]

Create a new project in group GROUP or in your default group and upload the files from srpm file.

-h - makes project hidden.

-n NAME - set the project name. If not specified - get from srpm

-d DESCRIPTION - project description.

abfsys detach GROUP/PRJ PLAT_TARGET/REPO_TARGET

Attach the project to the repository, or detach it from repository.

Attaching with PLAT_ORIG/REPO_ORIG will detach project from one repo and attach to another.

For example, two commands:

abfsys attach import/mc rosa2012lts/contrib abfsys attach import/mc rosa2012lts/main

equals:

abfsys move import/mc rosa2012lts/contrib rosa2012lts/main

Workflow

   When you start abfsys for the first time, it will ask you for your username, 
   password and some other things (if needed), and store it in ~/.abfsys . Later 
   the password will be stored using python-keyring or python-keyring-kde.

   There will be configuration files for every  in ~/.abfsys: