repoconf

Repo configuration repository for autobuild

Contains a configuration file that is used by repo to install things.

Installing

Installing repo on Ubuntu 14.04

sudo apt-get install openjdk-7-jdk
sudo apt-get install bison g++-multilib git gperf libxml2-utils make zlib1g-dev:i386 zip
mkdir ~/bin
PATH=~/bin:$PATH
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo

You will also need some dev dev tools to create packages and packge repos:

apt-get install dpkg-dev devscripts sbuild

NOTE: I have no idea what the actual install steps are, or if there are other deps. I am really just guessing and trying to provice docs b/c there are no docs.

Using Repo

Make a directory to install your repo in:

mkdir repodir

Change to working directory and use repo to install repoconf repo:

cd repodir repo init -u [email protected]:JioCloud/repoconf

The -b option can be used to select a branch to use from the repo:

cd repodir repo init -u [email protected]:bodepd/repoconf -b mytestbranch

Next sync the repo

repo sync

Now run the script that will generate the package:

pushd repodir
bash debian/sync-repo.sh build
popd

Now run sbuild (you may need to escalate to sudo privs)

sbuild -d trusty -A rjil-cicd_2014.2.179ubuntu1.dsc

When sbuild finsihes, it will generate a tons of debs into the top level dir.

create a new directory to serve as your package repo:

mkdir new_repo

copy all of the debs there:

cp *.deb new_repo

Now create the repo:

pushd new_repo
apt-ftparchive packages . > Packages
popd

And just for run, tar it up:

tar -cvzf new_repo.tgz new_repo

Now you are ready to do something with it!

Running from jenkins

In general, it makes the most sense to run repoconf from a jenkins job when you need to build out a set of custom packages.

Jenkins is advantageous because it can target a full build of repoconf against a preconfigured slave (since it may be difficult to have a machine that meets all of the requirements of a build slave). It may not be usable for everyone since I'm not sure if it can archive everyone's package repos at the same time.

The following script shows how override_packages.sh from puppet-rjil can be used to build out a new package repo from jenkins. Note: override_packages.sh assumes that the parameters repoconf_repo_source and/or repoconf_source_branch have been provided so that it knows how to download a specified branch of repoconf to build against.

#!/bin/bash
set -xe
git remote add update $puppet_modules_source_repo
git fetch update
git checkout update/$puppet_modules_source_branch
bash -x build_scripts/override_packages.sh

Note: the above code exists in the (pkg_test_build)[http://jiocloud.rustedhalo.com:8080/job/pkg_test_build/] job in jenkins. This build also kicks off a build afterwards that uses the override_repo param to launch a build using the created pacakges.

Configuring packages to install

The entire purpose of this package is to build packages and populate them into a repo.

This is accomplished by configuration split across two repos:

repoconf

Repoconf simply holds the file: default.xml which is used to specify upstream remotes that should be pulled in.

autobuild

One of the repos that repp pulls in from default.xml is called autobuild. This repo contains the build script debian/sync-repo.sh. It also seems to contain some other files that have some purpose that needs to be documented as well.

More information on autobuild can be found at: (https://github.com/JioCloud/jiocloud-docs/blob/master/build_system.md)