mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-10 04:05:42 +01:00
854be47328
Refs: https://codeberg.org/forgejo/website/pulls/230 (cherry picked from commit87d56bf6c7) [CI] Forgejo Actions based release process (squash) base64 -w0 to avoid wrapping when the doer name is long as it creates a broken config.json (cherry picked from commit9efdc27e49) [CI] Forgejo Actions based release process (squash) generate .xz files and sources Generate .xz files Check .sha256 Generate the source tarbal (cherry picked from commit7afec520c4) [CI] Forgejo Actions based release process (squash) release notes (cherry picked from commitd8f4f4807b) [CI] Forgejo Actions based release process (squash) publish and sign release (cherry picked from commita52778c747) (cherry picked from commitcf2ec62740) [CI] Forgejo Actions based release process (squash) version use Actions environment variables in Makefile (#25319) (#25318) uses Actions variable to determine the version. But Forgejo builds happen in a container where they are not available. Do not use them. Also verify the version of the binary is as expected for sanity check. (cherry picked from commit6decf111a1) (cherry picked from commit206d0b3886) [CI] read STORED_VERSION_FILE if available (cherry picked from commitaf74085ebf) [CI] backward compatible executable compilation Add a new static-executable target to use in Dockerfiles and restore the $(EXECUTABLE) target to what it was before to for backward compatibility. The release process now builds static executables instead of dynamically linked ones which makes them more portable. It changes the requirements at compile time and is not backward compatible. In particular it may break packaging that rely on the target that currently creates a dynamically linked executable. (cherry picked from commit84d02a174a)
99 lines
3.7 KiB
YAML
99 lines
3.7 KiB
YAML
name: Integration tests for the release process
|
|
|
|
on:
|
|
push:
|
|
paths:
|
|
- Makefile
|
|
- Dockerfile
|
|
- Dockerfile.rootless
|
|
- docker/**
|
|
- .forgejo/actions/build-release/action.yml
|
|
- .forgejo/workflows/build-release.yml
|
|
- .forgejo/workflows/build-release-integration.yml
|
|
|
|
jobs:
|
|
release-simulation:
|
|
runs-on: self-hosted
|
|
if: secrets.ROLE != 'forgejo-integration' && secrets.ROLE != 'forgejo-experimental' && secrets.ROLE != 'forgejo-release'
|
|
steps:
|
|
- uses: actions/checkout@v3
|
|
|
|
- id: forgejo
|
|
uses: https://code.forgejo.org/actions/setup-forgejo@v1
|
|
with:
|
|
user: root
|
|
password: admin1234
|
|
image-version: 1.19
|
|
lxc-ip-prefix: 10.0.9
|
|
|
|
- name: publish the forgejo release
|
|
run: |
|
|
set -x
|
|
|
|
version=1.2.3
|
|
cat > /etc/docker/daemon.json <<EOF
|
|
{
|
|
"insecure-registries" : ["${{ steps.forgejo.outputs.host-port }}"]
|
|
}
|
|
EOF
|
|
systemctl restart docker
|
|
|
|
apt-get install -qq -y xz-utils
|
|
|
|
dir=$(mktemp -d)
|
|
trap "rm -fr $dir" EXIT
|
|
|
|
url=http://root:admin1234@${{ steps.forgejo.outputs.host-port }}
|
|
export FORGEJO_RUNNER_LOGS="${{ steps.forgejo.outputs.runner-logs }}"
|
|
|
|
#
|
|
# Create a new project with a fake forgejo and the release workflow only
|
|
#
|
|
cp -a .forgejo/testdata/build-release/* $dir
|
|
mkdir -p $dir/.forgejo/workflows
|
|
cp .forgejo/workflows/build-release.yml $dir/.forgejo/workflows
|
|
cp -a .forgejo/actions $dir/.forgejo/actions
|
|
cp $dir/Dockerfile $dir/Dockerfile.rootless
|
|
|
|
forgejo-test-helper.sh push $dir $url root forgejo |& tee $dir/pushed
|
|
eval $(grep '^sha=' < $dir/pushed)
|
|
|
|
#
|
|
# Push a tag to trigger the release workflow and wait for it to complete
|
|
#
|
|
forgejo-test-helper.sh api POST $url repos/root/forgejo/tags ${{ steps.forgejo.outputs.token }} --data-raw '{"tag_name": "v'$version'", "target": "'$sha'"}'
|
|
LOOPS=180 forgejo-test-helper.sh wait_success "$url" root/forgejo $sha
|
|
|
|
#
|
|
# uncomment to see the logs even when everything is reported to be working ok
|
|
#
|
|
#cat $FORGEJO_RUNNER_LOGS
|
|
|
|
#
|
|
# Minimal sanity checks. e2e test is for the setup-forgejo
|
|
# action and the infrastructure playbook. Since the binary
|
|
# is a script shell it does not test the sanity of the cross
|
|
# build, only the sanity of the naming of the binaries.
|
|
#
|
|
for arch in amd64 arm64 arm-6 ; do
|
|
binary=forgejo-$version-linux-$arch
|
|
for suffix in '' '.xz' ; do
|
|
curl --fail -L -sS $url/root/forgejo/releases/download/v$version/$binary$suffix > $binary$suffix
|
|
if test "$suffix" = .xz ; then
|
|
unxz --keep $binary$suffix
|
|
fi
|
|
chmod +x $binary
|
|
./$binary --version | grep $version
|
|
curl --fail -L -sS $url/root/forgejo/releases/download/v$version/$binary$suffix.sha256 > $binary$suffix.sha256
|
|
shasum -a 256 --check $binary$suffix.sha256
|
|
rm $binary$suffix
|
|
done
|
|
done
|
|
|
|
sources=forgejo-src-$version.tar.gz
|
|
curl --fail -L -sS $url/root/forgejo/releases/download/v$version/$sources > $sources
|
|
curl --fail -L -sS $url/root/forgejo/releases/download/v$version/$sources.sha256 > $sources.sha256
|
|
shasum -a 256 --check $sources.sha256
|
|
|
|
docker pull ${{ steps.forgejo.outputs.host-port }}/root/forgejo:$version
|
|
docker pull ${{ steps.forgejo.outputs.host-port }}/root/forgejo:$version-rootless
|