name: Integration tests for the release process on: push: paths: - Makefile - 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 cat > /etc/docker/daemon.json < $dir/Dockerfile < /app/gitea/gitea ; chmod +x /app/gitea/gitea EOF 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": "v1.2.3", "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 curl -L -sS $url/root/forgejo/releases/download/v1.2.3/forgejo-1.2.3-$arch > forgejo chmod +x forgejo ./forgejo --version | grep 1.2.3 curl -L -sS $url/root/forgejo/releases/download/v1.2.3/forgejo-1.2.3-$arch.sha256 > forgejo.one shasum -a 256 < forgejo | cut -f1 -d ' ' > forgejo.two diff forgejo.one forgejo.two done docker pull ${{ steps.forgejo.outputs.host-port }}/root/forgejo:1.2.3 docker pull ${{ steps.forgejo.outputs.host-port }}/root/forgejo:1.2.3-rootless