(→Package page, build log and project monitor page: Update for new webui, add more examples, handle failed package, add 'acl' example too.)
m (→Package page, build log and project monitor page: split top of log page from bottom)
|Line 85:||Line 85:|
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.
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.
Enter your "Home Project" 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:
Right below packages, there's "Link Package from other Project" .
Open that page and enter for
Name of original project: MeeGo:1.0:Core
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.
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.
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 and bottom of that page:
The comment at the end explains that on some of the packaging didn't look right. It 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. From your phome project click on the Monitor tab, and you'll see something like:
At your option, if you want to catch something building, , 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 may look like:
From your phome project click on the Monitor tab, and you'll see something like: