TrueCloudLab/neoneo-go
7
0
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity
neoneo-go/.github/workflows/build.yml

149 lines
4.6 KiB
YAML
Raw Permalink Normal View History

.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
name: Build
on:
pull_request:
branches:
- master
types: [opened, synchronize]
paths-ignore:
- 'scripts/**'
- '**/*.md'
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
push:
# Build for the master branch.
branches:
- master
release:
# Publish released commit as Docker `latest` and `git_revision` images.
types:
- published
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
workflow_dispatch:
.github: allow to trigger Build workflow manually
2021-12-03 09:22:48 +00:00
inputs:
ref:
description: 'Ref to build CLI for Ubuntu and Windows Server Core [default: latest master; examples: v0.92.0, 0a4ff9d3e4a9ab432fd5812eb18c98e03b5a7432]'
required: false
default: ''
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
push_image:
description: 'Push images to DockerHub [default: false; examples: true, false]'
required: false
default: 'false'
use_latest_tag:
description: 'Use `latest` tag while pushing images to DockerHub (applied to Ubuntu image only) [default: false; examples: true, false]'
required: false
default: 'false'
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
jobs:
workflows: simplify build configuration, use OS matrix
2022-07-15 10:55:18 +00:00
build_cli:
name: Build CLI
runs-on: ${{matrix.os}}
strategy:
matrix:
workflows: add MacOS CLI build and test configurations Unfortunately, the default MacOS runner produces amd64 binaries, therefore we need to set GOARCH appropriately. At the same time, docker image will be linux/arm64, so we can build it as well.
2022-07-15 10:56:08 +00:00
os: [ubuntu-20.04, windows-2022, macos-12]
arch: [amd64, arm64]
exclude:
- os: windows-2022
arch: 'arm64'
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
steps:
workflows: use checkout@v3 No functional changes, but let's be up to date.
2022-07-20 16:21:40 +00:00
- uses: actions/checkout@v3
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
with:
.github: allow to trigger Build workflow manually
2021-12-03 09:22:48 +00:00
ref: ${{ github.event.inputs.ref }}
# Allows to fetch all history for all branches and tags. Need this for proper versioning.
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
fetch-depth: 0
- name: Set up Go
workflows: update setup-go to v3 Use built-in cache, simplify steps.
2022-07-20 16:19:51 +00:00
uses: actions/setup-go@v3
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
with:
ci: update workflows' go version
2022-08-08 10:42:49 +00:00
go-version: 1.19
workflows: update setup-go to v3 Use built-in cache, simplify steps.
2022-07-20 16:19:51 +00:00
cache: true
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
- name: Update Go modules
run: go mod download -json
- name: Build CLI
run: make build
workflows: add MacOS CLI build and test configurations Unfortunately, the default MacOS runner produces amd64 binaries, therefore we need to set GOARCH appropriately. At the same time, docker image will be linux/arm64, so we can build it as well.
2022-07-15 10:56:08 +00:00
env:
GOARCH: ${{ matrix.arch }}
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
.github: upload binaries for Build workflows
2021-12-03 08:41:15 +00:00
- name: Upload artifact
uses: actions/upload-artifact@v2
with:
workflows: add MacOS CLI build and test configurations Unfortunately, the default MacOS runner produces amd64 binaries, therefore we need to set GOARCH appropriately. At the same time, docker image will be linux/arm64, so we can build it as well.
2022-07-15 10:56:08 +00:00
name: neo-go-${{ matrix.os }}-${{ matrix.arch }}
workflows: simplify build configuration, use OS matrix
2022-07-15 10:55:18 +00:00
path: ./bin/neo-go*
.github: upload binaries for Build workflows
2021-12-03 08:41:15 +00:00
if-no-files-found: error
workflows: simplify build configuration, use OS matrix
2022-07-15 10:55:18 +00:00
build_image:
needs: build_cli
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
name: Build and push docker image
workflows/Makefile: build Docker image for MacOS We build multiarch linux/amd64 and linux/arm64, because MacOS runner can't build docker images and even if it could that'd be linux/amd64 while we want linux/arm64 for Apple CPUs. Unfortunately, given the way GitHub workflows work we can't avoid using a Makefile helper, there is no easy way to set variables conditionally and/or use some logic to affect their contents. We reintroduce build_image_wsc as well here because Windows images can't be built with buildx using GitHub runners.
2022-07-18 16:14:42 +00:00
runs-on: ubuntu-20.04
steps:
workflows: use checkout@v3 No functional changes, but let's be up to date.
2022-07-20 16:21:40 +00:00
- uses: actions/checkout@v3
workflows/Makefile: build Docker image for MacOS We build multiarch linux/amd64 and linux/arm64, because MacOS runner can't build docker images and even if it could that'd be linux/amd64 while we want linux/arm64 for Apple CPUs. Unfortunately, given the way GitHub workflows work we can't avoid using a Makefile helper, there is no easy way to set variables conditionally and/or use some logic to affect their contents. We reintroduce build_image_wsc as well here because Windows images can't be built with buildx using GitHub runners.
2022-07-18 16:14:42 +00:00
with:
ref: ${{ github.event.inputs.ref }}
fetch-depth: 0
- name: Set up QEMU
uses: docker/setup-qemu-action@v2
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v2
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
- name: Login to DockerHub
workflows: don't login to Docker Hub when not pushing images Minor safety improvement, images are not pushed anyway in this case, but it makes little sense logging in as well.
2022-07-21 12:32:00 +00:00
if: ${{ github.event_name == 'release' || (github.event_name == 'workflow_dispatch' && github.event.inputs.push_image == 'true') }}
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
uses: docker/login-action@v2
with:
username: ${{ secrets.DOCKERHUB_USERNAME }}
password: ${{ secrets.DOCKERHUB_PASSWORD }}
workflows/Makefile: build Docker image for MacOS We build multiarch linux/amd64 and linux/arm64, because MacOS runner can't build docker images and even if it could that'd be linux/amd64 while we want linux/arm64 for Apple CPUs. Unfortunately, given the way GitHub workflows work we can't avoid using a Makefile helper, there is no easy way to set variables conditionally and/or use some logic to affect their contents. We reintroduce build_image_wsc as well here because Windows images can't be built with buildx using GitHub runners.
2022-07-18 16:14:42 +00:00
- name: Set vars
id: setvars
run: make gh-docker-vars
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
- name: Set latest tag
id: setlatest
if: ${{ (github.event_name == 'release' && github.event.release.target_commitish == 'master') || (github.event_name == 'workflow_dispatch' && github.event.inputs.push_image == 'true' && github.event.inputs.use_latest_tag == 'true') }}
run: echo "::set-output name=latest::,${{ steps.setvars.outputs.repo }}:latest"
workflows/Makefile: build Docker image for MacOS We build multiarch linux/amd64 and linux/arm64, because MacOS runner can't build docker images and even if it could that'd be linux/amd64 while we want linux/arm64 for Apple CPUs. Unfortunately, given the way GitHub workflows work we can't avoid using a Makefile helper, there is no easy way to set variables conditionally and/or use some logic to affect their contents. We reintroduce build_image_wsc as well here because Windows images can't be built with buildx using GitHub runners.
2022-07-18 16:14:42 +00:00
- name: Build and push
uses: docker/build-push-action@v3
with:
workflows: use path context for docker builds We have to checkout anyway for setvars step, so we can reuse the data instead of making yet another checkout.
2022-07-21 13:27:34 +00:00
context: .
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
push: ${{ github.event_name == 'release' || (github.event_name == 'workflow_dispatch' && github.event.inputs.push_image == 'true') }}
workflows/Makefile: build Docker image for MacOS We build multiarch linux/amd64 and linux/arm64, because MacOS runner can't build docker images and even if it could that'd be linux/amd64 while we want linux/arm64 for Apple CPUs. Unfortunately, given the way GitHub workflows work we can't avoid using a Makefile helper, there is no easy way to set variables conditionally and/or use some logic to affect their contents. We reintroduce build_image_wsc as well here because Windows images can't be built with buildx using GitHub runners.
2022-07-18 16:14:42 +00:00
platforms: linux/amd64,linux/arm64
build-args: |
Makefile: correct Docker image repository name Fix 403 Forbidden errors on push.
2022-07-21 14:20:37 +00:00
REPO=github.com/${{ github.repository }}
workflows/Makefile: build Docker image for MacOS We build multiarch linux/amd64 and linux/arm64, because MacOS runner can't build docker images and even if it could that'd be linux/amd64 while we want linux/arm64 for Apple CPUs. Unfortunately, given the way GitHub workflows work we can't avoid using a Makefile helper, there is no easy way to set variables conditionally and/or use some logic to affect their contents. We reintroduce build_image_wsc as well here because Windows images can't be built with buildx using GitHub runners.
2022-07-18 16:14:42 +00:00
VERSION=${{ steps.setvars.outputs.version }}
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
tags: ${{ steps.setvars.outputs.repo }}:${{ steps.setvars.outputs.version }}${{ steps.setvars.outputs.suffix }}${{ steps.setlatest.outputs.latest }}
workflows/Makefile: build Docker image for MacOS We build multiarch linux/amd64 and linux/arm64, because MacOS runner can't build docker images and even if it could that'd be linux/amd64 while we want linux/arm64 for Apple CPUs. Unfortunately, given the way GitHub workflows work we can't avoid using a Makefile helper, there is no easy way to set variables conditionally and/or use some logic to affect their contents. We reintroduce build_image_wsc as well here because Windows images can't be built with buildx using GitHub runners.
2022-07-18 16:14:42 +00:00
build_image_wsc:
needs: build_cli
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
name: Build and push docker image (Windows Server Core)
workflows/Makefile: build Docker image for MacOS We build multiarch linux/amd64 and linux/arm64, because MacOS runner can't build docker images and even if it could that'd be linux/amd64 while we want linux/arm64 for Apple CPUs. Unfortunately, given the way GitHub workflows work we can't avoid using a Makefile helper, there is no easy way to set variables conditionally and/or use some logic to affect their contents. We reintroduce build_image_wsc as well here because Windows images can't be built with buildx using GitHub runners.
2022-07-18 16:14:42 +00:00
runs-on: windows-2022
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
steps:
workflows: use checkout@v3 No functional changes, but let's be up to date.
2022-07-20 16:21:40 +00:00
- uses: actions/checkout@v3
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
with:
.github: allow to trigger Build workflow manually
2021-12-03 09:22:48 +00:00
ref: ${{ github.event.inputs.ref }}
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
fetch-depth: 0
workflows: upgrade supported go version
2022-02-22 16:37:27 +00:00
# For proper `deps` make target execution.
- name: Set up Go
workflows: update setup-go to v3 Use built-in cache, simplify steps.
2022-07-20 16:19:51 +00:00
uses: actions/setup-go@v3
workflows: upgrade supported go version
2022-02-22 16:37:27 +00:00
with:
ci: update workflows' go version
2022-08-08 10:42:49 +00:00
go-version: 1.19
workflows: update setup-go to v3 Use built-in cache, simplify steps.
2022-07-20 16:19:51 +00:00
cache: true
workflows: upgrade supported go version
2022-02-22 16:37:27 +00:00
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
- name: Login to DockerHub
workflows: don't login to Docker Hub when not pushing images Minor safety improvement, images are not pushed anyway in this case, but it makes little sense logging in as well.
2022-07-21 12:32:00 +00:00
if: ${{ github.event_name == 'release' || (github.event_name == 'workflow_dispatch' && github.event.inputs.push_image == 'true') }}
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
uses: docker/login-action@v2
with:
username: ${{ secrets.DOCKERHUB_USERNAME }}
password: ${{ secrets.DOCKERHUB_PASSWORD }}
.github: create separate workflow to build CLI/image There's too much jobs in Tests workflow, so we can split them into several parts.
2021-11-19 12:42:53 +00:00
- name: Build Docker image
run: make image
workflows: move docker push logic to the Build workflow publish_to_dockerhub.yml duplicated build.yml and run_tests.yml in many ways. We always want to build docker images, it's just that we don't push them on every occasion and there is some additional logic around the latest tag. We also want to publish multiarch images now, so all of this logic better be consolidated in one workflow. It doesn't depend on tests, since we only publish on release or on manual run, so it's known to be good.
2022-07-20 10:36:00 +00:00
- name: Push image to registry
if: ${{ github.event_name == 'release' || (github.event_name == 'workflow_dispatch' && github.event.inputs.push_image == 'true') }}
run: make image-push
Reference in a new issue Copy permalink