bjoernager/forgejo
bjoernager/forgejo
1
Fork 0
Code Activity

chore(ci): optimize end-to-end runs

Browse source 
* specify the version targeted by the pull request. The end-to-end
  tests previously compiled all known branches which was a waste. The
  pull request now must specify which version it is targeting so that
  only this version is recompiled and used for testing.
* when building the daily releases, use the release from the
  integration organization to ensure the tests are run against the
  latest build. Clarify in a comment why the lookup order of
  organizations is reversed in this particular case.

Refs: https://code.forgejo.org/forgejo/end-to-end/pulls/239
This commit is contained in:
Earl Warren 2024-08-08 17:53:12 +02:00
parent 7cfa3305bf
commit 1f8e6b6e31
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
2 changed files with 22 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

16
.forgejo/cascading-release-end-to-end
View file

@ -8,15 +8,15 @@ forgejo=$3
forgejo_ref=$4
cd $end_to_end
date > last-upgrade
date >last-upgrade
organizations=lib/ORGANIZATIONS
if ! test -f $organizations ; then
echo "$organizations file not found"
false
if ! test -f $organizations; then
echo "$organizations file not found"
false
fi
#
# do not include forgejo-experimental so that 7.0-test is found
# in forgejo-integration where it was just built instead of
# forgejo-experimental which was published by the previous build
# Inverse the order of lookup because the goal in the release built
# pipeline is to test the latest build, if available, instead of the
# stable version by the same version.
#
echo forgejo forgejo-integration > $organizations
echo forgejo-integration forgejo-experimental forgejo >$organizations