Added info about manually triggering CI builds. Added option to skip …

…ci builds

skip-ci

.github/workflows/editor-only.yml

@@ -18,6 +18,7 @@ env:
 
 jobs:
   build-and-notarize-editor:
+    if: !contains(github.event.head_commit.message, 'skip-ci')
     runs-on: macOS-latest
     steps: [
       { name: 'Checkout', uses: actions/checkout@v2 },

.github/workflows/main-ci.yml

@@ -22,6 +22,7 @@ env:
 jobs:
 # ---- BUILD ENGINE VERSIONS ------------------
   build-engine-windows:
+    if: !contains(github.event.head_commit.message, 'skip-ci')
     strategy:
       matrix:
         platform: [win32, x86_64-win32]
@@ -39,6 +40,7 @@ jobs:
       }]
 
   build-engine-macos:
+    if: !contains(github.event.head_commit.message, 'skip-ci')
     strategy:
       matrix:
         platform: [x86_64-darwin]
@@ -55,6 +57,7 @@ jobs:
       }]
 
   build-engine-ios:
+    if: !contains(github.event.head_commit.message, 'skip-ci')
     strategy:
       matrix:
         platform: [armv7-darwin, arm64-darwin, x86_64-ios]
@@ -71,6 +74,7 @@ jobs:
       }]
 
   build-engine-web:
+    if: !contains(github.event.head_commit.message, 'skip-ci')
     strategy:
       matrix:
         platform: [js-web, wasm-web]
@@ -87,6 +91,7 @@ jobs:
       }]
 
   build-engine-android:
+    if: !contains(github.event.head_commit.message, 'skip-ci')
     strategy:
       matrix:
         platform: [armv7-android, arm64-android]
@@ -103,6 +108,7 @@ jobs:
       }]
 
   build-engine-linux:
+    if: !contains(github.event.head_commit.message, 'skip-ci')
     strategy:
       matrix:
         platform: [x86_64-linux]

README_CI.md

@@ -9,3 +9,30 @@ The Defold CI jobs are divided into three main categories, each represented by a
 * [Engine Nightly](/.github/workflows/engine-nightly.yml) - Runs Address Sanitizer (ASAN) and Valgrind nightly to detect leaks and other problems. This is done on the `dev` branch.
 
 The workflow files listed above sets up the jobs and distributes them to multiple workers to build, test and release the engine and/or editor. The bulk of the work is done in the [ci.py](/ci/ci.py) script.
+
+## How to trigger builds manually
+
+You can use the `ci/trigger-build.py` script to manually trigger a build using the `Main` workflow:
+
+```
+./ci/trigger-build.py --token=<personal_access_token> --branch=9a32ac5e9513e8aff669cf4cbe4334aeec2fbf8e --skip-engine --skip-sdk --skip-bob
+```
+
+Available options are:
+
+```
+$ ./ci/trigger-build.py --help                                                                   
+usage: trigger-build.py [-h] [--token TOKEN] [--action ACTION]
+                        [--branch BRANCH] [--skip-engine] [--skip-sdk]
+                        [--skip-bob] [--skip-editor]
+
+optional arguments:
+  -h, --help       show this help message and exit
+  --token TOKEN    GitHub API personal access token
+  --action ACTION  The trigger action
+  --branch BRANCH  The branch to build
+  --skip-engine    Skip building the engine
+  --skip-sdk       Skip building the Defold SDK
+  --skip-bob       Skip building bob
+  --skip-editor    Skip building the editor
+```