fleet/.github/workflows
Lucas Manuel Rodriguez 9a3b4cd365
Attempt to stabilize the broken integration.yml workflow (#13653)
#13547

This is an attempt to stabilize this workflow that has been broken for
4-6 months.

# Issue and proposed solution

Github runner VMs re-use UUIDs, which is not supported by Orbit (this
causes a host to be enrolled as two hosts in Fleet), thus, until that is
fixed in https://github.com/fleetdm/fleet/issues/8021 I propose we
stabilize this workflow by testing all `stable` channels only (which is
better than having the build broken all the time IMO).

Once https://github.com/fleetdm/fleet/issues/8021 is fixed we can re-add
the edge channels.
2023-09-01 12:25:17 -03:00
..
config set default shell in workflows (#8108) 2022-10-07 09:43:56 -06:00
build-and-push-fleetctl-docker.yml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
build-binaries.yaml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
build-orbit.yaml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
codeql-analysis.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
deploy-fleet-website.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
docs.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
dogfood-deploy.yml Warn against deploying fleetdm/fleet:main directly (#11316) 2023-04-25 13:22:59 -05:00
example-workflow.yaml Add example workflow (#11893) 2023-05-23 13:52:21 -05:00
fleet-and-orbit.yml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
fleetctl-preview-latest.yml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
fleetctl-preview.yml Fix expected number of hosts for the Test fleetctl preview workflow (#13605) 2023-08-30 17:45:41 -03:00
fleetctl-workstations-canary.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
fleetctl-workstations.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
generate-desktop-targets.yml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
generate-nudge-targets.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
generate-osqueryd-targets.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
golangci-lint.yml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
goreleaser-fleet.yaml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
goreleaser-orbit.yaml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
goreleaser-snapshot-fleet.yaml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
integration.yml Attempt to stabilize the broken integration.yml workflow (#13653) 2023-09-01 12:25:17 -03:00
merge-gatekeeper.yml Add merge gatekeeper action (#13546) 2023-08-31 11:11:46 -05:00
pr-helm.yaml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
push-osquery-perf-to-ecr.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
README.md add concurrency to ci (#8271) 2022-10-24 14:01:00 -06:00
release-helm.yaml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
scorecards-analysis.yml Bump github/codeql-action from 2.2.4 to 2.20.1 (#12437) 2023-06-23 12:40:54 -07:00
test-db-changes.yml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
test-go.yaml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
test-native-tooling-packaging.yml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
test-packaging.yml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
test-website.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
test-yml-specs.yml upgrade go to v1.19.12 (#13617) 2023-08-31 13:49:24 -05:00
test.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
tfsec.yml Bump github/codeql-action from 2.2.4 to 2.20.1 (#12437) 2023-06-23 12:40:54 -07:00
tfvalidate.yml Pin all workflow actions versions by commit (#13462) 2023-08-31 12:09:21 -05:00
trivy_scan.yml Bump github/codeql-action from 2.2.4 to 2.20.1 (#12437) 2023-06-23 12:40:54 -07:00
update-certs.yml add concurrency to ci (#8271) 2022-10-24 14:01:00 -06:00

Github Actions

Fleet uses Github Actions for continuous integration (CI). This document describes best practices and at patterns for writing and maintaining Fleet's Github Actions workflows.

Bash

By default, Github Actions sets the shell to bash -e for linux and MacOS runners. To help write safer bash scripts in run jobs and avoid common issues, override the default by adding the following to the workflow file

defaults:
  run:
    # fail-fast using bash -eo pipefail. See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference
    shell: bash

By specifying the default shell to bash, some extra flags are set. The option pipefail changes the behaviour when using the pipe | operator such that if any command in a pipeline fails, that commands return code will be used a the return code for the whole pipeline. Consider the following example in test-go.yaml

    - name: Run Go Tests
      run: |
        # omitted ...
          make test-go 2>&1 | tee /tmp/gotest.log

If the pipefail option was not set, this job would always succeed because tee would always return success. This is not the intended behavior. Instead, we want the job to fail if make test-go fails.

Concurrency

Github Action runners are limited. If a lot of workflows are queued, they will wait in pending until a runner becomes available. This has caused issue in the past where workflows take an excessively long time to start. To help with this issue, use the following in workflows

# This allows a subsequently queued workflow run to interrupt previous runs
concurrency:
  group: ${{ github.workflow }}-${{ github.head_ref || github.run_id}}
  cancel-in-progress: true

When a workflow is triggered via a pull request, it will cancel previous running workflows for that pull request. This is especially useful when changes are pushed to a pull request frequently. Manually triggered workflows, workflows that run on a schedule, and workflows triggered by pushes to main are unaffected.