Update build actions to avoid rate limits on upload artifacts

Author: josmartin

.github/workflows/release-all-debian.yaml

@@ -6,8 +6,6 @@ name: "release-all-debian"
 # ensure all artifacts are up-to-date with security and other patches to these distributions
 on:
   workflow_dispatch:
-  schedule:
-    - cron:  '0 0 1 * *'  
 
 # Wish I could use a matrix strategy here - tried to and discovered that there are limitations
 #     The strategy property is not supported in any job that calls a reusable workflow.

.github/workflows/release-all-ubuntu.yaml

@@ -0,0 +1,26 @@
+# Copyright 2021-2022 The MathWorks, Inc.
+---
+name: "release-all-ubuntu"
+
+# Build and release all artifacts is either triggered manually or on the first day of the month to 
+# ensure all artifacts are up-to-date with security and other patches to these distributions
+on:
+  workflow_dispatch:
+  schedule:
+    - cron:  '0 3 1 * *'  
+
+# Wish I could use a matrix strategy here - tried to and discovered that there are limitations
+#     The strategy property is not supported in any job that calls a reusable workflow.
+# from https://docs.github.com/en/actions/using-workflows/reusing-workflows#limitations
+jobs:
+  build-ubuntu-bionic:
+    uses: ./.github/workflows/build-glibc-and-release.yaml
+    with: 
+      dist-base: ubuntu
+      dist-tag: bionic
+
+  build-ubuntu-focal:
+    uses: ./.github/workflows/build-glibc-and-release.yaml
+    with: 
+      dist-base: ubuntu
+      dist-tag: focal

.github/workflows/release-debian-bullseye.yaml

@@ -0,0 +1,20 @@
+# Copyright 2021-2022 The MathWorks, Inc.
+---
+name: "release-debian-bullseye"
+
+# Build and release all artifacts is either triggered manually or on the first day of the month to 
+# ensure all artifacts are up-to-date with security and other patches to these distributions
+on:
+  workflow_dispatch:
+  schedule:
+    - cron:  '0 5 1 * *'  
+
+# Wish I could use a matrix strategy here - tried to and discovered that there are limitations
+#     The strategy property is not supported in any job that calls a reusable workflow.
+# from https://docs.github.com/en/actions/using-workflows/reusing-workflows#limitations
+jobs:
+  build-debian-bullseye:
+    uses: ./.github/workflows/build-glibc-and-release.yaml
+    with: 
+      dist-base: debian
+      dist-tag: bullseye

.github/workflows/release-debian-buster.yaml

@@ -0,0 +1,20 @@
+# Copyright 2021-2022 The MathWorks, Inc.
+---
+name: "release-debian-buster"
+
+# Build and release all artifacts is either triggered manually or on the first day of the month to 
+# ensure all artifacts are up-to-date with security and other patches to these distributions
+on:
+  workflow_dispatch:
+  schedule:
+    - cron:  '0 7 1 * *'  
+
+# Wish I could use a matrix strategy here - tried to and discovered that there are limitations
+#     The strategy property is not supported in any job that calls a reusable workflow.
+# from https://docs.github.com/en/actions/using-workflows/reusing-workflows#limitations
+jobs:
+  build-debian-buster:
+    uses: ./.github/workflows/build-glibc-and-release.yaml
+    with: 
+      dist-base: debian
+      dist-tag: buster