Skip to content

Commit

Permalink
Add workflow to build and push docker image to gh registry
Browse files Browse the repository at this point in the history
  • Loading branch information
katyukha authored Oct 23, 2024
1 parent be05c70 commit de2d783
Showing 1 changed file with 107 additions and 0 deletions.
107 changes: 107 additions & 0 deletions .github/workflows/publish-dockerhub.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,107 @@
#
name: Create and publish a Docker image

# Configures this workflow to run every time new release is published
on:
release:
types: [published]

# 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.
env:
REGISTRY: ghcr.io
IMAGE_NAME: ${{ github.repository }}
ODOOD_DLANG_COMPILER: ldc-1.39.0

# There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
jobs:
build-ubuntu-20_04:
name: Build Ubuntu:20.04
runs-on: ubuntu-20.04
steps:
- uses: actions/checkout@v4

- name: Install D compiler
uses: dlang-community/setup-dlang@v1
with:
compiler: ${{ env.ODOOD_DLANG_COMPILER }}

- name: Install system dependencies
uses: lyricwulf/abc@v1
with:
linux: libzip-dev libpq-dev python3-dev

- name: Build Odood
run: |
dub build -b release -c bash-autocomplete --d-version OdoodInDocker
dub build -b release --d-version OdoodInDocker
- name: Upload Odood compiled assets
uses: actions/upload-artifact@v3
with:
name: odood-amd64
path: |
build/odood
build/odood.bash
build-and-push-image:
runs-on: ubuntu-latest
# Sets the permissions granted to the `GITHUB_TOKEN` for the actions in this job.
permissions:
contents: read
packages: write
attestations: write
id-token: write
#
steps:
- name: Checkout repository
uses: actions/checkout@v4

- name: 'Download artifacts for amd64'
uses: actions/download-artifact@v3
with:
name: odood-amd64
path: docker/bin/

# 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.
- name: Log in to the Container registry
uses: docker/login-action@65b78e6e13532edd9afa3aa52ac7964289d1a9c1
with:
registry: ${{ env.REGISTRY }}
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}

# 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.
- name: Extract metadata (tags, labels) for Docker
id: meta
uses: docker/metadata-action@9ec57ed1fcdbf14dcef7dfbe97b2010124a938b7
with:
images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}

- name: Prepare debian dependencies dependencies
id: prepare_deb_deps
run: |
echo "universal_deb_deps=$(cat .ci/deps/universal-deb.txt | tr '\n' ',' | sed 's/,$/\n/')" >> $GITHUB_OUTPUT
# 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.
# 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.
# It uses the `tags` and `labels` parameters to tag and label the image with the output from the "meta" step.
- name: Build and push Docker image
id: push
uses: docker/build-push-action@f2a1d5e99d037542a71f64918e516c093c6f3fc4
with:
context: ./docker
push: true
build-args:
ODOO_VERSION: "17.0"
ODOOD_DEPENDENCIES: ${{ steps.prepare_deb_deps.outputs.universal_deb_deps }}
tags: 17.0-${{ github.ref_name }} # ${{ steps.meta.outputs.tags }}
labels: ${{ steps.meta.outputs.labels }}

# 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 "[AUTOTITLE](/actions/security-guides/using-artifact-attestations-to-establish-provenance-for-builds)."
- name: Generate artifact attestation
uses: actions/attest-build-provenance@v1
with:
subject-name: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME}}
subject-digest: ${{ steps.push.outputs.digest }}
push-to-registry: true

0 comments on commit de2d783

Please sign in to comment.