From 15a651455e305f5a402466b27dc88b7033ce1afc Mon Sep 17 00:00:00 2001
From: Michael Lynch <mtlynch@users.noreply.github.com>
Date: Wed, 30 Nov 2022 12:36:40 -0500
Subject: [PATCH] Build TinyPilot Debian package and install bundle outside the
 main branch (#1214)

This change adjusts filtering in CircleCI so that we build the TinyPilot
Debian package and install bundle even in non-main repo branches.

Uploading a bundle changes state on our update server, so we should only
do that in our main branch. But all the other steps are fine to run in
branches because it doesn't affect state outside of CI. It's often
useful to build packages or bundles in the branches if we want to test
something end-to-end.
---
 .circleci/config.yml | 13 +++----------
 1 file changed, 3 insertions(+), 10 deletions(-)

diff --git a/.circleci/config.yml b/.circleci/config.yml
index aedd47c06..40559c62e 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -209,28 +209,21 @@ workflows:
       - check_style
       - build_python
       - build_javascript
-      - build_debian_package:
-          filters:
-            branches:
-              only: master
+      - build_debian_package
       - lint_debian_package:
           requires:
             - build_debian_package
       - build_bundle:
           requires:
             - build_debian_package
-          filters:
-            branches:
-              only: master
       - verify_bundle:
           requires:
             - build_bundle
-          filters:
-            branches:
-              only: master
       - upload_bundle:
           requires:
             - verify_bundle
+          # Uploading a new bundle affects Gatekeeper's view of the latest
+          # bundle available, so we should only do this on master.
           filters:
             branches:
               only: master