Contents 1 Creating a link and adding a repository 1.1 Startpage and Login 1.2 Create a link to a package in your home: 1.2.1 Add link to existing package 1.2.2 Add repository / build target 1.2.3 Package page, build log and project monitor page 1.3 Repository Output: Built Packages 1.4 Summary

Creating a link and adding a repository

Welcome to the MeeGo OBS webinterface guide - part 2. We'll show you how you can login and use the webinterface being hosted at build.meego.com . This includes login, adding a link to a package in your personal workspace (home:) and how to build that package by adding a repository.

Please note: you'll need an account to access the build service server.
See this page on the progress of the Community Builder.

Startpage and Login

Open your favourite browser and navigate to https://build.meego.com. You'll be directed to the startpage.

To proceed, you'll need to login and authenticate with your username and your password. Enter the data in the upper right corner.

After successful authentication, you'll end up on the startpage again - with new options visible.

Create a link to a package in your home:

Enter "My Projects" by clicking on the link at the bottom left. You'll see this page as setup in part 1:

Now lets create a link to a package and add a repository to build against. A link is basically a pointer to sources of an already existing package in another project. By *repository*, we mean a build target - e.g. like Trunk/Fedora_12/openSUSE_11.2. Lets follow these steps:

1. Add link to the existing package.
2. Add repository / build target.
3. Enable the build (optional, if not already enabled).
4. Observe the build on the monitor page
5. Look at package's page

Add link to existing package

Right below packages, there's "Link Package from other Project" .

Open that page and enter for

Name of original project:
MeeGo:1.0:Core

and for

Name of package in original project:
bash

- we'll leave "Name of linked package in target project" empty.

This is shown on the next picture:

Proceed with "Create Link" and you'll be redirected to your home again. You'll see a new package "bash" and a notice about the link being added.

Wonderful, we've added a pointer to the sources - now we need a build repository added, so the builder knows the target-distribution.

Add repository / build target

To do this, click on "Add Repository". This will look like:

Now select "Meego:Trunk/standard" as target repository:

(if it is not in the initial list, see if there an an Advanced link to a more comprehensive list). This will take you back to your home: project. The build repository might be disabled: if so, klick on the cogwheel to enable it.

Congratulations, it is configured. On a heavily loaded server it can sometimes take a few minutes for your changes to become effective, but your linked package will automatically begin building.

Package page, build log and project monitor page

Next it is time to explore the Monitor page, the package detail page and the build log. Just Click on the links and explore the webinterface.

I recommend starting with your home project's top level 'overview' page - click on the Overview tab and you may see something like this:

This page has shown that some builds for some packages failed to complete successfully. Let's go look at the package itself. Click on the 'Packages' tab and then on 'bash'. You'll see the package detail page:

What failed? You can click on failed for either of the packages builds to inspect the build log. Below are the top of that page:

... and the bottom of the build log page:

The comment at the end hints that the package probably built OK and rpms were produced, but that there were style violations in the packaging tests mandated by the MeeGo project. In fact, all that is confirmed some lines above when the rpmlint test is started:

Return using your browser back button to your home project Overview page. Click on the Monitor tab, and you'll see something like:

So you can monitor something as it is building, let's add the acl package too. Click on the Packages tab. Then, click Link package from another project. Enter MeeGo:1.0:Core as the original project and acl as the name of package, and click Create Link. Return to your home project. Click on the Monitor tab and it will look like:

Feel free to inspect the logs as it each version of the package is building.

Repository Output: Built Packages

To find the RPMs you built, go to your home project page and click Repositories. From there click on the repository name. For example, Trunk:

And from there, click on Go to download repository. You'll see something like this:

Your rpms can be found in the subdirectories, and the .repo file is suitable for use with zypper, yum or other repository-friendly package management tools.

Summary

We've had a look at adding a linked package. We watched it build automatically, pulling in prerequisite source packages, and inspected the logs. We also located the final output: built package files: source and binary rpm files. In our next step, we'll show how you can set up your own first package using the web interface -- continue at Part 3.