feat: add pre-install script execution

Signed-off-by: Maximilian Bösing <[email protected]>

Author: boesing

README.md

@@ -65,13 +65,20 @@ jobs:
 Some packages may require additional setup steps: setting up a web server to test an HTTP client, seeding a database or cache service, etc.
 Other times, you may want to do additional reporting, particularly if the QA command failed.
 
-To enable this, you may create one or both of the following files in your package:
+To enable this, you may create one or more of the following files in your package:
 
-- `.laminas-ci/pre-run.sh`
+- `.laminas-ci/pre-install.sh`
+- `.laminas-ci/pre-run.sh` 
 - `.laminas-ci/post-run.sh`
 
 (Note: the files MUST be executable to be consumed!)
 
+These runs immediately before any other command is being executed in this action.
+The `.laminas-ci/pre-install.sh` command will receive the following arguments:
+- `$1`: the user the QA command will run under
+- `$2`: the WORKDIR path
+- `$3`: the `$JOB` passed to the entrypoint (see above)
+
 These run immediately before and after the QA command, respectively.
 The `.laminas-ci/pre-run.sh` command will receive the following arguments:
 

entrypoint.sh

@@ -157,6 +157,12 @@ fi
 echo "Marking PHP ${PHP} as configured default"
 update-alternatives --set php /usr/bin/php${PHP}
 
+# Is there a pre-install script available?
+if [ -x ".laminas-ci/pre-install.sh" ];then
+    echo "Executing pre-install commands from .laminas-ci/pre-install.sh"
+    ./.laminas-ci/pre-install.sh testuser "${PWD}" "${JOB}"
+fi
+
 echo "PHP version: $(php --version)"
 echo "Installed extensions:"
 php -m