Hi,
I would like to run some kind of continuous integration of my AUR
packages. The goal is to know when a package I maintain fails to build
because either:
1/ its dependencies have been updated (new API, new incompatible version
of GCC, ...)
2/ for -git packages, changes made upstream broke
I actually have a Jenkins setup for my packages that does almost exactly
that, I have a job generator build that I give an AUR package name to and
that's all the config for new packages, and it builds them in a docker
container.
You can obviously set up dependencies between the jobs to build in or
Hi,
On Thu, Feb 18, 2016 at 12:25:53PM +, Justin Dray wrote:
> I actually have a Jenkins setup for my packages that does almost exactly
> that, I have a job generator build that I give an AUR package name to and
> that's all the config for new packages, and it builds them in a docker
> contain
On Thu, 18 Feb 2016 12:51:19 +0100
Baptiste Jonglez wrote:
> Hi,
>
> The scripts in devtools [1] look like they should work just fine to
> automate these kind of builds. After all, they are used to build the
> official Archlinux packages.
>
> However, I found that the build scripts do not reall
I was using the chroot tools for a year and a half or so before that, but
had some issues occasionally with things like updating it, or using package
caches inside the chroot, or other various things. I do still have the
shell script I used at the time, it was called by jenkins and cloned a
chroot
