Dongsu Park [Fri, 17 Jan 2014 13:47:17 +0000 (14:47 +0100)]
extract_storage: dist of ANDBD must be not dev_feature* but pre-staging
A yet another bug on building a kernel image from a feature branch.
So far profitbricks-linux-image-storage has been built successfully.
However, its subtask building profitbricks-andbd-modules-storage
has always failed.
Its reason was apt sources list having enabled only dev-repository,
where ANDBD modules are normally not built at all. This could result
in an error case, where installation process of ANDBD module package
tries to find a bogus kernel version, such as 2.6.32.
Even though there would exist any feature branch of ANDBD that matches
exactly with the name of feature branch of linux-storage, we could not
have any way to determine at all, whether the two feature branches
should match with each other. There's no point of using $TARGET_NAME
for configuring distribution of the ANDBD module package.
Therefore the solution is to always add a pre-staging repository
to apt sources list. Then linux-storage from a feature branch can be
installed with andbd-modules from the pre-staging (develop) branch.
Dongsu Park [Tue, 14 Jan 2014 12:16:18 +0000 (13:16 +0100)]
extract_storage: support for a new format of DISTRIBUTION variable
since several months, this script has not been able to support for
building feature branch kernels any more. It looks like $DISTRIBUTION
is now being given with a format of "dev_feature_$branchname".
To fix errors of Jenkins job dev-feature_extract-storage-kernel-and
-modules, let's make it support for dev_feature_$branchname" too.
Benjamin Drung [Mon, 9 Dec 2013 08:28:52 +0000 (09:28 +0100)]
lib/git_buildpackage.py: Fix build failure caused by calling clean target.
We do want to let dpkg-buildpackage call the clean target, because
it can fail if we do not have all build dependencies installed.
Instead we make sure that the git checkout is clean and the clean
target will be called inside the pbuilder chroot (after the
installation of the build dependencies).
Fabian Holler [Thu, 22 Aug 2013 09:34:05 +0000 (11:34 +0200)]
add script to create liveboot kernel debug archives
The script downloads the sources and debug symbols for ethoip6 and the
profitbricks-linux-pserver kernel that are installed on a liveboot.
From the extracted files a tar.xz archive is created that contains
everything what is needed to debug kernel oopses.
The archives is stored at /srv/liveboot/debug_archives on the jenkins
build server
Dongsu Park [Thu, 22 Aug 2013 11:43:43 +0000 (13:43 +0200)]
extract_storage: fix a bug on selecting modules directory name
In the sub-script, which is externally invoked by this script,
there was a little bug like "cd /lib/modules/*storage/".
This has been working if there's only 1 directory under /lib/modules.
But after upgrading kernel 3.4.23 to 3.4.51, there could be 2 different
directories, because ANDBD package could be possibly depending on
the older version.
To avoid such situations, set the kernel modules directory just the
same as its kernel version.
Dongsu Park [Thu, 22 Aug 2013 11:43:43 +0000 (13:43 +0200)]
extract_storage: fix a bug on selecting modules directory name
In the sub-script, which is externally invoked by this script,
there was a little bug like "cd /lib/modules/*storage/".
This has been working if there's only 1 directory under /lib/modules.
But after upgrading kernel 3.4.23 to 3.4.51, there could be 2 different
directories, because ANDBD package could be possibly depending on
the older version.
To avoid such situations, set the kernel modules directory just the
same as its kernel version.
Mathias Klette [Mon, 24 Jun 2013 11:42:33 +0000 (13:42 +0200)]
debian_buid.py: reset new_tag when build with autoincrement
let's assume this:
- user changes files but not version in changelog and commits
- call_jenkins accepts and triggers build
- debian_build.py figures out version / tag to create from changelog
- debian_build.py will incrase version number and pushes new HEAD back to origin
- call_jenkins will not push trigger another jenkins call
- debian_build.py will build with the new version
- tagging must happen when build was successful BUT with the new version number
instead of the one gathered in the very first beginning of the script