Use fbot (jenkins-ci no longuer exists)

Change-Id: I5b99dc6cd809eaad23f5b92a1650bf2775fd0d01
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>

diff --git a/jjb/releng/releng-release-create-branch.sh b/jjb/releng/releng-release-create-branch.sh
index cef870c..beb493b 100644 (file)
--- a/jjb/releng/releng-release-create-branch.sh
+++ b/jjb/releng/releng-release-create-branch.sh
@@ -14,7 +14,7 @@ STREAM=${STREAM:-'nostream'}
 RELEASE_FILES=$(git diff HEAD^1 --name-only -- "releases/$STREAM")
 
 # Configure the git user/email as we'll be pushing up changes
-git config --global user.name "jenkins-ci"
+git config --global user.name "fbot"
 git config --global user.email "jenkins-opnfv-ci@opnfv.org"
 
 # Ensure we are able to generate Commit-IDs for new patchsets

diff --git a/jjb/releng/releng-release-tagging.sh b/jjb/releng/releng-release-tagging.sh
index 7c4cd25..1fce35f 100644 (file)
--- a/jjb/releng/releng-release-tagging.sh
+++ b/jjb/releng/releng-release-tagging.sh
@@ -49,7 +49,7 @@ for release_file in $RELEASE_FILES; do
               # If the tag doesn't exist and we're in a merge job,
               # everything has been verified up to this point and we
               # are ready to create the tag.
-              git config --global user.name "jenkins-ci"
+              git config --global user.name "fbot"
               git config --global user.email "jenkins-opnfv-ci@opnfv.org"
               echo "--> Creating $tag tag for $repo at $ref"
               git tag -am "$tag" $tag $ref