Skip to content

Workflow file for this run

name: Build Nextcloud from upstream daily and push to AUR latest release
on:
push:
branches: ["main"]
pull_request:
branches: ["main"]
workflow_dispatch:
jobs:
Update-AppImage:
runs-on: ubuntu-latest
container: archlinux:latest
steps:
- name: Checkout codebase
uses: actions/checkout@v3
# TODO: Build automatically inside an ArchLinux Chroot
- name: Pacman key init, upgrade, update, install deps
run: pacman-key --init && pacman -Syu --noconfirm
- name: Install all latest dependencies in container
run: |
pacman -S --noconfirm zlib curl p7zip wget bash base-devel git pacman-contrib
- name: Create a user for makepkg usage
run: |
chmod a+rwx ./update.sh
chmod a+rwx -R .
useradd makepkg-user
cat /etc/passwd
#- name: Git clone from AUR
# run: git clone https://aur.archlinux.org/nextcloud-client-appimage-daily.git
# INSERT step to setup git config from ENV variable containing secrets????
# TODO: Find if that's a good solution ^ or to avoid in terms of security
# Read a lot of documentation and blogs...
# TODO: Forced to use chroot because we are the root user in the container
- name: Build latest update from upstream
run: |
su makepkg-user
whoami
chmod +x ./update.sh
ls
su makepkg-user -c "bash ./update.sh"