Fix: Submit release note to the same branch

The release note created by 'genenrate-release-notes.sh' is pushed to
the master branch. Make sure the change is submitted to the same branch
in Gerrit.

And remove the sed command to append a new release note file in the
'index.rst' file since the file already includes a wildcard match
'release-notes-*'.

Change-Id: Id396d8fec4eae97b627fa490ea20b2c5f437b998
Signed-off-by: Sangwook Ha <sangwook.ha@verizon.com>

diff --git a/jjb/autorelease/generate-release-notes.sh b/jjb/autorelease/generate-release-notes.sh
index deb7af3d602ac1e5d16dce31b11e0805bb4fff67..9aa5907328917b76a0b40f6bd15a3a6d94238fe6 100644 (file)
--- a/jjb/autorelease/generate-release-notes.sh
+++ b/jjb/autorelease/generate-release-notes.sh
@@ -37,7 +37,6 @@ DOCS_DIR=$(mktemp -d)
 git clone -b "$GERRIT_BRANCH" https://git.opendaylight.org/gerrit/docs.git "$DOCS_DIR"
 cd "$DOCS_DIR" || exit 1
 cp "$WORKSPACE/release-notes.rst" "docs/release-notes/release-notes-${RELEASE,,}.rst"
-sed -i -e '$a     release-notes-'"${RELEASE,,}"'' "docs/release-notes/index.rst"
 git add docs/release-notes/
 
 GERRIT_COMMIT_MESSAGE="Update release notes for $RELEASE"
@@ -63,4 +62,4 @@ git config core.hooksPath "$(git rev-parse --show-toplevel)/.git/hooks"
 
 # Don't fail the build if this command fails because it's possible that there
 # is no changes since last update.
-git review --yes -t "$GERRIT_TOPIC" || true
+git review --yes -t "$GERRIT_TOPIC" "$GERRIT_BRANCH" || true