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

58 lines
1.7 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
steps:
CI: Update to actions/checkout@v4 No functional change, but we should keep this current. see 5f4ddb54b05ae0355b1f64c22263a6bc381410df
2023-09-06 14:57:29 +00:00
- uses: actions/checkout@v4
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
CI: dynamically determine actual version of h2spec previously we used hardcoded h2spec version. let us switch to the latest available
2022-05-05 10:15:12 +00:00
id: install-h2spec
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
run: |
CI: dynamically determine actual version of h2spec previously we used hardcoded h2spec version. let us switch to the latest available
2022-05-05 10:15:12 +00:00
H2SPEC_VERSION=`curl --silent "https://api.github.com/repos/summerwind/h2spec/releases/latest" | jq -r -j '.tag_name'`
curl -fsSL https://github.com/summerwind/h2spec/releases/download/${H2SPEC_VERSION}/h2spec_linux_amd64.tar.gz -o h2spec.tar.gz
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
tar xvf h2spec.tar.gz
sudo install -m755 h2spec /usr/local/bin/h2spec
CI: Replace the deprecated `::set-output` command by writing to $GITHUB_OUTPUT in workflow definition See "CI: Replace the deprecated `::set-output` command by writing to $GITHUB_OUTPUT in matrix.py" for the reasoning behind this commit.
2022-10-14 17:46:07 +00:00
echo "version=${H2SPEC_VERSION}" >> $GITHUB_OUTPUT
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: Compile HAProxy with ${{ matrix.CC }}
run: |
make -j$(nproc) all \
ERR=1 \
TARGET=${{ matrix.TARGET }} \
CC=${{ matrix.CC }} \
CI: update the build options to get rid of unneeded DEBUG options Now that DEBUG_STRICT and DEBUG_MEMORY_POOLS are the default, we can drop them from the build options.
2024-04-10 07:28:24 +00:00
DEBUG="-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
CI: Replace the deprecated `::set-output` command by writing to $GITHUB_OUTPUT in workflow definition See "CI: Replace the deprecated `::set-output` command by writing to $GITHUB_OUTPUT in matrix.py" for the reasoning behind this commit.
2022-10-14 17:46:07 +00:00
echo "version=$(haproxy -v |awk 'NR==1{print $3}')" >> $GITHUB_OUTPUT
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: Launch HAProxy ${{ steps.show-version.outputs.version }}
run: haproxy -f .github/h2spec.config -D
CI: dynamically determine actual version of h2spec previously we used hardcoded h2spec version. let us switch to the latest available
2022-05-05 10:15:12 +00:00
- name: Run h2spec ${{ steps.install-h2spec.outputs.version }}
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
run: h2spec -Svtk -h 127.0.0.1 -p 8443