Home Home > 2008 > 12 > 01 > Saschas Backtrace: Yabsc for Builder
Sign up | Login

Deprecation notice: openSUSE Lizards user blog platform is deprecated, and will remain read only for the time being. Learn more...

Saschas Backtrace: Yabsc for Builder

December 1st, 2008 by

Today i tried out the Program called: yabsc. With http://software.opensuse.org/search?q=yabsc you can install the Program with one Klick. After the Installation the Program read the hints in the “.osc” Directory, and uses your Identity and Password for Checkin to Build Service API.

After the Program-Launch you see a Image like this:

yabsc1 Main Menue

On the left side you can see the Projects on your Watchlist. In the Center you see the Packages from the selected Project or Subproject. You can see the Buildlogs and Commitlogs directly.

On the second Tab “Workers”, you can see a image like this:


Here you can see the “actual” Status in the openSUSE Buildservice. In this tab you can follow the Buildlog on the fly.  This is an very good thing 🙂

The third tab, labeld as “submit requests”, you can see your Requests. But for this Function i haven’t an image, so i haven’t actually submit requests.

Now i can say, this is an very good, and very short Programm. Try it out!

Both comments and pings are currently closed.

One Response to “Saschas Backtrace: Yabsc for Builder”

  1. Adrian

    I really like that it shares the code with osc, our official command line client.

    Thanks a lot for this !

    Btw, I was thinking about what the usecases for a GUI client are, I mean areas where it is better than the console client and the web client. I think, this area could be code browsing and merging. Simply because you want something better than a command line client for walking around all the submit requests and source changes (because you can syntax highlight sources for example).

    On the other hand this client could prepare also code to be processed with other local tools on the workstation. For example opening the personal favorite editor for solving merge conflicts.

    It is just an idea, but maybe you should think about if this is indeed an area where your client can have strength over the CLI and Web client.