lib: source build replace the matching release

Instead of having an explicit vX.Y-dev version to be referenced
explicitly, a binary built from source replaces the matching
version. For instance, if forgejo/build-from-sources contains v9.0,

* the development branch is compiled from source
* the v9.0 artifact is uploaded
* prior to running any test, the artificat is downloaded and used
* the v9.0 binary is not downloaded from
  forgejo/experimental/integration because it is already present

The vX.Y release is built daily and the end-to-end tests run on it. If
a regression is introduced, it will be spotted within 24h.

Compiling from source is used when the Forgejo runs the end-to-end
suite on a specific pull request.
This commit is contained in:
Earl Warren 2024-08-08 17:05:42 +02:00
parent 427c46dbf9
commit 149c6a545c
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
5 changed files with 19 additions and 26 deletions

View file

@ -52,9 +52,9 @@ function test_successful_upgrades() {
function test_gitea_upgrades() {
local config=$UPGRADE_DIR/default-app.ini
(
echo gitea 1.21 forgejo 7.0-dev
echo gitea 1.21 forgejo 9.0-dev
echo gitea 1.22 forgejo 9.0-dev
echo gitea 1.21 forgejo 7.0
echo gitea 1.21 forgejo 9.0
echo gitea 1.22 forgejo 9.0
) | while read gitea gitea_version forgejo forgejo_version; do
log_info "upgrading from Gitea $gitea_version to Forgejo $forgejo_version"
stop
@ -81,7 +81,6 @@ source $UPGRADE_DIR/test-pprof-upload.sh
function test_upgrades() {
run dependencies
run build_all
run test_successful_upgrades
run test_forgejo_pprof