Make a single package

.github/workflows/build_installation_package.yaml

@@ -3,7 +3,7 @@ name: Build DQMGUI Installation Package
 on: [push]
 
 jobs:
-  build_and_test:
+  build_and_upload:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout repository
@@ -13,9 +13,12 @@ jobs:
           $(which python3) --version
           sudo apt update && sudo apt install -y libcurl4-gnutls-dev
           bash download_dependencies.sh
+          rm -rf .git
+          mkdir -p /tmp/dqmgui
+          tar -cf /tmp/dqmgui/dqmgui_installation_package.tar.gz . -I "gzip --best"
       - name: Archive package artifact
         uses: actions/upload-artifact@v3
         with:
-          name: dist-without-markdown
+          name: dqmgui-installation-package
           path: |
-            .
+            /tmp/dqmgui/dqmgui_installation_package.tar.gz

README.md

@@ -1,5 +1,7 @@
 # [Legacy] DQMGUI Deployment
 
+[![Build DQMGUI Installation Package](https://github.com/cms-DQM/dqmgui_prod_deployment/actions/workflows/build_installation_package.yaml/badge.svg)](https://github.com/cms-DQM/dqmgui_prod_deployment/actions/workflows/build_installation_package.yaml)
+
 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 the method we implement in this repository depends on two steps: