Test github actions

.github/workflows/build_installation_package.yaml

@@ -0,0 +1,19 @@
+name: Build DQMGUI Installation Package
+
+on: [push]
+
+jobs:
+  build_and_test:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+      - name: npm install, build, and test
+        run: |
+          bash download_dependencies.sh
+      - name: Archive package artifact
+        uses: actions/upload-artifact@v3
+        with:
+          name: dist-without-markdown
+          path: |
+            .

README.md

@@ -1,8 +1,11 @@
 # [Legacy] DQMGUI Deployment
 
-This repository contains all the requirements for deploying the [Legacy] [DQMGUI](https://github.com/cms-DQM/dqmgui_prod) on a Red Hat Enterprise Linux 8 machine, with Python3.6 for the needs of moving DQM production to new machines.
+This repository contains all the requirements for deploying the [Legacy] [DQMGUI](https://github.com/cms-DQM/dqmgui_prod) on a Red Hat Enterprise Linux 8 machine, with Python3.8 for the needs of moving DQM production to new machines.
 
-It aims to replace the existing one (`Deploy`), found in [`dmwm/deployment`](https://github.com/dmwm/deployment/tree/master/Deploy), which only targets OS up to SLC7. The main difference is that the `Deploy` script relies on pre-built libraries and executables, found on `cmsrep.cern.ch`, while this script downloads and builds all requirements from source (hence takes longer to deploy).
+It aims to replace the existing one (`Deploy`), found in [`dmwm/deployment`](https://github.com/dmwm/deployment/tree/master/Deploy), which only targets OS up to SLC7. The main difference is that the `Deploy` script relies on pre-built libraries and executables, found on `cmsrep.cern.ch`, while the method we implement in this repository depends on two steps:
+
+1. Download all the external resources needed (e.g. python packages from PyPI, github repositories) and compress them.
+2. Copy the archives to the P5 machine and extract, then build from source (hence takes longer to deploy).
 
 > **Warning**
 > This deployment script should *not* be run as a sudo user.
@@ -13,7 +16,7 @@ It aims to replace the existing one (`Deploy`), found in [`dmwm/deployment`](htt
 - `sudo` permissions:
   - To install the system-wide packages (listed below).
 <!--  - To create a soft link in `/usr/lib64`. -->
-- Python 3.6
+- Python 3.8
 - Git
 - Access to PyPI for downloading python packages.
 - Access to GitHub for cloning several external dependencies.
@@ -161,7 +164,7 @@ Below is a list of the values that you will most probably need to change to cust
 
 ## [Debug] Selectively run parts of the installation script
 
-The script is split into steps (see: `installation_steps`), which can all be toggled off or on by arguments when running the script.
+The script is split into steps (see the `installation_steps` array declared in the `deploy_dqmgui.sh` script), which can all be toggled off or on by arguments when running the script.
 
 The flags are named by concatenating `do_` with the name of the step, so, for example, `do_check_dependencies` or `do_install_rotoglup`.
 
@@ -176,3 +179,7 @@ A useful combination that can be used when you've already installed and built al
 ```bash
 bash deploy_dqmgui.sh do_preliminary_checks=0 do_check_dependencies=0 do_create_directories=1 do_install_boost_gil=0 do_install_gil_numeric=0 do_install_rotoglup=0 do_install_classlib=0 do_compile_classlib=0 do_install_dmwm=0 do_install_root=0 do_compile_root=0 do_install_dqmgui=0 do_compile_dqmgui=1 do_install_yui=0 do_install_extjs=0 do_install_d3=0 do_install_jsroot=0
 ```
+
+## Notes
+
+- We're not using the RHEL8 `root` package, due to the fact that they are built for python3.6, hence we need to build it with python3.8.