1776bff1a1
Some of the libraries are listed in the constraints file using the name found in setup.cfg and some are listed using their canonical name. There doesn't seem to be any pattern to which is which, so just try to update both names under the assumption that only one will be present or if for some unforeseen reason both are there that we want them to be the same anyway. Change-Id: Ia02a4c4365f1e0eb60f186c12a0c16849030c8a5 Signed-off-by: Doug Hellmann <doug@doughellmann.com>
141 lines
4.4 KiB
Bash
Executable File
141 lines
4.4 KiB
Bash
Executable File
#!/bin/bash
|
|
#
|
|
# Script to release a project in one shot, including the git tag and
|
|
# launchpad updates.
|
|
#
|
|
# Copyright 2015 Thierry Carrez <thierry@openstack.org>
|
|
# All Rights Reserved.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
|
|
set -ex
|
|
|
|
TOOLSDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
|
|
source $TOOLSDIR/functions
|
|
|
|
function usage {
|
|
echo "Usage: release.sh [-a] repository series version diff_start SHA announce include_pypi first-full-release extra-metadata"
|
|
echo
|
|
echo "Example: release.sh openstack/oslo.rootwrap mitaka 3.0.3 '' gerrit/master openstack-dev@lists.openstack.org yes no 'meta:release:Workflow+1: Doug Hellmann <doug@doughellmann.com>'"
|
|
}
|
|
|
|
if [ $# -lt 5 ]; then
|
|
usage
|
|
exit 2
|
|
fi
|
|
|
|
REPO=$1
|
|
SERIES=$2
|
|
VERSION=$3
|
|
DIFF_START=$4
|
|
SHA=$5
|
|
ANNOUNCE=$6
|
|
INCLUDE_PYPI=${7:-no}
|
|
FIRST_FULL=${8:-no}
|
|
EXTRA_METADATA="$9"
|
|
|
|
SHORTNAME=`basename $REPO`
|
|
|
|
pre_release_pat='\.[[:digit:]]+[ab][[:digit:]]+'
|
|
rc_release_pat='\.[[:digit:]]+rc[[:digit:]]+'
|
|
if [[ $VERSION =~ $pre_release_pat ]]; then
|
|
RELEASETYPE="development milestone"
|
|
elif [[ $VERSION =~ $rc_release_pat ]]; then
|
|
RELEASETYPE="release candidate"
|
|
else
|
|
RELEASETYPE="release"
|
|
fi
|
|
|
|
setup_temp_space release-tag-$SHORTNAME
|
|
clone_repo $REPO
|
|
REPODIR="$(cd $REPO && pwd)"
|
|
cd $REPODIR
|
|
TARGETSHA=`git log -1 $SHA --format='%H'`
|
|
|
|
# Determine the most recent tag before we add the new one.
|
|
PREVIOUS=$(get_last_tag $TARGETSHA)
|
|
|
|
echo "Tagging $TARGETSHA as $VERSION"
|
|
if git show-ref "$VERSION"; then
|
|
echo "$REPO already has a version $VERSION tag"
|
|
# Reset the notion of "previous" to the version associated with
|
|
# the parent of the commit being tagged, since the tag we're
|
|
# applying already exists.
|
|
PREVIOUS=$(get_last_tag ${TARGETSHA}^1)
|
|
else
|
|
# WARNING(dhellmann): announce.sh expects to be able to parse this
|
|
# commit message, so if you change the format you may have to
|
|
# update announce.sh as well.
|
|
TAGMSG="$SHORTNAME $VERSION $RELEASETYPE
|
|
|
|
meta:version: $VERSION
|
|
meta:diff-start: $DIFF_START
|
|
meta:series: $SERIES
|
|
meta:release-type: $RELEASETYPE
|
|
meta:announce: $ANNOUNCE
|
|
meta:pypi: $INCLUDE_PYPI
|
|
meta:first: $FIRST_FULL
|
|
$EXTRA_METADATA
|
|
"
|
|
git tag -m "$TAGMSG" -s "$VERSION" $TARGETSHA
|
|
git push gerrit $VERSION
|
|
fi
|
|
|
|
# We don't want to die just because we can't update some bug reports,
|
|
# so ignore failures.
|
|
set +e
|
|
|
|
BUGS=$(git log $PREVIOUS..$VERSION | egrep -i "Closes(.| )Bug:" | egrep -o "[0-9]+")
|
|
if [[ -z "$BUGS" ]]; then
|
|
echo "No bugs found $PREVIOUS .. $VERSION"
|
|
else
|
|
$TOOLSDIR/launchpad_add_comment.py \
|
|
--subject="Fix included in $REPO $VERSION" \
|
|
--content="This issue was fixed in the $REPO $VERSION $RELEASETYPE." \
|
|
$BUGS
|
|
fi
|
|
|
|
# Apply the PEP 503 rules to turn the dist name into a canonical form,
|
|
# in case that's the version that appears in upper-constraints.txt. We
|
|
# have to try substituting both versions because we have a mix in that
|
|
# file and if we rename projects we'll end up with bad references to
|
|
# existing build artifacts.
|
|
function pep503 {
|
|
echo $1 | sed -e 's/[-_.]\+/-/g' | tr '[:upper:]' '[:lower:]'
|
|
}
|
|
|
|
# Try to propose a constraints update for libraries.
|
|
if [[ $INCLUDE_PYPI == "yes" ]]; then
|
|
echo "Proposing constraints update"
|
|
dist_name=$(python setup.py --name)
|
|
canonical_name=$(pep503 $dist_name)
|
|
if [[ -z "$dist_name" ]]; then
|
|
echo "Could not determine the name of the constraint to update"
|
|
else
|
|
cd $MYTMPDIR
|
|
clone_repo openstack/requirements stable/$SERIES
|
|
cd openstack/requirements
|
|
git checkout -b "$dist_name-$VERSION"
|
|
sed -e "s/^${dist_name}=.*/$dist_name===$VERSION/" --in-place upper-constraints.txt
|
|
sed -e "s/^${canonical_name}=.*/$canonical_name===$VERSION/" --in-place upper-constraints.txt
|
|
git commit -a -m "update constraint for $dist_name to new release $VERSION
|
|
|
|
$TAGMSG
|
|
"
|
|
git show
|
|
git review -t 'new-release'
|
|
fi
|
|
fi
|
|
|
|
exit 0
|