You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
186526 3306ce22c3
4 months ago
balena-etcher@246ab3d254 Update 4 months ago
google-chrome@95891c4a41 Update 4 months ago
guestfs-tools@198fed0e72 Update 4 months ago
srv-bin@e738464992 Update 4 months ago
ttyd@b44bd42099 Update 4 months ago
wps-office@4cb1d4bfcf Update 4 months ago
.drone.yml Update 4 months ago
.drone.yml.backup Add ananicy 1 year ago
.gitattributes Add ananicy 1 year ago
.gitmodules Update 4 months ago Update 4 months ago Update 4 months ago
buildjob.txt Update 4 months ago
packages.txt Update 4 months ago

Automated AUR Build Pipeline with Drone CI

This Repository wants to achieve a simple building of packages with Drone CI, Docker and Nexus.

Build Status



  1. Fork the Repository
  2. Connect Drone CI with your Git Repository and activate it
  3. Clone your Repository
  4. Remove ananicy package from the repository (it is just a example package)
  5. Add the packages you want
git submodule add timeshift
  1. Register the Packages you want in the packages.txt. You can add commands that should be executed first, before building the package with an ^. So for example if you want to install nano before installing timeshift register the package like this in the packages.txt (every package in a single line).
timeshift^pacman -Sy --noconfirm nano
  1. Change the variables in the For example the volumepath describes where the shared volume for all pipeline steps is mounted. This is important because this i later the name you add into your pamac.conf. Also change the apiurl to the API URL of your Nexus Instance.

  2. Change buildjob.txt to your needs. So for example change the environemt variables to your Nexus instance and change the mountpoint in the commands to your repo name.

  3. run and push the changes to your repository.

  4. Change timeout of the Drone Repository, because it may take longer than 60 minutes to build your packages.

  5. Add anonymous role in your Nexus Repository so your raw Nexus Repository can be read by anybody.

The pipeline should build your packages and pushs the packages to your Nexus Raw Repository.