Feature tests as GitHub actions #39

	---
	name: feature tests

	on:
	pull_request:
	branches: [master]

	env:
	SOURCE: /usr/src/rmt-server
	SCC_USERNAME: ${{ secrets.SCC_USERNAME }}
	SCC_PASSWORD: ${{ secrets.SCC_PASSWORD }}
	SYSTEM_UUID: ${{ secrets.SYSTEM_UUID }}

	# Within containters Github Actions does create a bridged network exposing
	# the service named after its label
	MYSQL_HOST: mysql

	jobs:
	feature-tests:
	runs-on: ubuntu-latest
	defaults:
	run:
	working-directory: /usr/src/rmt-server
	container:
	image: registry.opensuse.org/systemsmanagement/scc/containers/15.5/rmt-ci-container:latest
	options: --user root
	services:
	mysql:
	image: mysql:5.7
	env:
	MYSQL_DATABASE: rmt_features
	MYSQL_USER: rmt
	MYSQL_PASSWORD: rmt
	MYSQL_ROOT_PASSWORD: root
	ports:
	- 3306:3306
	options: >-
	--health-cmd="mysqladmin ping"
	--health-interval=10s
	--health-timeout=5s
	--health-retries=3
	steps:
	- uses: actions/checkout@v4
	with:
	fetch-depth: 0

	- name: move source to /usr/src/rmt-server
	run: \|
	[ -d $SOURCE ] && rm -r $SOURCE
	cp -r $GITHUB_WORKSPACE $SOURCE

	- name: build RPM package
	run: \|
	bash ci/rmt-build-rpm

	- name: gather RPM build artifacts
	uses: actions/upload-artifact@v4
	with:
	name: rmt-server-rpms
	path: ${{ env.SOURCE }}/tmp/artifacts/*.rpm

	- name: configure RMT to run feature tests
	run: \|
	bash ci/rmt-configure

	# Yes, yes we could use setup-ruby for this BUT:
	# it will require to make local ruby available within
	# our custom container. This here is more easy and clean!
	- name: install test dependencies
	run: \|
	bundle install

	- name: run feature tests
	run: \|
	bash ci/rmt-run-feature-tests

Provide feedback