6 Commits

Author	SHA1	Message	Date
Fabian Koller	884d85de56	Fix GitHub actions ... Follow-up to #630. The check for the target git sha can does not work in the molecule step. Instead expose the sha through an env variable in GitHub actions.	2021-02-26 19:39:44 +01:00
Fabian Koller	bd41efe868	Use local HEAD hash as installation target ... GitHub actions' GITHUB_SHA provides unexpected hashes for manually re-run pipelines. Instead rely on the commit as seen from the current git history.	2021-02-25 06:59:27 +01:00
Fabian Koller	1ba1b3a946	Switch CI target to sha instead of ref	2021-01-31 11:28:54 +01:00
Fabian Koller	2fd8b4d56b	Simplify molecule tests ... "Upgrade" path includes multiple paths anyway: - installing the latest official release package - builing the current PR from source - upgrading between the two versions	2021-01-23 22:55:46 +01:00
Fabian Koller	e1d903a6df	molecule scenario to test upgrading from releases ... Provide a separate scenario to install the last release, then update to the current one. Also includes improved deployment verification (check if uploading a .txt through the API works).	2021-01-18 22:51:40 +01:00
Fabian Koller	c9d90d8ae0	Add molecule test for role ... Only test default installation with jbig2enc and sqlite	2020-12-28 11:28:19 +01:00