Prevent manual re-trigger of release pipelines

.buildkite/release-builds.yml

@@ -11,10 +11,18 @@ steps:
     command: ".buildkite/commands/release-build-wordpress.sh $BETA_RELEASE"
     plugins: [$CI_TOOLKIT_PLUGIN]
     notify:
-    - slack: "#build-and-ship"
+      - slack: "#build-and-ship"
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false
 
   - label: ":jetpack: :testflight: Jetpack Release Build (App Store Connect)"
     command: ".buildkite/commands/release-build-jetpack.sh"
     plugins: [$CI_TOOLKIT_PLUGIN]
     notify:
     - slack: "#build-and-ship"
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false

.buildkite/release-pipelines/code-freeze.yml

@@ -18,3 +18,7 @@ steps:
 
       echo '--- :shipit: Run code freeze'
       bundle exec fastlane code_freeze skip_confirm:true
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false

.buildkite/release-pipelines/complete-code-freeze.yml

@@ -9,9 +9,17 @@ steps:
   - label: Complete Code Freeze
     key: complete_code_freeze
     plugins: [$CI_TOOLKIT_PLUGIN]
-    command: ".buildkite/commands/complete-code-freeze.sh $RELEASE_VERSION"
+    command: .buildkite/commands/complete-code-freeze.sh $RELEASE_VERSION
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false
 
   - label: Log Outdated Pods
     depends_on: complete_code_freeze
     plugins: [$CI_TOOLKIT_PLUGIN]
-    command: ".buildkite/commands/log-outdated-pods.sh $RELEASE_VERSION"
+    command: .buildkite/commands/log-outdated-pods.sh $RELEASE_VERSION
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false

.buildkite/release-pipelines/finalize-hotfix.yml

@@ -7,4 +7,8 @@ steps:
         queue: mac
     env:
       IMAGE_ID: $IMAGE_ID
-    command: ".buildkite/commands/finalize-hotfix.sh $VERSION"
+    command: .buildkite/commands/finalize-hotfix.sh $VERSION
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false

.buildkite/release-pipelines/finalize-release.yml

@@ -7,4 +7,8 @@ steps:
         queue: mac
     env:
       IMAGE_ID: $IMAGE_ID
-    command: ".buildkite/commands/finalize-release.sh $RELEASE_VERSION"
+    command: .buildkite/commands/finalize-release.sh $RELEASE_VERSION
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false

.buildkite/release-pipelines/new-beta-release.yml

@@ -19,3 +19,7 @@ steps:
 
       echo '--- :shipit: Deploy new beta'
       bundle exec fastlane new_beta_release skip_confirm:true
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false

.buildkite/release-pipelines/new-hotfix.yml

@@ -19,3 +19,7 @@ steps:
 
       echo '--- :shipit: Start new hotfix'
       bundle exec fastlane new_hotfix_release skip_confirm:true version:"$VERSION"
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false

.buildkite/release-pipelines/update-app-store-strings.yml

@@ -18,3 +18,7 @@ steps:
 
       echo '--- :shipit: Update relaese notes and other App Store metadata'
       bundle exec fastlane update_appstore_strings skip_confirm:true
+    retry:
+      manual:
+        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
+        allowed: false