arch-travis

arch-travis provides a chroot based Arch Linux build environment for Travis-CI builds. It supports a very simple (and limited) configuration based on .travis.yml.

Example:

sudo: required

arch:
  repos:
    - papyros=http://dash.papyros.io/repos/$repo/$arch
  packages:
    # pacman packages
    - python
    - perl
    # aur packages
    - go-git
    # packages from papyros repo
    - papyros-shell
  script:
    - "./build_script.sh"

script:
  - "curl -s https://raw.githubusercontent.com/mikkeloscar/arch-travis/master/arch-travis.sh | bash"

arch.repos defines a list of custom repositories.

arch.packages defines a list of packages (from official repos or AUR) to be installed before running the build.

arch.script defines a list of scripts to run as part of the build. Anything defined in the arch.script list will run from the base of the repository as a normal user called travis. sudo is available as well as any packages installed in the setup. The path of the build dir (or repository base), is stored in the TRAVIS_BUILD_DIR environment variable inside the chroot.

script defines the scripts to be run by travis, this is where arch-travis is initialized.

Default packages and repositories

By default the following packages are installed and usable from within the build environment.

• base-devel (group)
• git
• cower
• pacaur

The following repositories are enabled by default.

• core
• extra
• community
• multilib

It is possible to use custom respositories by adding them to the arch.repos section of .travis.yml using the following format:

arch:
  repos:
    - repo-name=http://repo.com/path

The first repository in the list will be added first in pacman.conf and all custom repositories will be added before the default repositories.

Limitations/tradeoffs

• Increases build time with about 1-3 min.
• Doesn't work on travis container-based infrastructure because sudo is required.
• Limited configuration.
• Doesn't include base group packages. If you need anything from base just add it to the arch.packages list in .travis.yml.

Advanced configuration

Apart from the basic arch entry in .travis.yml it is also possible to define some environment variables in order to control the chroot setup.

The following variables are available:

ARCH_TRAVIS_CHROOT name of the folder containing the chroot. (default is root.x86_64).

ARCH_TRAVIS_MIRRORS Comma separated list of Arch Linux mirrors used by pacman. See list of available mirrors here. Omit the /$repo/os/$arch part of the mirrors when defining this variable.

Note some https mirrors are not supported due to #4757.

ARCH_TRAVIS_CLEAN_CHROOT by default the chroot archive and chroot folder is left in $TRAVIS_BUILD_DIR, if you don't want this, then you can make arch-travis remove them by enabling ARCH_TRAVIS_CLEAN_CHROOT.

ARCH_TRAVIS_ARCH Set the default architecture to use in the chroot. Valid values are x86_64 (default) and i686.

ARCH_TRAVIS_CONFIRM_YES when set, this configures arch-travis to always answer yes when installing packages. This is needed if you want to overwrite a default package e.g. pacman-git where pacaur will prompt pacman-git and pacman are in conflict. Remove pacman? [y/N].

To use, just add the variable to the env section of .travis.yml.

env:
  - ARCH_TRAVIS_CHROOT="custom_root" ARCH_TRAVIS_CLEAN_CHROOT=1

clang support

The default compiler available in the chroot is gcc, if you want to use clang instead just add the following to .travis.yml and arch-travis will export CC=clang in your build:

language: c

compiler: clang

Projects using arch-travis

• sway

LICENSE

Copyright (C) 2016-2017 Mikkel Oscar Lyderik Larsen

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.