sourcegraph/release.yaml
Jean-Hadrien Chabran 35aed2491e
feat(rel): plug upgradetest into release tests (#61563)
---------

Co-authored-by: Warren Gifford <warrenbruceg@gmail.com>
2024-04-19 16:36:38 +02:00

206 lines
8.5 KiB
YAML

meta:
productName: sourcegraph
repository: 'github.com/sourcegraph/sourcegraph'
owners:
- '@sourcegraph/release'
requirements:
- name: "curl"
cmd: "curl --help"
- name: "Buidkite access token"
# `write_builds` permission is all that's needed here
# You also need to ensure you add access to the Sourcegraph organization on Buildkite.
env: BUILDKITE_ACCESS_TOKEN
# #announce-engineering slack webhook url:
# https://start.1password.com/open/i?a=HEDEDSLHPBFGRBTKAKJWE23XX4&v=dnrhbauihkhjs5ag6vszsme45a&i=pldpna5vivapxe4phewnqd42ji&h=team-sourcegraph.1password.com
# #bolaji-release-testing
# https://start.1password.com/open/i?a=HEDEDSLHPBFGRBTKAKJWE23XX4&v=isv4abynddpox72wwbhaamo76e&i=7zjax5rm5hlilbgrzeb257i62i&h=team-sourcegraph.1password.com
- name: 'Slack Webhook URL'
env: SLACK_WEBHOOK_URL
internal:
create:
steps:
patch:
- name: 'buildkite'
cmd: |
echo "Triggering build on sourcegraph/sourcegraph with VERSION={{version}} on branch {{git.branch}}"
body=$(curl -s --fail-with-body -X POST "https://api.buildkite.com/v2/organizations/sourcegraph/pipelines/sourcegraph/builds" -H "Content-Type: application/json" -H "Authorization: Bearer $BUILDKITE_ACCESS_TOKEN" -d '{
"commit": "HEAD",
"branch": "{{git.branch}}",
"message": "Internal release build for {{version}}",
"env": {
"RELEASE_INTERNAL": "true",
"VERSION": "{{tag}}"
}
}')
exit_code=$?
if [ $exit_code != 0 ]; then
echo "❌ Failed to create build on Buildkite, got:"
echo "--- raw body ---"
echo $body
echo "--- raw body ---"
exit $exit_code
else
echo "Build created, see:"
echo $body | jq .web_url
fi
finalize:
steps:
- name: 'Register on release registry'
cmd: |
echo "pretending to call release registry api"
- name: 'notifications'
cmd: |
set -eu
# Post an annotation.
cat << EOF | buildkite-agent annotate --style info
Internal release is ready for promotion under the branch [\`{{git.branch}}\`](https://github.com/sourcegraph/sourcegraph/tree/$branch).
EOF
test:
steps:
- name: 'check:git tag does not exist'
cmd: |
tags=$(git ls-remote --tags origin | sort -t '/' -k 3 | cut -f 2 | awk -F '/' '{gsub(/\^\{\}$/, "", $3); print $3}' | uniq)
if echo "${tags}" | grep -q "^{{version}}$"; then
echo "❌ Tag '{{version}}' already exists"
exit 1
fi
- name: 'check:migrator-schemas'
cmd: |
set -eu
REGISTRY="${PROD_REGISTRY:-''}"
# the reason this is not in the requirements check of the release yaml is because those checks also
# apply when running the release tooling locally, and the testing steps are supposed to run in CI
if [ -z ${REGISTRY} ]; then
echo "PROD_REGISTRY is not set - unable to check migrator image"
exit 1
fi
IMAGE="${REGISTRY}/migrator:{{tag}}"
# Pull the image so that we can inspect it
echo "pulling migrator image ${IMAGE}"
docker pull "${IMAGE}"
echo "checking migrator image for {{version}} schema description files"
# now we check that the schema description files exist
# we need to trim the result from docker since it has '\r' hence the use of tr
count=$(docker run -t --rm --entrypoint /bin/sh "${IMAGE}" -c "ls -al /schema-descriptions/{{version}}-*.json | wc -l" | tr -d '[:space:]')
if [[ "$count" -ne 3 ]]; then
echo "migrator:{{tag}} does not contain the correct amount of schema description files for this release - expected 3 got ${count}"
exit 1
fi
echo "checking migrator image for older schema description files"
count=$(docker run -t --rm --entrypoint /bin/sh "${IMAGE}" -c "ls -al /schema-descriptions/*-internal_database_schema*json | wc -l" | tr -d '[:space:]')
# in our newer releases we have upwards of 300 schema descriptions, so we check that we have at least 300
if [[ "$count" -lt 300 ]]; then
echo "migrator:{{tag}} does not contain the correct amount of schema description files for this release - expected more than 300 got ${count}"
exit 1
fi
- name: 'db:migration:coherence_test'
cmd: |
set -eu
aspectRC="/tmp/aspect-generated.bazelrc"
rosetta bazelrc > "$aspectRC"
bazelrc=(--bazelrc="$aspectRC" --bazelrc=.aspect/bazelrc/ci.sourcegraph.bazelrc)
# The upgradetest are inferring the stamp-version flag based on the version, so we need to unset it here.
_VERSION=$VERSION
unset VERSION
# We purposely limit the concurrency to 6, because if we use the default, there are
# scenarios where we can exhaust available ports to the docker daemon and end up
# with an infrastructure flake.
max_routines=6
# Hardcoding version, as for now I just want to make sure this works in CI.
bazel ${bazelrc[*]} run //testing/tools/upgradetest:release_test_run -- all \
--post-release-version={{tag}} \
--target-registry us-central1-docker.pkg.dev/sourcegraph-ci/rfc795-internal/ \
--max-routines $max_routines
# Restoring it to avoid creating a footgun if we add more test steps later on.
VERSION=$_VERSION
promoteToPublic:
create:
steps:
- name: 'buildkite'
cmd: |
# We set DISABLE_ASPECT_WORKFLOWS to true, because the promotion is purely about retagging images
# and we don't rely on AW at all.
echo "Triggering build on sourcegraph/sourcegraph with VERSION={{version}} on branch {{git.branch}}"
body=$(curl -s --fail-with-body -X POST "https://api.buildkite.com/v2/organizations/sourcegraph/pipelines/sourcegraph/builds" -H "Content-Type: application/json" -H "Authorization: Bearer $BUILDKITE_ACCESS_TOKEN" -d '{
"commit": "HEAD",
"branch": "{{git.branch}}",
"message": "Promoting internal release {{version}} to public",
"env": {
"DISABLE_ASPECT_WORKFLOWS": "true",
"RELEASE_PUBLIC": "true",
"VERSION": "{{tag}}"
}
}')
exit_code=$?
if [ $exit_code != 0 ]; then
echo "❌ Failed to create build on Buildkite, got:"
echo "--- raw body ---"
echo $body
echo "--- raw body ---"
exit $exit_code
else
echo "Build created, see:"
echo $body | jq .web_url
fi
finalize:
steps:
- name: 'Promote on release registry'
cmd: |
echo "pretending to call release registry api"
- name: 'git:tag'
cmd: |
set -eu
# we need to first fetch the branch because the repo in CI is in a detached state
git fetch origin '+refs/heads/{{git.branch}}:refs/heads/{{git.branch}}'
git checkout {{git.branch}}
git tag {{version}}
git push origin {{git.branch}} --tags
# Annotate build
cat << EOF | buildkite-agent annotate --style info
Promoted release is **publicly available** through a git tag at [\`{{version}}\`](https://github.com/sourcegraph/sourcegraph/tree/{{version}}).
EOF
# tag is usually in the format `5.3.2`
# while version is usually the tag prepended with a v, `v5.3.2`
- name: 'Slack notification (#announce-engineering)'
cmd: |
echo "Posting slack notification for release"
tag="{{tag}}"
changelog_version="${tag//./}"
body=$(curl -s --fail-with-body -X POST "$SLACK_WEBHOOK_URL" -H "Content-Type: application/json" -d '{
"type": "mrkdwn"
"text": "*Sourcegraph {{tag}} has been published*\n\n• <https://sourcegraph.com/docs/CHANGELOG#${changelog_version} | Changelog>\n• <https://github.com/sourcegraph/sourcegraph/releases/tag/{{version}} | GitHub release>"
}')
exit_code=$?
if [ $exit_code != 0 ]; then
echo "❌ Unable to post message to slack, got:"
echo "--- raw body ---"
echo $body
echo "--- raw body ---"
exit $exit_code
else
echo "Posted to slack."
fi