RepoMirrors
/
haproxy
mirror of http://git.haproxy.org/git/haproxy.git/
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
haproxy/.github/workflows/compliance.yml

57 lines
1.5 KiB
YAML
Raw Normal View History

CI: Make the h2spec workflow more consistent with the VTest workflow This PR aims to make the workflow more consistent, by reusing the same wording for the step names and the same commands to make it look like the vtest workflow as much as possible. It was renamed to compliance.yml to match the human readable name better. This also allows to extend the workflow with other compliance tools later on, nicely grouping those jobs together in a single file. No functional changes have been made.
2020-11-13 19:15:53 +00:00
name: Spec Compliance
on:
schedule:
CI: Clean up formatting in GitHub Action definitions This patch cleans up the formatting within the .yml definition files for GitHub Actions to ensure a consistent look across all actions.
2021-10-16 16:10:27 +00:00
- cron: "0 0 * * 3"
CI: Make the h2spec workflow more consistent with the VTest workflow This PR aims to make the workflow more consistent, by reusing the same wording for the step names and the same commands to make it look like the vtest workflow as much as possible. It was renamed to compliance.yml to match the human readable name better. This also allows to extend the workflow with other compliance tools later on, nicely grouping those jobs together in a single file. No functional changes have been made.
2020-11-13 19:15:53 +00:00
CI: Add `permissions` to GitHub Actions This change locks down the permissions of the access token in GitHub Actions to only allow reading the repository contents and nothing else. see https://docs.github.com/en/actions/security-guides/automatic-token-authentication#permissions-for-the-github_token
2021-10-16 16:10:26 +00:00
permissions:
contents: read
CI: Make the h2spec workflow more consistent with the VTest workflow This PR aims to make the workflow more consistent, by reusing the same wording for the step names and the same commands to make it look like the vtest workflow as much as possible. It was renamed to compliance.yml to match the human readable name better. This also allows to extend the workflow with other compliance tools later on, nicely grouping those jobs together in a single file. No functional changes have been made.
2020-11-13 19:15:53 +00:00
jobs:
h2spec:
name: h2spec
runs-on: ${{ matrix.os }}
strategy:
matrix:
include:
- TARGET: linux-glibc
CC: gcc
os: ubuntu-latest
env:
H2SPEC_VERSION: '2.6.0'
steps:
CI: Update to actions/checkout@v3 No functional change, but we should keep this current.
2022-04-09 20:08:41 +00:00
- uses: actions/checkout@v3
CI: Make the h2spec workflow more consistent with the VTest workflow This PR aims to make the workflow more consistent, by reusing the same wording for the step names and the same commands to make it look like the vtest workflow as much as possible. It was renamed to compliance.yml to match the human readable name better. This also allows to extend the workflow with other compliance tools later on, nicely grouping those jobs together in a single file. No functional changes have been made.
2020-11-13 19:15:53 +00:00
- name: Install h2spec
run: |
curl -fsSL https://github.com/summerwind/h2spec/releases/download/v${H2SPEC_VERSION}/h2spec_linux_amd64.tar.gz -o h2spec.tar.gz
tar xvf h2spec.tar.gz
sudo install -m755 h2spec /usr/local/bin/h2spec
- name: Compile HAProxy with ${{ matrix.CC }}
run: |
make -j$(nproc) all \
ERR=1 \
TARGET=${{ matrix.TARGET }} \
CC=${{ matrix.CC }} \
CI: github: enable pool debugging by default This enables DEBUG_MEMORY_POOLS and DEBUG_POOL_INTEGRITY so that by default the tests run under stricter checks, which are likely to catch more bugs. Note that these ones are permanently used in prod on haproxy.org.
2022-02-23 16:58:46 +00:00
DEBUG="-DDEBUG_STRICT -DDEBUG_MEMORY_POOLS -DDEBUG_POOL_INTEGRITY" \
CI: Make the h2spec workflow more consistent with the VTest workflow This PR aims to make the workflow more consistent, by reusing the same wording for the step names and the same commands to make it look like the vtest workflow as much as possible. It was renamed to compliance.yml to match the human readable name better. This also allows to extend the workflow with other compliance tools later on, nicely grouping those jobs together in a single file. No functional changes have been made.
2020-11-13 19:15:53 +00:00
USE_OPENSSL=1
sudo make install
- name: Show HAProxy version
id: show-version
run: |
echo "::group::Show dynamic libraries."
if command -v ldd > /dev/null; then
# Linux
ldd $(which haproxy)
else
# macOS
otool -L $(which haproxy)
fi
echo "::endgroup::"
haproxy -vv
echo "::set-output name=version::$(haproxy -v |awk 'NR==1{print $3}')"
- name: Launch HAProxy ${{ steps.show-version.outputs.version }}
run: haproxy -f .github/h2spec.config -D
- name: Run h2spec
run: h2spec -Svtk -h 127.0.0.1 -p 8443