Update to Brussels 0.2.0 (#2300)

This PR updates Brussels to 0.2.0 (oxidecomputer/brussels#7) and makes
the necessary changes to be compatible with it.

This release of Brussels doesn't change the manual steps needed to
publish a release (it still only does the tagging and initial build),
and instead contains these changes:

* Records the commit we are releasing in the manifest, so that the rest
of the (future) release process will be able to rely on it.
* Rather than hardcoding the release groups in the Brussels source code,
there is now a file in the Hubris repository, `brussels.toml`. The fine
defines both how to create the tag and the list of boards to release.

Along with the update I changed the GitHub release creation code to use
the commit we are actually releasing, instead of releasing the latest
commit on `main` unconditionally. This will prevent cases like the
all-sp-v1.0.49 tag pointing to the wrong commit.

Author: pietroalbini

.github/workflows/release.yml

@@ -30,7 +30,7 @@ jobs:
         name: Download Brussels
         run: |
           if [[ "${BRUSSELS_RUN_ID}" == "" ]]; then
-            gh release download -R oxidecomputer/brussels -p brussels v0.1.1
+            gh release download -R oxidecomputer/brussels -p brussels v0.2.0
           else
             gh run download "${BRUSSELS_RUN_ID}" -R oxidecomputer/brussels -n prebuilt-binary
           fi
@@ -42,7 +42,7 @@ jobs:
 
       - id: init
         name: Initialize the release
-        run: brussels init $group >> brussels-manifest.json
+        run: brussels init "$group" HEAD >brussels-manifest.json
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           group: ${{ github.event.inputs.group }}
@@ -83,6 +83,7 @@ jobs:
     - name: Publish the release
       uses: softprops/action-gh-release@v1
       with:
+        target_commitish: ${{ needs.init.outputs.commit_sha1 }}
         tag_name: ${{ needs.init.outputs.tag_name }}
         name: "${{ github.event.inputs.group }} release"
         fail_on_unmatched_files: true

brussels.toml

@@ -0,0 +1,50 @@
+# Configuration for oxidecomputer/brussels, the SP and Rot release tool. 
+#
+# Each group will publish all boards within it as part of a single tag and GitHub release, creating
+# the tag according to the defined rules. The hubris-app-dirs key defines the list of directores
+# containing the Hubris apps CI will build as part of the release.
+
+version = 1 # Schema version of this file.
+
+[groups.all-sp]
+tag-bump = "patch"
+tag-prefix = "all-sp-v"
+hubris-app-dirs = [
+    "app/sidecar/",
+    "app/gimlet/",
+    "app/psc/",
+    "app/cosmo/",
+]
+
+[groups.all-sp.boards]
+gimlet-b = {}
+gimlet-b-lab = {}
+gimlet-c = {}
+gimlet-c-lab = {}
+gimlet-d = {}
+gimlet-d-lab = {}
+gimlet-e = {}
+gimlet-e-lab = {}
+gimlet-f = {}
+gimlet-f-lab = {}
+psc-b = {}
+psc-c = {}
+sidecar-b = {}
+sidecar-b-lab = {}
+sidecar-c = {}
+sidecar-c-lab = {}
+sidecar-d = {}
+sidecar-d-lab = {}
+cosmo-a = {}
+cosmo-a-lab = {}
+cosmo-b = {}
+cosmo-b-lab = {}
+
+[groups.rot]
+tag-bump = "patch"
+tag-prefix = "oxide-rot-1-v"
+hubris-app-dirs = ["app/oxide-rot-1/"]
+
+[groups.rot.boards]
+oxide-rot-1 = { images = ["a", "b"] }
+oxide-rot-1-selfsigned = { images = ["a", "b"] }