You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Begin to adjust stats reader to new JSON Level List
- Fix CI/CD Pipeline not pulling our level repository (missing submodule init), update build steps
- Adjust feedback dialogue to better communicate the maximum score
- Add Bearer authentication to /metrics endpoint
- Update the Grafana examples to show an instance selector and display the client error metrics
Copy file name to clipboardExpand all lines: .github/workflows/deploy-image.yml
+32-14Lines changed: 32 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,21 @@
1
1
#
2
2
name: Create and publish a Docker image
3
3
4
-
# Configures this workflow to run every time a change is pushed to the branch called `main`.
4
+
# Configures this workflow to run every time a change is pushed to the branch called
5
+
# `main` or `dev`.
5
6
on:
6
7
push:
7
8
branches: ['main', 'dev']
8
9
tags: ['*']
9
10
10
-
# Defines two custom environment variables for the workflow. These are used for the Container registry domain, and a name for the Docker image that this workflow builds.
11
+
# Defines two custom environment variables for the workflow. These are used for the
12
+
# Container registry domain, and a name for the Docker image that this workflow builds.
11
13
env:
12
14
REGISTRY: ghcr.io
13
15
IMAGE_NAME: ${{ github.repository }}
14
16
15
-
# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
17
+
# There is a single job in this workflow. It's configured to run on the latest available
18
+
# version of Ubuntu.
16
19
jobs:
17
20
build-and-push-image:
18
21
runs-on: ubuntu-latest
@@ -25,21 +28,28 @@ jobs:
25
28
26
29
steps:
27
30
- name: Checkout repository
28
-
uses: actions/checkout@v4
31
+
uses: actions/checkout@v6
32
+
with:
33
+
submodules: true
29
34
30
-
# Uses the `docker/login-action` action to log in to the Container registry registry using the account and password that will publish the packages. Once published, the packages are scoped to the account defined here.
35
+
# Uses the `docker/login-action` action to log in to the Container registry registry
36
+
# using the account and password that will publish the packages. Once published, the
37
+
# packages are scoped to the account defined here.
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
45
+
# This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about)
46
+
# to extract tags and labels that will be applied to the specified image.
47
+
# The `id` "meta" allows the output of this step to be referenced in a subsequent
48
+
# step. The `images` value provides the base name for the tags and labels.
39
49
# It will automatically create the latest Docker tag, if a git tag is found: https://github.com/docker/metadata-action?tab=readme-ov-file#latest-tag
40
50
- name: Extract metadata (tags, labels) for Docker
# This step uses the `docker/build-push-action` action to build the image, based on your repository's `Dockerfile`. If the build succeeds, it pushes the image to GitHub Packages.
55
-
# It uses the `context` parameter to define the build's context as the set of files located in the specified path. For more information, see [Usage](https://github.com/docker/build-push-action#usage) in the README of the `docker/build-push-action` repository.
56
-
# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
64
+
# This step uses the `docker/build-push-action` action to build the image, based on
65
+
# your repository's `Dockerfile`. If the build succeeds, it pushes the image to
66
+
# GitHub Packages.
67
+
# It uses the `context` parameter to define the build's context as the set of files
68
+
# located in the specified path. For more information, see [Usage](https://github.com/docker/build-push-action#usage)
69
+
# in the README of the `docker/build-push-action` repository.
70
+
# It uses the `tags` and `labels` parameters to tag and label the image with the
# This step generates an artifact attestation for the image, which is an unforgeable statement about where and how it was built. It increases supply chain security for people who consume the image. For more information, see [Using artifact attestations to establish provenance for builds](/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
84
+
# This step generates an artifact attestation for the image, which is an unforgeable
85
+
# statement about where and how it was built. It increases supply chain security for
86
+
# people who consume the image. For more information, see [Using artifact attestations
87
+
# to establish provenance for builds](/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds).
LABEL org.opencontainers.image.description="Ready to deploy Docker container to use ReverSim for research. ReverSim is an open-source environment for the browser, originally developed at the Max Planck Institute for Security and Privacy (MPI-SP) to study human aspects in hardware reverse engineering."
0 commit comments