mirrors/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-24 22:35:39 +03:00
Code Issues Projects Releases Packages Wiki Activity
forgejo/.forgejo/cascading-pr-end-to-end

31 lines
843 B
Text
Raw Normal View History

[CI] upload the forgejo under test as an artifact for end-to-end (cherry picked from commit ded1f27ebbae7e5e09973ce15551827cff4a00d1) (cherry picked from commit e452b184557bf170688ca042b3a01af7a233d2ed) [CI] upload the forgejo under test as an artifact for end-to-end (squash) use forgejo-pr cascade a PR to https://code.forgejo.org/forgejo/end-to-end on the forgejo-pr branch which will only run end-to-end tests relevant to a Forgejo PR and not the entire end-to-end suite. (cherry picked from commit 011de92174ad29ee9b3b72d5c845b52ef229f66f) (cherry picked from commit 50290011b255e2a548ed1ef608af947cfc557288) [CI] upload the forgejo under test as an artifact for end-to-end (squash) after build (cherry picked from commit ba35f42e3d1d4ca0132d3edd09c4647940cf5e17) (cherry picked from commit ddf43faecb9a833137dbbb783fddf0b4765b0e87) [CI] upload the forgejo under test as an artifact for end-to-end (squash) do not display env (cherry picked from commit d186ec3db49d8a23d4eb6328e6393c107b166a79) (cherry picked from commit 20e9d4bffb90260dc9699db81ccdd23dd695f8da) [CI] upload the forgejo under test as an artifact for end-to-end (squash) merge feature branches (cherry picked from commit 83cd7a3ad992202c02510e807bdea0f1ab865461) (cherry picked from commit 75fd819ee5161ad9591fe95744e538d805dfb9bb) (cherry picked from commit c6d021692951b1b2dc1209422df766becaa8fe22) (cherry picked from commit 4a0ee31376ce60f498a0844e0aa4dd5f5bf321a4) (cherry picked from commit 5f440052fb67e11e5b6522e87b9b657384da7218) (cherry picked from commit e603cd3dcf3384e3b753aa64f620e6771eff03f1) (cherry picked from commit f1c5e86d83d70560b16fdfcfefda46bde36401bb)
2023-12-16 18:24:55 +03:00
#!/bin/bash
set -ex
end_to_end=$1
end_to_end_pr=$2
forgejo=$3
[CI] do not hardcode the Forgejo release in end-to-end testing Now that Forgejo has its own release number, use the Makefile as a reference. Also document and improve support for debugging this pull_request_target workflow by using a branch in the repository.
2024-03-05 19:44:26 +03:00
forgejo_pr_or_ref=$4
cd $forgejo
full_version=$(make show-version-full)
major_version=$(make show-version-major)
[CI] upload the forgejo under test as an artifact for end-to-end (cherry picked from commit ded1f27ebbae7e5e09973ce15551827cff4a00d1) (cherry picked from commit e452b184557bf170688ca042b3a01af7a233d2ed) [CI] upload the forgejo under test as an artifact for end-to-end (squash) use forgejo-pr cascade a PR to https://code.forgejo.org/forgejo/end-to-end on the forgejo-pr branch which will only run end-to-end tests relevant to a Forgejo PR and not the entire end-to-end suite. (cherry picked from commit 011de92174ad29ee9b3b72d5c845b52ef229f66f) (cherry picked from commit 50290011b255e2a548ed1ef608af947cfc557288) [CI] upload the forgejo under test as an artifact for end-to-end (squash) after build (cherry picked from commit ba35f42e3d1d4ca0132d3edd09c4647940cf5e17) (cherry picked from commit ddf43faecb9a833137dbbb783fddf0b4765b0e87) [CI] upload the forgejo under test as an artifact for end-to-end (squash) do not display env (cherry picked from commit d186ec3db49d8a23d4eb6328e6393c107b166a79) (cherry picked from commit 20e9d4bffb90260dc9699db81ccdd23dd695f8da) [CI] upload the forgejo under test as an artifact for end-to-end (squash) merge feature branches (cherry picked from commit 83cd7a3ad992202c02510e807bdea0f1ab865461) (cherry picked from commit 75fd819ee5161ad9591fe95744e538d805dfb9bb) (cherry picked from commit c6d021692951b1b2dc1209422df766becaa8fe22) (cherry picked from commit 4a0ee31376ce60f498a0844e0aa4dd5f5bf321a4) (cherry picked from commit 5f440052fb67e11e5b6522e87b9b657384da7218) (cherry picked from commit e603cd3dcf3384e3b753aa64f620e6771eff03f1) (cherry picked from commit f1c5e86d83d70560b16fdfcfefda46bde36401bb)
2023-12-16 18:24:55 +03:00
cd $end_to_end
date > last-upgrade
[CI] do not hardcode the Forgejo release in end-to-end testing Now that Forgejo has its own release number, use the Makefile as a reference. Also document and improve support for debugging this pull_request_target workflow by using a branch in the repository.
2024-03-05 19:44:26 +03:00
if test -f "$forgejo_pr_or_ref" ; then
forgejo_pr=$forgejo_pr_or_ref
head_url=$(jq --raw-output .head.repo.html_url < $forgejo_pr)
test "$head_url" != null
branch=$(jq --raw-output .head.ref < $forgejo_pr)
test "$branch" != null
echo $head_url $branch $full_version > forgejo/sources/$major_version
else
forgejo_ref=$forgejo_pr_or_ref
echo $GITHUB_SERVER_URL/$GITHUB_REPOSITORY ${forgejo_ref#refs/heads/} $full_version > forgejo/sources/$major_version
fi
[CI] upload the forgejo under test as an artifact for end-to-end (cherry picked from commit ded1f27ebbae7e5e09973ce15551827cff4a00d1) (cherry picked from commit e452b184557bf170688ca042b3a01af7a233d2ed) [CI] upload the forgejo under test as an artifact for end-to-end (squash) use forgejo-pr cascade a PR to https://code.forgejo.org/forgejo/end-to-end on the forgejo-pr branch which will only run end-to-end tests relevant to a Forgejo PR and not the entire end-to-end suite. (cherry picked from commit 011de92174ad29ee9b3b72d5c845b52ef229f66f) (cherry picked from commit 50290011b255e2a548ed1ef608af947cfc557288) [CI] upload the forgejo under test as an artifact for end-to-end (squash) after build (cherry picked from commit ba35f42e3d1d4ca0132d3edd09c4647940cf5e17) (cherry picked from commit ddf43faecb9a833137dbbb783fddf0b4765b0e87) [CI] upload the forgejo under test as an artifact for end-to-end (squash) do not display env (cherry picked from commit d186ec3db49d8a23d4eb6328e6393c107b166a79) (cherry picked from commit 20e9d4bffb90260dc9699db81ccdd23dd695f8da) [CI] upload the forgejo under test as an artifact for end-to-end (squash) merge feature branches (cherry picked from commit 83cd7a3ad992202c02510e807bdea0f1ab865461) (cherry picked from commit 75fd819ee5161ad9591fe95744e538d805dfb9bb) (cherry picked from commit c6d021692951b1b2dc1209422df766becaa8fe22) (cherry picked from commit 4a0ee31376ce60f498a0844e0aa4dd5f5bf321a4) (cherry picked from commit 5f440052fb67e11e5b6522e87b9b657384da7218) (cherry picked from commit e603cd3dcf3384e3b753aa64f620e6771eff03f1) (cherry picked from commit f1c5e86d83d70560b16fdfcfefda46bde36401bb)
2023-12-16 18:24:55 +03:00
test "$GITHUB_RUN_NUMBER"
[CI] do not hardcode the Forgejo release in end-to-end testing Now that Forgejo has its own release number, use the Makefile as a reference. Also document and improve support for debugging this pull_request_target workflow by using a branch in the repository.
2024-03-05 19:44:26 +03:00
echo $GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_NUMBER/artifacts/forgejo > forgejo/binary-url
Reference in a new issue Copy permalink