The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)


Mer Delivery System

From Mer Wiki
(Difference between revisions)
Jump to: navigation, search
m (FakeOBS moved to Mer Delivery System: Rename FakeOBS to Mer Delivery System)
(WIP)
Line 1: Line 1:
To set up your own Mer build:
+
Mer provides the Mer Delivery System (MDS) to make it easy for vendors to track upstream Mer releases.
  
1. Install:
+
= Overview =
 +
 
 +
MDS is a small collection of tools that both supports distributing Mer
 +
binary releases and OBS build targets to vendors and accessing the
 +
local copy of the xrelease from a private vendor-managed OBS.
 +
 
 +
= Operations =
 +
 
 +
== MDS tools ==
 +
 
 +
=== Installation ===
 +
 
 +
The MDS is installed in the root of the data area which will store the
 +
Mer releases (several Gb). This may be a dedicated VM.
 +
 
 +
Ensure the system has the following installed:
  
 
* git
 
* git
Line 13: Line 28:
 
* cpio
 
* cpio
  
2. Get the release tools
+
Get the release tools
 
  git clone http://review.merproject.org/p/mer/release-tools
 
  git clone http://review.merproject.org/p/mer/release-tools
  
3. Build the tools
+
=== Update ===
Note: You might need to set rsync proxy:
+
export RSYNC_PROXY=proxy.company.com:8080
+
  
This will rsync all the package git repos and clone Core git and check it out
+
The tools are updated periodically - simply run
and make a mappings cache of git repos (will md5sum all sources)
+
git remote update
 +
to update and then
 +
git checkout vXXX
 +
to obtain the version required.
 +
 
 +
== Mer release(s) ==
 +
 
 +
=== Setup ===
 +
 
 +
This step will pull (using rsync) all the git repositories for the Mer
 +
packages (nb: this is a huge download).
 +
 
 +
It will then build a list of the packages, create a set of mappings
 +
and prepare the OBS event stream.
 +
 
 +
Finally the OBS projects are cloned and extracted ready for the API
 +
service.
 +
 
 +
Note: You might need to set rsync proxy:
 +
export RSYNC_PROXY=proxy.company.com:8080
  
 
  cd release-tools; make
 
  cd release-tools; make
  
4. Pull down the latest Mer release binaries
+
=== Update ===
  
make update  
+
An update simply requires:
  
5. Start the fakeobs server
+
cd release-tools; make update
 +
 
 +
This will...
 +
 
 +
Running this periodicall will rsync from the upstream project ensure
 +
that up-to-date changes are available.
 +
 
 +
== Setup an API sercvice for Mer releases ==
 +
 
 +
MDS runs a simple http server that emulates the OBS api for a static release.
 +
 
 +
To start this 'fake obs server' (hence the original name for the packages):
  
 
  python tools/fakeobs.py 8001 &
 
  python tools/fakeobs.py 8001 &
 +
  
 
6. Setup OBS locally on your build environment of choice:
 
6. Setup OBS locally on your build environment of choice:

Revision as of 21:36, 29 January 2012

Mer provides the Mer Delivery System (MDS) to make it easy for vendors to track upstream Mer releases.

Contents

Overview

MDS is a small collection of tools that both supports distributing Mer binary releases and OBS build targets to vendors and accessing the local copy of the xrelease from a private vendor-managed OBS.

Operations

MDS tools

Installation

The MDS is installed in the root of the data area which will store the Mer releases (several Gb). This may be a dedicated VM.

Ensure the system has the following installed:

Get the release tools

git clone http://review.merproject.org/p/mer/release-tools

Update

The tools are updated periodically - simply run

git remote update

to update and then

git checkout vXXX

to obtain the version required.

Mer release(s)

Setup

This step will pull (using rsync) all the git repositories for the Mer packages (nb: this is a huge download).

It will then build a list of the packages, create a set of mappings and prepare the OBS event stream.

Finally the OBS projects are cloned and extracted ready for the API service.

Note: You might need to set rsync proxy:

export RSYNC_PROXY=proxy.company.com:8080
cd release-tools; make

Update

An update simply requires:

cd release-tools; make update

This will...

Running this periodicall will rsync from the upstream project ensure that up-to-date changes are available.

Setup an API sercvice for Mer releases

MDS runs a simple http server that emulates the OBS api for a static release.

To start this 'fake obs server' (hence the original name for the packages):

python tools/fakeobs.py 8001 &


6. Setup OBS locally on your build environment of choice:

7. Add a remote link for your FakeOBS's server, port 8001, /public, http, not-https (see how)

8. Follow the rest of OBS Install until the end

9. Once your project is set-up, OBS should start building it automatically (use Status Monitor to track the progress)


Show up in #mer and poke Stskeeps if there's any questions

Personal tools